Package Details: ledger-udev 1-6

Git Clone URL: (read-only, click to copy)
Package Base: ledger-udev
Description: Udev rules to connect a ledger wallet to your linux box
Upstream URL:
Licenses: GPL
Submitter: quest
Maintainer: quest
Last Packager: quest
Votes: 13
Popularity: 1.44
First Submitted: 2018-07-26 08:07
Last Updated: 2019-06-04 02:53

Latest Comments

1 2 Next › Last »

Eothred commented on 2021-01-05 13:44

I had to change the udev-rules as suggested by option 3 here (nano x, using usb):

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.

quest commented on 2020-11-10 03:13

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...

sebstar commented on 2020-11-09 18:32

Please either disable the consistency checks ('SKIP') or keep the checksum updated. Thanks you!

es20490446e commented on 2019-11-14 10:24

curl: (7) Failed to connect to port 443: Connection refused ==> ERROR: Failure while downloading

es20490446e commented on 2019-06-05 10:36

@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.

cuzyoo commented on 2019-06-05 10:16

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!

quest commented on 2019-06-05 02:43

@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).

es20490446e commented on 2019-06-04 08:38

@ 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.

es20490446e commented on 2019-05-22 16:40

@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.

pancakes commented on 2019-05-22 15:27

Could the rules be packaged locally at build-time instead? it doesn't seem right to load it remotely, as the behavior is less transparent.

Packaging the rule file in the AUR package would also show the diffs in an AUR manager. Either way the AUR package will need a version bump if the rule file changes, so why not be explicit?