Search Criteria
Package Details: ledger-live 2.94.0-3
Package Actions
Git Clone URL: | https://aur.archlinux.org/ledger-live.git (read-only, click to copy) |
---|---|
Package Base: | ledger-live |
Description: | Maintain your Ledger devices |
Upstream URL: | https://www.ledger.com/ledger-live |
Keywords: | bitcoin cryptocurrency wallet |
Licenses: | MIT |
Submitter: | meriadec |
Maintainer: | phnx47 |
Last Packager: | phnx47 |
Votes: | 21 |
Popularity: | 0.037252 |
First Submitted: | 2018-07-19 09:01 (UTC) |
Last Updated: | 2024-12-19 06:15 (UTC) |
Dependencies (5)
- electron32 (electron32-binAUR)
- ledger-udevAUR (ledger-udev-gitAUR)
- node-gyp (corepackerAUR) (make)
- nvmAUR (nvm-gitAUR) (make)
- pnpm (yarn-pnpm-corepackAUR, pnpm-binAUR, corepackerAUR) (make)
Required by (2)
- vechain-sync-bin (optional)
- vechain-sync2-bin (optional)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 15 Next › Last »
frostwork commented on 2023-12-14 16:48 (UTC)
The issue was reported ~3 hours ago, the latest package bump is ~ 8hrs old. I'd suggest open communication in here
frostwork commented on 2023-12-14 16:37 (UTC)
Is the latest bump to ledger-live 2.73.0-1 already the fix for the security breach? https://github.com/LedgerHQ/connect-kit/issues/29
cehovski commented on 2023-09-11 16:29 (UTC)
Ah @phnx47. Sorry. I flagged it again. I apologize.
phnx47 commented on 2023-09-11 15:53 (UTC)
@cehovski Package will be updated after release on the website: https://www.ledger.com/ledger-live.
phnx47 commented on 2023-06-24 08:25 (UTC) (edited on 2023-06-24 08:46 (UTC) by phnx47)
@hyper_puncher Hello! Sometimes Ledger cancel published release on GitHub so I don't update
ledger-live
andledger-live-bin
until Ledger publish on website: https://www.ledger.com/ledger-live. If you want latest version from GitHub you can useledger-live-git
package.1x2y commented on 2023-03-31 14:07 (UTC)
I think I'll just wait for that issue to be fixed as I'm in no rush but thanks for the update!
phnx47 commented on 2023-03-31 13:51 (UTC) (edited on 2023-03-31 14:08 (UTC) by phnx47)
@1x2y Oh, yes, it is because major
pnpm
release. You can try manually update PKGBUILD - remove--frozen-lockfile
. But I recommend you downgradepnpm
to v7.LedgerHQ Issue: #3070 - chore: pnpm v8 update + pnpm-lock update
1x2y commented on 2023-03-31 11:19 (UTC)
Same issue, seems like a few people are running into this error since the pnpm 8.0 release due to an incompatibility. Struggling to follow what they're talking about but here's the link:
https://github.com/pnpm/action-setup/issues/40
phnx47 commented on 2023-03-31 11:00 (UTC)
@1x2y Try install with
makepkg
1x2y commented on 2023-03-31 10:57 (UTC)
I ran
yay -Sc --aur
and getting the same message.« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 15 Next › Last »