| 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.38 |
| First Submitted: | 2018-07-26 08:07 (UTC) |
| Last Updated: | 2024-03-25 23:31 (UTC) |
I had to change the udev-rules as suggested by option 3 here (nano x, using usb): https://support.ledger.com/hc/en-us/articles/360019301813
Not sure why it differs from their github version, just thought I could mention if someone else have similar issues. Could be worth a try.
The file hasn't changed in over a year. The SHASUM is correct and I was able to build it just fine. Not sure what your issue is @sebstar, but this package is working fine...
Please either disable the consistency checks ('SKIP') or keep the checksum updated. Thanks you!
curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused ==> ERROR: Failure while downloading https://raw.githubusercontent.com/LedgerHQ/udev-rules/master/20-hw1.rules
@quest This package only does one thing, installing a single file, file that should always work as provided upstream. Otherwise it's better to let them know.
The pkgver function relies on the GitHub interface itself, which has been also quite stable from day one.
The likelihood of the package suddenly stopping working is quite low. And even if that rare case happened, the consequence would simply be that the package no longer updates, and the package manager will clearly notice that to the user. The installed version will still work meanwhile.
I think that it's more productive only to update the PKGBUILD on error, versus doing on every software update. The likelihood of getting a malfunction due to an outdated package, with missing rules, is higher than due to automating updates.
https://bin.privacytools.io/?c286ecfa84da2af0#5Khi3wbmIwlzCTIR5Ew01s72HSM5PmrIaXuq5Ffic0g=
Seems like the upstream repository has new rules, but the checksum hasn't been updated. ==> Validating source files with sha256sums... 20-hw1.rules ... FAILED ==> ERROR: One or more files did not pass the validity check!
@es20490446e I would do this, but it seems the format of the file has changed dramatically before. For instance in your script you still have the sed call which is no longer needed. For now I actually think it is ok for this to break temporarily and require a fix to make sure it continues to operate correctly and doesn't have commands that do nothing (like the sed call).
@ quest In order for the package to be able to update properly it needs a pkgver function.
Take my provided PKGBUILD as example. We can change something if you are not convinced about it, it's rather a suggestion.
@pancakes I don't know what you mean. After building the package is binary itself, with all the files being inside it.
It's only before building that the files are remote, but that's the case to any AUR package.
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?