Package Details: ledger-live 2.84.1-1

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://github.com/LedgerHQ/ledger-live
Keywords: bitcoin cryptocurrency wallet
Licenses: MIT
Submitter: meriadec
Maintainer: phnx47
Last Packager: phnx47
Votes: 20
Popularity: 0.24
First Submitted: 2018-07-19 09:01 (UTC)
Last Updated: 2024-07-26 12:53 (UTC)

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

phnx47 commented on 2024-07-23 07:44 (UTC)

Can build with the latest pnpm.

Tristero commented on 2024-06-11 17:59 (UTC)

The error regarding "frozen lockfile" does no more occurr after downgrading pnpm to 8.15.2-2. (Searched for just the error message, thanks for pointing.)

phnx47 commented on 2024-06-11 17:28 (UTC)

@Tristero please read the pinned message and downgrade pnpm to v8

Tristero commented on 2024-06-11 17:16 (UTC)

After cloning the AUR repo, cd'ing into the git directory and calling makepkg the build fails with the following message:

ERR_PNPM_LOCKFILE_CONFIG_MISMATCH  Cannot proceed with the frozen installation. The current "pnpmfileChecksum" configuration doesn't match the value found in the lockfile

es20490446e commented on 2024-06-03 17:10 (UTC)

I didn't need to downgrade pnpm, neither to use an specific electron version.

I just needed export UV_USE_IO_URING=0.

phnx47 commented on 2024-06-01 06:03 (UTC) (edited on 2024-06-01 06:03 (UTC) by phnx47)

To be able to build the package, you need to downgrade pnpm to v8.

Issue with "bad interpreter: Text file busy", "ELIFECYCLE" should be fixed in 2.81.2-2 with export UV_USE_IO_URING=0

I spent many hours trying to migrate to corepack which is part of nodejs but still 'experimental' for being pnpm version independent. I have some progress, but still have an issue with building in clean chroot.

phnx47 commented on 2024-05-29 05:09 (UTC)

@HD_hirku I didn't know about a kernel-related issue before. Feel free to maintain this package in the proper way.

polyzen commented on 2024-05-29 02:14 (UTC)

HD_hirku, the attitude is completely unnecessary.

"bad interpreter: Text file busy" is a seperate issue which can be worked around by calling export UV_USE_IO_URING=0 before the relevant command/s. It should be fixed in Linux 6.9.3.

HD_hirku commented on 2024-05-29 01:19 (UTC) (edited on 2024-05-29 01:25 (UTC) by HD_hirku)

@phnx47 Do you not understand what "spinning up a fresh VM with bare user directory" means? It means there is no cache. Unless you're implying that pnpm 8.15.2-2 somehow creates a global cache?

The bottom line is: whatever you did to "fix" this it not something that is applying globally. In fact, the error is identical to https://github.com/nodejs/node/issues/53051 but with slightly different versioning:

==> Starting build()...
v20.11.0 is already installed.
Now using node v20.11.0 (npm v10.2.4)
Scope: 60 of 101 workspace projects
Lockfile is up to date, resolution step is skipped
.                                        |    +4145 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 4145, reused 3883, downloaded 0, added 2, done
node_modules/.pnpm/es5-ext@0.10.61/node_modules/es5-ext: Running postinstall script...
node_modules/.pnpm/bufferutil@4.0.8/node_modules/bufferutil: Running install script, failed in 28ms
.../node_modules/bufferutil install$ node-gyp-build
│ sh: /home/throwaway/ledger-live/src/LedgerHQ-ledger-live-6f2bc1a/node_modules/.pnpm/bufferutil@4.0.8/node_modules/bufferutil/node_modules/.bin/node-gyp-build: /bin/sh: bad interpreter: Text file busy
└─ Failed in 29ms at /home/throwaway/ledger-live/src/LedgerHQ-ledger-live-6f2bc1a/node_modules/.pnpm/bufferutil@4.0.8/node_modules/bufferutil
node_modules/.pnpm/protobufjs@6.10.2/node_modules/protobufjs: Running postinstall script...
node_modules/.pnpm/utf-8-validate@5.0.10/node_modules/utf-8-validate: Running install script, failed in 28ms
.../node_modules/utf-8-validate install$ node-gyp-build
│ sh: /home/throwaway/ledger-live/src/LedgerHQ-ledger-live-6f2bc1a/node_modules/.pnpm/utf-8-validate@5.0.10/node_modules/utf-8-validate/node_modules/.bin/node-gyp-build: /bin/sh: bad interpreter: Text file busy
└─ Failed in 28ms at /home/throwaway/ledger-live/src/LedgerHQ-ledger-live-6f2bc1a/node_modules/.pnpm/utf-8-validate@5.0.10/node_modules/utf-8-validate
 ELIFECYCLE  Command failed with exit code 126.
==> ERROR: A failure occurred in build().
    Aborting...

With the error being:

node-gyp-build: /bin/sh: bad interpreter: Text file busy

which is discussed in https://github.com/nodejs/node/issues/53051

So, no, downgrading to "v8" doesn't solve this issue. I would suggest you check your caches and ensure that you're building on a fresh VM w/ latest updates.

If this issue is not related to https://github.com/nodejs/node/issues/53051 then a real patch should be applied here instead of trust-me-bro, or a new upstream issue should be opened. If this ends up being entirely a kernel-related issue, then your comments should reflect as such.

phnx47 commented on 2024-05-26 08:47 (UTC) (edited on 2024-05-26 08:54 (UTC) by phnx47)

To be able to build the package, you need to downgrade pnpm to v8.

Some people receive ELIFECYCLE error. This error is not related to pnpm version. Usually, ELIFECYCLE means there is an issue with npm/pnpm cache on your computer.

1 2 3 4 5 6 .. 14 Next › Last »