Arch Linux User Repository

@jeyes https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

If people are having issues, try building with extra-x86_64-build in a clean chroot.

Hi!

Zotero 8 ships ARM Linux Support, see: https://www.zotero.org/blog/zotero-8/#arm-linux-support

We have been testing this in the zotero-beta-bin (https://aur.archlinux.org/packages/zotero-beta-bin) for a while now already and it works great.

Here is the commit from August last year that introduced aarch64 support in zotero-beta-bin: https://aur.archlinux.org/cgit/aur.git/commit/?h=zotero-beta-bin&id=2f13b4807337db19dd0b898efa6d0af16bb64b60

Now that Zotero 8 is released, it would be great if this zotero package could also support aarch64:

It's actually quite easy, just one workaround is needed because CARCH refers to aarch64 in Arch, but the staging folder of Zotero uses arm64 in its name.

To make things easy I set up things in a zotero_aarch64 branch here: https://github.com/mkurz/aur/commits/zotero_aarch64

That branch contains just one commit on top of your zotero branch you maintain, with the fix necessary: https://github.com/mkurz/aur/commit/bf9b1a60f2aa710ea28c6c3845f4b77730ff060e

You can apply that code now easily in your repo with:

git remote add mkurz git@github.com:mkurz/aur.git
git fetch mkurz zotero_aarch64
git merge mkurz/zotero_aarch64

I have tested that branch on my aarch64 (Asahi Linux) and it works great, the package will be created correctly.

Afterwards you could release a new version - please do not forget to bump pkgrel.

Would be great if you could do that :) What do you think?

Thank you very much!

PS: I also added a similiar commit to https://aur.archlinux.org/packages/zotero-bin to make things work over there as well.

With this diff, the package buidlds for the 7.0.31 release. Needed because there were changes for the document fields in that release compared to the current 7.0.30, and it meant that I couldn't sync some items on Arch, that e.g. I've added on a MacOS client. It was mystifying until checked the logs and release notes, and updating to the new version fixed things for me on Arch.

diff --git a/PKGBUILD b/PKGBUILD
index cb377e0..584d082 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Aaron Keesing <agkphysics at gmail dot com>

 pkgname=zotero
-pkgver=7.0.30
+pkgver=7.0.31
 pkgrel=1
 pkgdesc="A free, easy-to-use tool to help you collect, organize, cite, and share your research sources."
 arch=('x86_64' 'i686')
@@ -9,7 +9,7 @@ url="https://github.com/zotero/zotero"
 license=('AGPL-3.0-or-later')
 depends=('dbus-glib' 'gtk3' 'nss' 'libxt')
 makedepends=('npm' 'git' 'zip' 'unzip' 'perl' 'python>=3' 'curl' 'wget' 'rsync' 'nodejs' 'patch')
-_tag=76a04d5aff69a6515aef7af1e3496510f74e62d2 # git rev-parse $pkgver
+_tag=4abc0975f45c8ff5e02a183f354b8d3c685dac5c  # git rev-parse $pkgver
 source=("zotero.desktop"
         "zotero-client::git+https://github.com/zotero/zotero.git#tag=${_tag}"
         "zotero-translators::git+https://github.com/zotero/translators.git"
@@ -27,7 +27,7 @@ source=("zotero.desktop"
         "zotero-epub-js::git+https://github.com/zotero/epub.js.git"
         "disable-updater.patch")
 sha256sums=('eab76db7a56a4d9aaa17baaf240b82fcf57944a4ddf8ef1b58cc64182426cedc'
-            'd500b977fde886b2195e2f99a8195093263c3bc2df50a5adb88dd4a0c5ca0490'
+            '3a0b2c6d6cbe9d3d3c861ed99721cd04a13de0dfb265ed9e061074619231095e'
             'SKIP'
             'SKIP'
             'SKIP'

@carsme I have added the 0BSD license, REUSE.toml, etc., to the repo.

I'm planning to move this to the official repositories. In order to base our package on your PKGBUILD, we'll need you to license it under 0BSD, see https://rfc.archlinux.page/0040-license-package-sources/.

Could you add a 0BSD license file to the repository? Alternatively, run pkgctl license setup and it will do it for you.

Thanks for maintaining this so far!

@JonasKonrad @AmbassadorDave I have made the suggested change. It seems they have also patched the issue in Node, so it may be that only that specific version is affected. Hopefully in future we can remove the needed option entirely so long as people do not install that specific version.

@agkphysics I seem to be one affected by the --no-experimental-webstorage workaround, hopefully JonasKonrad's recommendation would fix it?

==> Starting build()...
node: --no-experimental-webstorage is not allowed in NODE_OPTIONS
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: zotero-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
zotero - exit status 4

My installation does use nodejs-lts-iron

@agkphysics Consider using

node_options="--openssl-legacy-provider"
if (( $(vercmp "$(node --version)" "25.2.0") >= 0 )); then
    node_options="$node_options --no-experimental-webstorage"
fi
NODE_OPTIONS=$node_options npm run build

Otherwise, build will fail for people like me who use a nodejs LTS version (from the extra repo!).

@agkphysics that fixed it. I can build in a clean chroot now. Thanks.

@daniel_shub There seems to be a NodeJS update that caused this: https://github.com/nodejs/node/issues/60704. I have added a workaround mentioned in this comment: https://github.com/nodejs/node/issues/60704#issuecomment-3529614006