Package Details: ledger-live-bin 2.92.1-1

Git Clone URL: https://aur.archlinux.org/ledger-live-bin.git (read-only, click to copy)
Package Base: ledger-live-bin
Description: Maintain your Ledger devices
Upstream URL: https://www.ledger.com/ledger-live
Keywords: bitcoin cryptocurrency wallet
Licenses: MIT
Conflicts: ledger-live
Provides: ledger-live
Submitter: DescartesHorse
Maintainer: phnx47
Last Packager: phnx47
Votes: 54
Popularity: 1.11
First Submitted: 2018-07-10 01:52 (UTC)
Last Updated: 2024-11-22 01:15 (UTC)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 Next › Last »

DescartesHorse commented on 2019-04-29 01:28 (UTC)

Odd - maybe retry the download; just redid it myself, and it worked fine :/ otherwise, paste your full output for us :)

oberon2007 commented on 2019-04-29 00:57 (UTC) (edited on 2019-04-29 00:58 (UTC) by oberon2007)

Somehow extraction of the AppImg doesn't seem to work ... /home/oberon/local-build/ledger-live-bin/PKGBUILD: line 33: /home/oberon/local-build/ledger-live-bin/src/ledger-live-desktop-1.8.0-linux-x86_64.AppImage: No such file or directory

DescartesHorse commented on 2019-04-28 22:16 (UTC)

Sorry folks - first baby just born so had missed the notifications. Will have this updated within the hour when I reach a computer.

shredder commented on 2019-04-28 16:12 (UTC)

If people want to manually update this to the current version - 1.8.0

Change: pkgver=1.6.0 to pkgver=1.8.0

Update the sha512sums to: sha512sums_x86_64=(decefa2170be091bde187b9999b4f3416df3266885b646512501cd5ac806a989388c28dc1ada1d9352d6d67cc9eb4f0905129d247dfcd24afe0d20d3d79db3e0)

Cpt_Pi commented on 2019-04-17 07:01 (UTC)

I've updated the PKGBUILD and put it in my github gist.

Please update this PKGBUILD

https://gist.github.com/rblaine95/1f9f79bfe7acb331dc13d0572822c673

DescartesHorse commented on 2019-03-14 04:22 (UTC)

Hi sebstar - first up, no worries! Happy to help :) As for your suggestion, I considered this, however as I'm not an "upstream" maintainer, I figured it doesn't make sense (all I'd be doing is certifying that the file that I retrieved from upstream is the same as the file you retrieved from upstream, and this is certified by the hash as well). In regard to confirming that the hash hasn't been tampered with, I am already signing every git commit I do to this repository.

The best would be if Ledger themselves signed their releases, however, in the absence of this, do you see any benefit to signing the files with my key vs. signing the repo? Thanks!

sebstar commented on 2019-03-13 18:30 (UTC)

Thanks for the package! Would be great if you could additionally PGP-sign the source files for heightened security.

DescartesHorse commented on 2018-12-24 13:03 (UTC)

I'll make them optdepends as we have a few folks with different experiences; I also don't need those libs (and also i3), but understand that other DE's may require them. Thanks @trulex

polyzen commented on 2018-12-23 19:14 (UTC)

I'm not using a DE, just i3.

trulex commented on 2018-12-23 19:03 (UTC)

I reproduced this twice on a fresh Plasma installation. Maybe other DEs provide the dependencies in other packages