Arch Linux User Repository

@zgulg. Sorry I only saw your comment now. I've been really busy the last couple weeks. I have to look into it. Don't know if I will have time for it before end of August though.

For info, I still had this issue: "The remote archive doesn't match the expected checksum".

After some researchs, I found other people having the same issue with yarn. For info, this issue is coming from /tmp being mount with noexec flag on my system. I had to remount it without this flag in order to work.

@scientress, do you think there is something that could be done on companinon packaging to solve this while keeping the noexec flag on /tmp folder of the system? This is the only package I got this issue on Arch.

sorry update to the new release will take another day or two due to the change in how udev rules are handled in the new version

@scientress even better! Thanks too for the speedy response.

I was very busy and sadly missed the 4.2.2 release. Versino 4.2.3 was just released and I updated the package to it.

Hoping we get the v4.2.2 package update soon as v4.2.1 broke all my buttons that launch apps. Apparently Bitfocus reverted that part of the update so hopefully v4.2.2 restores the functionality.

I cannot install version 3.4.4-1:

➤ YN0000: └ Completed in 0s 228ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0002: │ companion@workspace:companion doesn't provide jest (p3325c), requested by jest-mock-extended.
➤ YN0086: │ Some peer dependencies are incorrectly met by your project; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0000: │ /tmp/xfs-424bc765 STDOUT Packing asn1@https://github.com/evs-broadcast/node-asn1.git#commit=0146823069e479e90595480dc90c72cafa161ba1 from sources
➤ YN0000: │ /tmp/xfs-424bc765 STDOUT No package manager configuration detected; defaulting to Yarn
➤ YN0000: │ /tmp/xfs-424bc765 STDOUT 
➤ YN0000: │ /tmp/xfs-424bc765 STDERR ! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e.
➤ YN0000: │ /tmp/xfs-424bc765 STDERR ! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager
➤ YN0000: │ /tmp/xfs-424bc765 STDERR 
➤ YN0000: │ /tmp/xfs-8f102e84 STDOUT Packing node-gyp-build@https://github.com/julusian/node-gyp-build.git#commit=52ef582b6e6394bff838d8e8b6c9d79995f2d706 from sources
➤ YN0000: │ /tmp/xfs-8f102e84 STDOUT No package manager configuration detected; defaulting to Yarn
➤ YN0000: │ /tmp/xfs-8f102e84 STDOUT 
➤ YN0000: │ /tmp/xfs-8f102e84 STDERR ! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e.
➤ YN0000: │ /tmp/xfs-8f102e84 STDERR ! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager
➤ YN0000: │ /tmp/xfs-8f102e84 STDERR 
➤ YN0000: │ /tmp/xfs-424bc765 STDOUT yarn pack v1.22.22
➤ YN0000: │ /tmp/xfs-424bc765 STDOUT success Wrote tarball to "/tmp/xfs-424bc765/package.tgz".
➤ YN0000: │ /tmp/xfs-424bc765 STDOUT Done in 0.06s.
➤ YN0000: │ /tmp/xfs-8f102e84 STDOUT yarn pack v1.22.22
➤ YN0000: │ /tmp/xfs-8f102e84 STDOUT success Wrote tarball to "/tmp/xfs-8f102e84/package.tgz".
➤ YN0000: │ /tmp/xfs-8f102e84 STDOUT Done in 0.04s.
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDOUT Packing asn1@https://github.com/evs-broadcast/node-asn1.git#commit=0146823069e479e90595480dc90c72cafa161ba1 from sources
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDOUT No package manager configuration detected; defaulting to Yarn
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDOUT 
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDERR ! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e.
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDERR ! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDERR 
➤ YN0000: │ /tmp/xfs-5b74445c STDOUT Packing node-gyp-build@https://github.com/julusian/node-gyp-build.git#commit=52ef582b6e6394bff838d8e8b6c9d79995f2d706 from sources
➤ YN0000: │ /tmp/xfs-5b74445c STDOUT No package manager configuration detected; defaulting to Yarn
➤ YN0000: │ /tmp/xfs-5b74445c STDOUT 
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDOUT yarn pack v1.22.22
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDOUT success Wrote tarball to "/tmp/xfs-8dbe51a6/package.tgz".
➤ YN0000: │ /tmp/xfs-8dbe51a6 STDOUT Done in 0.04s.
➤ YN0000: │ /tmp/xfs-5b74445c STDERR ! The local project doesn't define a 'packageManager' field. Corepack will now add one referencing yarn@1.22.22+sha512.a6b2f7906b721bba3d67d4aff083df04dad64c399707841b7acf00f6b133b7ac24255f2652fa22ae3534329dc6180534e98d17432037ff6fd140556e2bb3137e.
➤ YN0000: │ /tmp/xfs-5b74445c STDERR ! For more details about this field, consult the documentation at https://nodejs.org/api/packages.html#packagemanager
➤ YN0000: │ /tmp/xfs-5b74445c STDERR 
➤ YN0018: │ asn1@https://github.com/evs-broadcast/node-asn1.git#commit=0146823069e479e90595480dc90c72cafa161ba1: The remote archive doesn't match the expected checksum
➤ YN0000: │ /tmp/xfs-5b74445c STDOUT yarn pack v1.22.22
➤ YN0000: │ /tmp/xfs-5b74445c STDOUT success Wrote tarball to "/tmp/xfs-5b74445c/package.tgz".
➤ YN0000: │ /tmp/xfs-5b74445c STDOUT Done in 0.04s.
➤ YN0018: │ node-gyp-build@https://github.com/julusian/node-gyp-build.git#commit=52ef582b6e6394bff838d8e8b6c9d79995f2d706: The remote archive doesn't match the expected checksum
➤ YN0000: └ Completed in 1s 719ms
➤ YN0000: · Failed with errors in 1s 994ms

v3.3.1 built fine for me on Manjaro. But I see 2 days back v3.4.0 was released by Bitfocus, so hopefully there is an update soon here on the AUR package.

I seem to be unable to build this package. electron-builder always bails due to an issue with "afterSign". Downgrading from 3.3.1 to 3.2.2 version of the package (which built fine a day ago on my x86 machine) did not help. The companion-x.x.x/electron-output/ directory is never populated.

$ node dist/main.js check-launches
It launches!
$ yarn workspace @companion-app/launcher run -B electron-builder --publish=never --arm64 --linux
  • electron-builder  version=24.13.3 os=5.10.110-34-rockchip-gca15bbe36e6c
  • loaded configuration  file=package.json ("build" field)
  • author is missed in the package.json  appPackageFile=/home/j/.cache/yay/companion/src/companion-3.3.1/launcher/package.json
  • installing production dependencies  platform=linux arch=arm64 appDir=/home/j/.cache/yay/companion/src/companion-3.3.1/launcher
  • packaging       platform=linux arch=arm64 electron=29.3.1 appOutDir=/home/j/.cache/yay/companion/src/companion-3.3.1/electron-output/linux-arm64-unpacked
  • skipping "afterSign" hook as no signing occurred, perhaps you intended "afterPack"?

$ node dist/main.js check-launches
It launches!
$ /home/j/.cache/yay/companion/src/companion-3.2.2/launcher/node_modules/.bin/electron-builder --publish=never --arm64 --linux
  • electron-builder  version=24.9.1 os=5.10.110-34-rockchip-gca15bbe36e6c
  • loaded configuration  file=package.json ("build" field)
  • author is missed in the package.json  appPackageFile=/home/j/.cache/yay/companion/src/companion-3.2.2/launcher/package.json
  • packaging       platform=linux arch=arm64 electron=27.1.2 appOutDir=/home/j/.cache/yay/companion/src/companion-3.2.2/electron-output/linux-arm64-unpacked
  • skipping "afterSign" hook as no signing occurred, perhaps you intended "afterPack"?
Done in 219.14s.

Not sure if this is an upstream issue, or a packaging or an arm64 issue. Any ideas?

----- EDIT ------

electron-builder uses a different output directory for arm64 builds, and the package() function is not aware of this. This change makes it build the package.

diff --git a/PKGBUILD b/PKGBUILD
index b900b1f..d2e8a2a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -65,7 +65,7 @@ build() {
 package() {
        cd "${srcdir}"

-       builddir="${pkgname}-${pkgver}/electron-output/linux-unpacked"
+       builddir="${pkgname}-${pkgver}/electron-output/linux-arm64-unpacked"

        # Licenses
        install -Dm644 "${pkgname}-${pkgver}/LICENSE.md" -t "${pkgdir}/usr/share/licenses/${pkgname}/"

Maybe it's possible to build in some CPU architecture handling?

/etc/udev/rules.d/50-companion.rules:31 Unknown group 'plugdev', ignoring.

plugdev is Ubuntu smell and does not exist in Arch Linux. Since you set mode to 666, the devices are accessible by everyone anyway... Definitely an upstream bug since you removed 50-companion.rules. But you could do some patch magic for the next release :-)

Edit: Created upstream issue: https://github.com/bitfocus/companion/issues/2635