Arch Linux User Repository

@Win8Error:

yeah, the node-canvas error is this one: https://github.com/Automattic/node-canvas/issues/2144

Applying the small patch from https://github.com/Automattic/node-canvas/issues/2144#issuecomment-1287688646 seems to work for that.

As for better-sqlite3, I haven't figured that one out yet...

All of this I think in the end is caused by breaking changes in the newer 19.0.0.0 version of node that arch has shipped recently.

Edit: yes, sure enough, the new PKGBUILD that @BrainDamage has pushed with a dependency on nodejs-lts-hydrogen fixes these issues. Thanks, as always, for prompt and quality packaging @BrainDamage 👍

Build failed ...

==> Beginne prepare()...
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ wordwrapjs@npm:3.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ wrappy@npm:1.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ ws@npm:7.5.7 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ xtend@npm:4.0.2 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yallist@npm:4.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0000: └ Completed in 0s 576ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 1s 593ms
➤ YN0000: Done in 2s 319ms
==> Beginne pkgver()...
==> Beginne build()...
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: └ Completed
➤ YN0000: ┌ Link step
➤ YN0007: │ better-sqlite3@npm:7.5.1 must be built because it never has been before or the last one failed
➤ YN0007: │ canvas@npm:2.9.1 must be built because it never has been before or the last one failed
➤ YN0009: │ canvas@npm:2.9.1 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-dbb22165/build.log)
➤ YN0009: │ better-sqlite3@npm:7.5.1 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-c2854fe9/build.log)
➤ YN0000: └ Completed in 42s 350ms
➤ YN0000: Failed with errors in 42s 620ms
==> FEHLER: Ein Fehler geschah in build().
    Breche ab...

I confirm that this fails to start unless you remove SystemCallFilter=@system-service from the service definition. (Foolish me bisected until I identified that cause, rather than just checking the comments here.)

<del>I think this might have to do with binary stripping, but directly installing this package doesn't work for me while doing a git clone of upstream and manually building from that works perfectly. Here's a diff of this package's build vs my manual build: https://paste.tildeverse.org/?46f5646ab6d98e2c#32apm3aogm1MXa8ToH5wwvU27sVH23HZENkJjqnveMyG</del>

Edit: It works for me now with the following tweak: I had to comment out SystemCallFilter=@system-service in the systemd service to avoid a coredump.

Upstream recently switched from npm to yarn, which causes this to currently fail to build.

To fix this, it should be as simple as using yarn install and yarn build instead of the current npm commands, then cp -r the build to the /usr/lib/node_modules directory.

I apologize for the delay, I've had the changes made ... one month ago, but I've just noticed I never pushed them

I finally figured out a solution to my issue from 10 months ago! I needed to add options=(!strip) to the PKGBUILD, and now this package works perfectly.

Right. I've tracked it down to the https://github.com/Sorunome/mx-puppet-bridge component. Somebody opened an issue there already: https://github.com/Sorunome/mx-puppet-bridge/issues/79

that's a different error, unrelated to the previous unfortunately, it seems to be an upstream problem, npm pins versions of libs while archs track official releases, and arch's sqlite libs are incompatible with that version of better-sqlite in nodejs

now I'm not sure if a newer version of better-sqlite exists which fixes the issue and mx-pupppet-discord has to just point to a different version, or it doesn't exist entirely and you'll have to wait even more

I'd suggest you to report it to mx-puppet-discord bugtracker for now

Thanks for your insights and helpful suggestions @Ta180m and @BrainDamage. Unfortunately, makepkg --cleanbuild made no difference. Indeed, I even cloned the git repo from this package fresh, and that made no difference. Attempting to perform the makepkg as a brand new user failed. I spun up a local vanilla archlinux vm and still get the same error. This is not related to my "upgrade"… as it stands, the PKGBUILD doesn't build, see log from fresh VM here: https://termbin.com/7jve