Arch Linux User Repository

@dhruvasambrani Thank you!

@mkurz thank you for catching these errors, the changes have been made

This package has flaws:

• It is missing the aarch64 checksum (sha256sums_aarch64).

• The checksums are generated incorrectly: Both sha256sums_x86_64 and sha256sums_i686 contain the same checksum. This is because when you run updpkgsums (or makepkg -g) the sources which get downloaded use the same filename. This is because CARCH always points to the same architecture:

source_x86_64=("Zotero-${_pkgver}_linux-${CARCH}.tar.xz
source_i686=("Zotero-${_pkgver}_linux-${CARCH}.tar.xz

So what happens is the first file gets downloaded and saved. For the next architecture(s) the download(s) gets skipped because for makepkg the file exists already - and calculcates the checksum for that next architecture(s) from the wrong file. So the solution is to NOT use the ${CARCH} variable in the source_* fields.

• In the update script the *.tar.xz files are not cleaned up.

• The prepare() function fails for the arm64 package from Zotero. If you download and unpack the Zotero arm64 package you will see it gets extracted into an *-arm64 folder. But CARCH in Arch Linux is aarch64. By just renaming the extracted folder we can easily fix this problem.

I fixed all of those problems in my zotero-beta-bin-fix_architectures branch:

• https://github.com/mkurz/aur/tree/zotero-beta-bin-fix_architectures

Please pull in my changes into this AUR:

• Diff to this AUR repo: https://github.com/archlinux/aur/compare/zotero-beta-bin...mkurz:aur:zotero-beta-bin-fix_architectures?expand=1
• The commit: https://github.com/archlinux/aur/commit/46766f99577dc60ec65be6f6574da784c95e8688
• The commit as patch: https://github.com/archlinux/aur/commit/46766f99577dc60ec65be6f6574da784c95e8688.patch
• The commit as diff: https://github.com/archlinux/aur/commit/46766f99577dc60ec65be6f6574da784c95e8688.diff

Instead of applying a patch or diff file you can also clone my repo and merge my zotero-beta-bin-fix_architectures branch.

Thank you!

I couldn't reopen the application after updating. /usr/lib/zotero/zotero: line 20: /zotero-bin: File or directory not found. Yesterday, August 9th, 2023, they officially released Zotero 7, so I suppose they changed the names to drop the 'beta' label. Now available: Zotero 7 - Zotero Forums

➜  ~ zotero
/usr/bin/zotero: line 20: /zotero-bin: No such file or directory

After update, there is something wrong in the path of the executable file

The last version of the package does not work properly as the patch does not apply correctly.

Here the patch i made to make it work

diff --git a/PKGBUILD b/PKGBUILD
index 092b091..6c47f08 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -22,7 +22,7 @@ depends=(
 source=('zotero-absolute-path-fix.sh')
 source_x86_64=("Zotero-${_pkgver}_linux-${CARCH}.tar.bz2::https://download.zotero.org/client/beta/${_pkgver//+/%2B}/Zotero-${_pkgver//+/%2B}_linux-x86_64.tar.bz2")
 source_i686=("Zotero-${_pkgver}_linux-${CARCH}.tar.bz2::https://download.zotero.org/client/beta/${_pkgver//+/%2B}/Zotero-${_pkgver//+/%2B}_linux-x86_64.tar.bz2")
-sha256sums=('884266c2216fc5042ec5728424c7a92fcf61d961071d74e925d90445658f416f')
+sha256sums=('38846fde4b952be354323ba508919f18cf7f399ed72f4a432f67cb5742571ce0')
 sha256sums_x86_64=('2f4d7866121de5d13acaebd37c855c6f294ccf473b80f94d58ad63fa5db036c0')
 sha256sums_i686=('2f4d7866121de5d13acaebd37c855c6f294ccf473b80f94d58ad63fa5db036c0')

diff --git a/zotero-absolute-path-fix.sh b/zotero-absolute-path-fix.sh
index 6cf25b7..c81b1a0 100644
--- a/zotero-absolute-path-fix.sh
+++ b/zotero-absolute-path-fix.sh
@@ -1,7 +1,7 @@
 #! /bin/sh

 sed -E "s;^CALLDIR.*$;;" -i zotero
-sed -E "s;^\"\$CALLDIR.*;exec \"/usr/lib/zotero/zotero-bin\" -app \"/usr/lib/zotero/app/application.ini\" \"\$@\";" -i zotero
+sed -E 's;^"\$CALLDIR.*;exec "/usr/lib/zotero/zotero-bin" -app "/usr/lib/zotero/app/application.ini\" "$@";'  -i zotero
 sed -E "s;^Exec=.*$;Exec=/usr/lib/zotero/zotero -url %U;" -i zotero.desktop

The latest version is Zotero-7.0.0-beta.95+694ccecf4 at 2024.07.06.

this package is outdated for one month, @qubidt could you please update it?