This is not a valid PKGBUILD. You MUST version the download, and you MUST NOT pull directly from master.
Search Criteria
Package Details: ledger-udev 1-9
Package Actions
Git Clone URL: | https://aur.archlinux.org/ledger-udev.git (read-only, click to copy) |
---|---|
Package Base: | ledger-udev |
Description: | Udev rules to connect a ledger wallet to your linux box |
Upstream URL: | https://www.ledgerwallet.com |
Licenses: | Apache |
Submitter: | quest |
Maintainer: | quest |
Last Packager: | quest |
Votes: | 25 |
Popularity: | 0.22 |
First Submitted: | 2018-07-26 08:07 (UTC) |
Last Updated: | 2024-03-25 23:31 (UTC) |
Dependencies (1)
- udev (systemd-chromiumosAUR, eudevAUR, systemd-selinuxAUR, systemd-gitAUR, systemd-fmlAUR, systemd)
Required by (4)
Sources (1)
Scimmia commented on 2024-03-31 03:13 (UTC)
joow commented on 2024-03-29 07:35 (UTC)
@TSTSTS there is a good chance that you already got an older version of the file 20-hw1.rules
downloaded from a previous build.
Delete the file and you should be good.
TSTSTS commented on 2024-03-28 21:05 (UTC)
Hello I am getting an error when updating. Did I do something wrong?
==> Making package: ledger-udev 1-9 (Thu 28 Mar 2024 03:30:32 PM CDT) ==> Retrieving sources... -> Found 20-hw1.rules ==> Validating source files with sha256sums... 20-hw1.rules ... FAILED ==> ERROR: One or more files did not pass the validity check! error: failed to download sources for 'ledger-udev-1-9': error: packages failed to build: ledger-udev-1-9
overrule commented on 2024-03-03 10:02 (UTC)
I flagged the package out of date since the checksum doesn't match the source anymore. Is it expected of the user to work around this? Currently this package is a dependency of ledger-live-bin, so installing that package results in an error.
carlosala commented on 2023-05-04 07:10 (UTC)
Could we update to latest add_udev_rules.sh
. It adds compatibility for Ledger Stax. I think we could just copy that directly in AUR, and track the repo. It's going to be for sure easier.
Eothred commented on 2023-03-22 21:42 (UTC)
The shell script now installs to /etc/udev/rules.d/20-hw1.rules, and on my computer it looks like I need to move it there to make it work?
phnx47 commented on 2023-02-27 04:47 (UTC) (edited on 2023-02-27 05:19 (UTC) by phnx47)
I don't think that use 20-hw1.rules
from repository is good idea. This repository is bad maintain. No releases, no tags, actual rules in add_udev_rules.sh
, 20-hw1.rules
produced by add_udev_rules.sh
and obsolete now. My PR#23 ignored.
Maybe better just copy 20-hw1.rules
to AUR, track GitHub changes in add_udev_rules.sh
and update file in AUR manually. We can add our own rules as well.
sshaikh commented on 2023-02-22 22:10 (UTC)
@yochananmarqos, you'd need the udev rules to use via a web browser or to install (unsigned) apps directly etc.
yochananmarqos commented on 2023-02-22 21:23 (UTC)
@sshaikh: How would it be useful otherwise? Maybe if someone packaged the CLI application?
sshaikh commented on 2023-02-22 21:13 (UTC)
I think it might have something to do with me accessing the machine remotely and so not being subject to uaccess. Will dig more.
Pinned Comments
sshaikh commented on 2023-02-22 20:04 (UTC)
Another two points:
Should this be a vcs package? I understand that the source file doesn't change but since it's being downloaded from master, it's not really a reproducible build and will remain at 1-8 even if the source file changes.
I always have to add MODE="0666" to these udev rules in order to actually access the hardware, as per:
https://wiki.archlinux.org/title/udev#Allowing_regular_users_to_use_devices
is there a strategy here that I'm missing that doesn't require this?