Arch Linux User Repository

Hello, I wanted to report the release script has been moved out from the repository and moved to its own package.

BTW @jneidel, it's building fine now. Perhaps something was temporally broken from the npm packages provider... Good thing, now it builds fine.

@jneidel, yes, I tried daownloading the snapshot and doing everything anew:

wget https://aur.archlinux.org/cgit/aur.git/snapshot/nodejs-webpack.tar.gz
tar zxf nodejs-webpack.tar.gz
cd nodejs-webpack/
makepkg

And getting the same:

==> Starting package()...

added 77 packages, and audited 78 packages in 6s

9 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm notice
npm notice New major version of npm available! 8.19.2 -> 9.8.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.8.0
npm notice Run npm install -g npm@9.8.0 to update!
npm notice
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
grep: /home/vasqueja/.pkgs/src/others/nodejs-webpack/pkg/nodejs-webpack/usr/lib/node_modules: Is a directory
grep: /home/vasqueja/.pkgs/src/others/nodejs-webpack/pkg/nodejs-webpack/usr/lib/node_modules: Is a directory
==> Creating package "nodejs-webpack"...
  -> Generating .PKGINFO file...
cat: ./usr/lib/node_modules: Is a directory
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
bsdtar: (null)
  -> Compressing package...
bsdtar: (null)
==> ERROR: Failed to create package file.

It's weird since I can build jitsi-meet-desktop which actually build webpack, with no issues... I also can build nodejs-nativefier with no issues, part of which nodejs-webpack indicates it's based on...

@je-vv have you tried a clean build? Otherwise I don't know what could cause that.

Hi @jneidel, I have no idea why this error when building:

==> Starting package()...

added 77 packages, and audited 78 packages in 5s

9 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm notice
npm notice New major version of npm available! 8.19.2 -> 9.7.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.7.2
npm notice Run npm install -g npm@9.7.2 to update!
npm notice
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
grep: /home/vasqueja/.pkgs/src/laur/nodejs-webpack/pkg/nodejs-webpack/usr/lib/node_modules/webpack/lib: Is a directory
grep: /home/vasqueja/.pkgs/src/laur/nodejs-webpack/pkg/nodejs-webpack/usr/lib/node_modules/webpack/schemas: Is a directory
grep: /home/vasqueja/.pkgs/src/laur/nodejs-webpack/pkg/nodejs-webpack/usr/lib/node_modules/webpack/node_modules/fast-json-stable-stringify: Is a directory
...
grep: /home/vasqueja/.pkgs/src/laur/nodejs-webpack/pkg/nodejs-webpack/usr/lib/node_modules/webpack/node_modules/fast-deep-equal: Is a directory
grep: /home/vasqueja/.pkgs/src/laur/nodejs-webpack/pkg/nodejs-webpack/usr/lib/node_modules/webpack/node_modules/buffer-from: Is a directory
grep: /home/vasqueja/.pkgs/src/laur/nodejs-webpack/pkg/nodejs-webpack/usr/lib/node_modules/webpack/node_modules/acorn-import-assertions: Is a directory
==> Creating package "nodejs-webpack"...
-> Generating .PKGINFO file...
cat: ./usr/lib/node_modules/webpack/lib: Is a directory
cat: ./usr/lib/node_modules/webpack/schemas: Is a directory
cat: ./usr/lib/node_modules/webpack/node_modules/fast-json-stable-stringify: Is a directory
...
cat: ./usr/lib/node_modules/webpack/node_modules/fast-deep-equal: Is a directory
cat: ./usr/lib/node_modules/webpack/node_modules/buffer-from: Is a directory
cat: ./usr/lib/node_modules/webpack/node_modules/acorn-import-assertions: Is a directory
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
bsdtar: (null)
-> Compressing package...
bsdtar: (null)
==> ERROR: Failed to create package file.

That when doing simple makepkg. Any ideas?

Hi @simon04, is nodejs-webpack a superset of nodejs-webpack-cli now? They have files in conclict with recent update of both. Actually I had to uninstall both, to be able to install one of them, and only one. I just went for nodejs-webpack, since that's I'd guess the biggest one...

> pacman -S nodejs-webpack-cli
...
checking for file conflicts...
error: failed to commit transaction (conflicting files)
nodejs-webpack-cli: /usr/bin/webpack exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/LICENSE exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/README.md exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/SECURITY.md exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/bin/webpack.js exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/hot/dev-server.js exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/hot/emitter.js exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/hot/lazy-compilation-node.js exists in filesystem (owned by nodejs-webpack)
...
nodejs-webpack-cli: /usr/lib/node_modules/webpack/lib/APIPlugin.js exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/lib/AbstractMethodError.js exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/lib/AsyncDependenciesBlock.js exists in filesystem (owned by nodejs-webpack)
...
nodejs-webpack-cli: /usr/lib/node_modules/webpack/lib/webworker/ImportScriptsChunkLoadingPlugin.js exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/lib/webworker/ImportScriptsChunkLoadingRuntimeModule.js exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/lib/webworker/WebWorkerTemplatePlugin.js exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/node_modules/.bin/acorn exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/node_modules/.bin/browserslist exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/node_modules/.bin/terser exists in filesystem (owned by nodejs-webpack)
...
nodejs-webpack-cli: /usr/lib/node_modules/webpack/node_modules/yocto-queue/license exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/node_modules/yocto-queue/package.json exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/node_modules/yocto-queue/readme.md exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/package.json exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/schemas/WebpackOptions.json exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/schemas/_container.json exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/schemas/_sharing.json exists in filesystem (owned by nodejs-webpack)
...
nodejs-webpack-cli: /usr/lib/node_modules/webpack/schemas/plugins/sharing/ProvideSharedPlugin.json exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/schemas/plugins/sharing/SharePlugin.json exists in filesystem (owned by nodejs-webpack)
nodejs-webpack-cli: /usr/lib/node_modules/webpack/types.d.ts exists in filesystem (owned by nodejs-webpack)
Errors occurred, no packages were upgraded.

If one is a subset of the other, can the conflict variable be used to prevent such errors. Otherwise, can they be installed in a way they don't conflict with each other? Thanks !

@simon04, could you please add --cache "${srcdir}/npm-cache" or something similar so that npm doesn't pollute the FS with bloated stuff? Thanks !