Arch Linux User Repository

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.nodejs-nativefier/releases

Seems to work fine after bumping pkgver to 46.0.4. EDIT: 46.1.1 also works with no further changes.

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.nodejs-nativefier/releases

Hi, upstream Nativefier maintainer here.

Heads up to the maintainers of this AUR package: in 45.0.1 I'm (re-)introducing lockfiles (package-lock.json + app/package-lock.json), for security & reproducibility reasons. Looking at your PKGBUILD I don't see obvious trouble with it, but please confirm. If upstream changes are needed, GitHub issue/PR welcome.

Cheers.

EDIT 2021-09-25 45.0.1 meant to introduce lockfiles, but a misunderstanding of npm publishing caused it to actually not have them. This was fixed in 45.0.4, which now actually includes the lockfiles.

hi, please upgrade checksum to sha256sums.

@gdamjan good call! Removed

--user root needs to be removed from the npm install

I had the same problem as @najahiri. This fixed it:

sudo npm install -g semver@7.2.0 sudo npm install -g npm@7.7.4

I am compiling the package and it gives an error in the form npm ERR! semver.simplifyRange is not a function and cannot complete the installation.

Has a bunch of /usr/lib/node_modules/root/ files conflicting with https://archlinux.org/packages/community/any/semver/ now.

@Superjolly002 21-03-17 I can confirm straight building in "clean" Arch worked (yaourt and pamac-aur failed in remnants of Antergos: dead repos disabled, survives just as "Arch w/graphic install", 2 different PCs; this may be a problem of messy optional [system, not package] dependencies preventing clean upgrade, if the problem persists, try building in clean chroot)

@Superjolly002 upgrading npm from 7.6.0 to 7.6.3 fixed it for me.

@Superjolly002 Can you build directly without a helper and post a gist to the debug error log? Alternatively, feel free to email me directly (email is in my profile).

@lostkhaos I tried to remove the npm and paru cache, but it didn't work. Other ideas?

@Superjolly002 it looks like that might happen if something is confusing npm's cache (old version of npm or the use of nvm). Someone else on AUR managed to fix it by clearing their local npm cache, but we're overriding the cache in our PKGBUILD, so I would think that would prevent this.

Are you able to remove your helper's cache (~/.cache/paru/clone/nodejs-nativefier/) or build directly without using a helper?

I can't update the package because of a missing function (I think):

npm ERR! semver.simplifyRange is not a function

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/foo/.cache/paru/clone/nodejs-nativefier/src/npm-cache/_logs/2021-03-14T08_57_50_764Z-debug.log

Folks on NPM 7, be aware that there's an upstream issue that breaks --prefix see here.

@mxfm your issue is likely related to that bug then.

@lostkhaos yes, I have npm 7.0.5-1

Edit: If you're on NPM 7, this could be related to a bug upstream there.

Otherwise.. I'm honestly mystified how it fails to build in a clean environment for you but not for me. Does the tweak proposed by NobodyDBG fix the problem for you? I'll just fold it in if it fixes the problem for folks since I can't recreate it myself. Here's the Dockerfile I'm using to make sure my environment isn't accidentally fixing the problem:

FROM archlinux/base

# General setup
RUN pacman -Syu --noconfirm && pacman -S --needed --noconfirm base-devel
RUN useradd lowpriv -m
RUN echo 'lowpriv   ALL=(ALL) NOPASSWD: ALL' >> /etc/sudoers
USER lowpriv

# Build
RUN cd /tmp && \
    curl -LO https://aur.archlinux.org/cgit/aur.git/snapshot/nodejs-nativefier.tar.gz && \
    tar -xzf nodejs-nativefier.tar.gz
RUN sudo pacman -S --noconfirm nodejs unzip jq npm
RUN cd /tmp/nodejs-nativefier && makepkg

I cannot update the package either in my local environment or in clean chroot (via aurutils) because of error 'npm ERR! enoent ENOENT: no such file or directory, lstat '/build/nodejs-nativefier/pkg/nodejs-nativefier/usr''.

Npm wanted a update yesterday to update WhatsApp

@damico: I've seen that error when mixing architectures (e.g. trying to run x86 ELF files on ARM).

@NobodyDBG: I don't get that error but I see some folks online also getting that issue (e.g. lerna).

Do you have any environment variables or etc that might be messing with npm? I just tested it in a clean environment with npm 6.14.8-2 (nodejs 15.1.0-1).

Hi. Sorry, I must modify your PKGBUILD to install the Update. Error: ==> Beginne package()... npm ERR! code ENOENT npm ERR! syscall lstat npm ERR! path /tmp/AUR/nodejs-nativefier/pkg/nodejs-nativefier/usr/lib npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, lstat '/tmp/AUR/nodejs-nativefier/pkg/nodejs-nativefier/usr/lib' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in: npm ERR! /tmp/AUR/nodejs-nativefier/src/npm-cache/_logs/2020-11-10T18_52_30_968Z-debug.log ==> FEHLER: Ein Fehler geschah in package().

To fix this error: package() { # Thanks jeremejevs and je-vv for the pointers on these! mkdir "$pkgdir/usr/" mkdir "$pkgdir/usr/lib" npm install -g --user root --cache "${srcdir}/npm-cache" --prefix "$pkgdir/usr" "$srcdir/$_npmname-$pkgver.tgz"

Hi, I'm getting this error:

==> Starting package()...
/usr/local/bin/node: /usr/local/bin/node: cannot execute binary file
==> ERROR: A failure occurred in package().
Aborting...
error making: nodejs-nativefier

Could you help me fix it?

License is missing. Should be MIT according to upstream.

@nahuelwexd added!

This package needs unzip as dependency :) Or you will get an Error during build. Run with --verbose for details. Error: spawn unzip ENOENT when using it

Thanks!

Nice, thanks @alecmev for the heads-up! Added that new chown recommendation+a quick noextract.

There has been a development, more cleanup is necessary now, unfortunately. Also, a noextract would be nice. More information in this wiki diff.

Currently this is the only package that seems to give me this error during makepkg, which hasn't happened UNTIL there was a new update: ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

may i have some help? (this honestly only happens with this package, i can install other packages with ease)

@lostkhaos Thank you!

@jeremejevs nice. Folded in the guideline changes. Been mildly irritated by that permission problem too.

@lostkhaos Please, take a look at the Node.js package guidelines: https://wiki.archlinux.org/index.php/Node.js_package_guidelines I personally am interested in the addition of the permission fix (777 vs. 755), but it also explains why the cache override suggested by @je-vv is needed. And why download the tarball, but not use it when installing? Here's a full PKGBUILD which appears to be inline with the guidelines: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=nodejs-neovim

@je-vv, does this solve a build issue or is it a sanity thing? I tried with and without that line and compared the generated packages and they look pretty similar to me other than timestamps.

Can you please add export npm_config_cache="$srcdir/npm_cache" prior to calling any nbm command? This will prevent dirtying other areas, and also will prevent as well picking caches from other/prior builds which have set this up.