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.

@agkphysics Apologies, I didn't with the previous message! Tried just now with extra-x86_64-build and it's still failed. Not sure if I've messed up somewhere this is the first time I've ever done something like this. My exact steps:

1. git clone https://aur.archlinux.org/zotero.git
2. installed yay -S devtools-git
3. tried with extra-x86_64-build -c it errored the first time failing to find lzo so had to yay -S lzo (which wasn't up to date, but updated successfully) and tried again.
4. ran extra-x86_64-build -c again and everything seemed to complete until the very end where it gave the following:

Success: [browserify] 4 files processed [3090ms]
Success: [copy] 67 files processed | 67 checked [3191ms]
Success: [js] 317 files processed | 329 checked [3414ms]
Success: [sass] 3 files processed | 55 checked [913ms]
Success: [sass] 0 files processed [124ms]
Success: [symlink] 1412 files processed | 1412 checked [3427ms]
Success: [symlink] 4 files processed | 4 checked [297ms]
Success: [cleanup] 0 files processed [0ms]
Success: [pdf-reader] 1 files processed | 1 checked [5402ms]
Success: [pdf-worker] 1 files processed | 1 checked [126922ms]
Success: [note-editor] 1 files processed | 1 checked [32682ms]
Total build time 126951ms

...

Checking PKGBUILD
Checking zotero-6.0.15-1-x86_64.pkg.tar.zst

...

==> Running checkpkg
error: target not found: zotero
==> WARNING: Skipped checkpkg due to missing repo packages

Have I missed some essential step?

Terminal's stdout is muuuch longer but I'm not sure if it is appropriate to post it all here.

@Feakster @Pippip19 I have updated the PKGBUILD to set the file protocol on a per-command basis, which seems to solve this problem.

@nomaly Have you tried with extra-x86_64-build?

Hi there,

My system is up to date (with yay -Syu)

I've attempted installing this but i'm getting build errors around the pdf-worker part:

Error: Error: Command failed: npm run build

...

npm ERR! code 1
npm ERR! path /home/user/.cache/yay/zotero/src/zotero-client/pdf-worker/pdf.js/node_modules/canvas
npm ERR! command failed
npm ERR! command sh -c -- node-pre-gyp install --fallback-to-build
npm ERR! make: Entering directory '/home/user/.cache/yay/zotero/src/zotero-client/pdf-worker/pdf.js/node_modules/canvas/build'
npm ERR!   SOLINK_MODULE(target) Release/obj.target/canvas-postbuild.node

...

[10:43:02] Try running: npm install
ERROR: "build:worker" exited with 2.

    at ChildProcess.exithandler (node:child_process:398:12)
    at ChildProcess.emit (node:events:527:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: 'npm run build',
  stdout: '\n' +
    '> pdf-worker@1.0.0 build\n' +
    '> run-s build:pdf.js build:worker\n' +
    '\n' +
    '\n' +
    '> pdf-worker@1.0.0 build:pdf.js\n' +
    '> sh scripts/build-pdfjs\n' +

...

I have nodejs-lts-gallium installed

@Feakster I was receiving the same errors and believe (temporarily) assigning the 'file' protocol an allow policy solved the issue: git config --global --add protocol.file.allow always I removed the entry generated in my ~/.gitconfig after the build succeeded.

Started getting errors on this during prepare(). The error says:

Submodule 'xpi/zotero-transfw' (https://github.com/egh/zotero-transfw.git) registered for path 'xpi/zotero-transfw'
Cloning into '/home/benjamin/.cache/paru/clone/zotero/src/zotero-build/xpi/zotero-transfw'...
fatal: transport 'file' not allowed
fatal: clone of '/home/benjamin/.cache/paru/clone/zotero/src/zotero-transfw' into submodule path '/home/benjamin/.cache/paru/clone/zotero/src/zotero-build/xpi/zotero-transfw' failed
Failed to clone 'xpi/zotero-transfw'. Retry scheduled
Cloning into '/home/benjamin/.cache/paru/clone/zotero/src/zotero-build/xpi/zotero-transfw'...
fatal: transport 'file' not allowed
fatal: clone of '/home/benjamin/.cache/paru/clone/zotero/src/zotero-transfw' into submodule path '/home/benjamin/.cache/paru/clone/zotero/src/zotero-build/xpi/zotero-transfw' failed
Failed to clone 'xpi/zotero-transfw' a second time, aborting
==> ERROR: A failure occurred in prepare().
    Aborting...
error: failed to build 'zotero-6.0.15-1': 
error: packages failed to build: zotero-6.0.15-1

I've had to make nodejs-lts-gallium a build requirement, due to a build error in the pdf-worker submodule. I've mentioned this on the Zotero dev mailing list.

But until this is fixed, you will need to install nodejs-lts-gallium or at least build in a chroot using

extra-x86_64-build

Upstream has now fixed the issue with zotero-standalone-build.

@Knecker I believe this is an upstream issue, as commit https://github.com/zotero/zotero-standalone-build/commit/e40273b282e1a904a4f51c1a7d2cfbd2a125160a reverted the LibreOffice extension submodule back to 2016.

I have filed an issue here: https://github.com/zotero/zotero-standalone-build/issues/102

In the meantime you could simply change the zotero-standalone-build checkout to commit 817b6e0d82e1a7234ebb8d32a56fb993f12feb1b:

"zotero-standalone-build::git+https://github.com/zotero/zotero-standalone-build.git#tag=817b6e0d82e1a7234ebb8d32a56fb993f12feb1b"

Strange. When installing the zotero-bin AUR repository https://aur.archlinux.org/packages/zotero-bin, everything works. When using this one here, there is a strange bug (?): "zotero libreoffice integration is incompatible" says the Zotero Extension Manager.

zotero-bin has been updated to 6.0.12.

However, the corresponding tag hasn't shown on github. Please keep an eye on it.

BTW, you may want to take a look at https://github.com/arch4edu/aur-auto-update to automatic update this package.