Arch Linux User Repository

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.

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

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.

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

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.

@HD_hirku I reproduced your issue with ELIFECYCLE when I tried installing without clean src that's why I suggested clean up src.

I can build with the following command as well:

$ source /usr/share/nvm/init-nvm.sh && git clone https://aur.archlinux.org/ledger-live.git && cd ledger-live && makepkg -sci

@phnx47 this makes absolutely no sense as I'm spinning up a fresh VM with bare user directory and using only the following command:

$ source /usr/share/nvm/init-nvm.sh && git clone https://aur.archlinux.org/ledger-live.git && cd ledger-live && makepkg -sci

Removing src and re-running makepkg changes nothing as it's simply repeating the original src generation process.

@HD_hirku I can build with pnpm v8.15.2. If you receive ELIFECYCLE error, then you need to clean up your src folder: rm -R src.

@phnx47 I cannot successfully build when rolling back to pnpm v8. I'm receiving ELIFECYCLE build errors:

node_modules/.pnpm/bufferutil@4.0.8/node_modules/bufferutil: Running install script, failed in 26ms
.../node_modules/bufferutil install$ node-gyp-build
│ sh: /home/hirku/ledger-live/src/LedgerHQ-ledger-live-6f2bc1a/node_modules/.pnpm/bufferutil@4.0.8/node_modules/bufferutil/node_m…
└─ Failed in 26ms at /home/hirku/ledger-live/src/LedgerHQ-ledger-live-6f2bc1a/node_modules/.pnpm/bufferutil@4.0.8/node_modules/bufferutil
 ELIFECYCLE  Command failed with exit code 126.
==> ERROR: A failure occurred in build().
    Aborting...

I have tried the following:

pnpm-8.6.1-1-any.pkg.tar.zst
pnpm-8.7.0-1-any.pkg.tar.zst
pnpm-8.8.0-1-any.pkg.tar.zst
pnpm-8.10.0-1-any.pkg.tar.zst
pnpm-8.13.1-1-any.pkg.tar.zst
pnpm-8.15.0-1-any.pkg.tar.zst
pnpm-8.15.1-1-any.pkg.tar.zst
pnpm-8.15.2-2-any.pkg.tar.zst

Which version are you using that builds successfully?

@HD_hirku I can build it with pnpm v8. Also I tried switch to corepack which is part of nodejs but still 'experimental' and I have issue with it.