Arch Linux User Repository

is it possible to ship pre-built package?

Upstream recommends using docker, for which they have pre-built images (that might also work with podman).

PostgreSQL 18 is coming to the Arch repos. Before upgrading, backup the files for vectorchord and pgvector somewhere, and then follow https://wiki.archlinux.org/title/PostgreSQL#Upgrading_PostgreSQL instructions. (In the next release, I'll also update the postinstall message to recommend changing postgresql.conf instead of doing ALTER SYSTEM SET.)

Also, you may find yourself updating VectorChord in this process. When doing so, remember to follow the migration steps at https://docs.immich.app/administration/postgres-standalone/#updating-vectorchord .

immich-web (localhost/immich-server:2283) used to be broken for some users of this package.

As @yparitcher also noticed, this was most likely caused by the following additions to .gitignore from f4e0aad2c495, which have since be reverted:

src/
pkg/
*.pkg.tar.zst
LICENSES/

The reason—for both this change sometimes and unpredictably breaking the build, and builds under a clean chroot still working—is unknown. I meant to investigate this on 2025-08-19 while updating the package but called it a day due to the unpredictability and long time of building. Help with figuring out why this happened would be greatly appreciated.

You may notice pacman refuse to upgrade this package, saying warning: cannot resolve "vectorchord", a dependency of "immich-server".

This is due to required manual intervention within the immich server database.

Newer versions of immich server have deprecated pgvecto.rs in favor of vectorchord.

Before updating from 1.133.1 or older, please follow steps 1 and 2 of the manual migration steps (should be the second dropdown) at https://immich.app/docs/administration/postgres-standalone/#migrating-to-vectorchord and uninstall pgvecto.rs.

Remember to remove references to "vectors.so" (which is shipped by pgvecto.rs) in shared_preload_libraries before pgvecto.rs in uninstalled. (For vectorchord to work, you'll need to add "vchord.so" to shared_preload_libraries after the upgrade as well.)

After that, you may upgrade this package. Please remember to follow steps 4 and 5 of the manual migration steps after the upgrade is finished to prevent data loss.

I don't know much about the error, but try https://stackoverflow.com/questions/42308879/how-to-solve-npm-error-npm-err-code-elifecycle .

Installation fails:

==> Starting build()...
Importing packages to virtual store
Already up to date
Progress: resolved 2340, reused 2333, downloaded 0, added 2340, done
node_modules/.pnpm/sharp@0.34.5/node_modules/sharp: Running install script...
 ELIFECYCLE  Command failed.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: immich-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
immich-server - exit status 4

Any advice?

@musta_ruhtinas Interestingly this doesn't reproduce when I just remove npm instead of using an entire chroot. Perhaps a common dependency... This might be related to the PKGBUILD's differences from the Dockerfile in treatment of sharp.js and libvips but I don't have the time to investigate this right now.

@AID Will do when I figure the above issue out!

This fixes the three dependency:

diff --git a/immich-2.4.1/web/package.json b/immich-2.4.1/web/package.json
index 9addfb6..040bee0 100644
--- a/immich-2.4.1/web/package.json
+++ b/immich-2.4.1/web/package.json
@@ -62,7 +62,8 @@
     "svelte-persisted-store": "^0.12.0",
     "tabbable": "^6.2.0",
     "thumbhash": "^0.1.1",
-    "uplot": "^1.6.32"
+    "uplot": "^1.6.32",
+    "three": "^0.170.1"
   },
   "devDependencies": {
     "@eslint/js": "^9.36.0",

Only saw your recent changes now.

[[ $(grep MemTotal /proc/meminfo | awk '{print $2}') > $(expr 5 * 1024 * 1024) ]]

Not sure whether this check is really useful, I think compilation is guaranteed to fail with less memory, but the comparison operator is string based, you meant to use -gt.

$(expr …) can just be replaced with $((…)) and no need for escaping *.

cannot build in a clean chroot unless adding npm to makedepends

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 1a29634 chore: libvips 8.17.3 (#291)
==> Starting build()...
Importing packages to virtual store
Already up to date
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 2340, reused 0, downloaded 92, added 43
Progress: resolved 2340, reused 0, downloaded 495, added 383
Progress: resolved 2340, reused 0, downloaded 1002, added 833
Progress: resolved 2340, reused 0, downloaded 1512, added 1515
Progress: resolved 2340, reused 0, downloaded 1842, added 1814
Progress: resolved 2340, reused 0, downloaded 2086, added 2038
Progress: resolved 2340, reused 0, downloaded 2181, added 2062
Progress: resolved 2340, reused 0, downloaded 2329, added 2327
Progress: resolved 2340, reused 0, downloaded 2333, added 2340, done
.../sharp@0.34.5/node_modules/sharp install$ node install/check.js || npm run build
.../bcrypt@6.0.0/node_modules/bcrypt install$ node-gyp-build
.../sharp@0.34.5/node_modules/sharp install: sh: line 1: npm: command not found
 ELIFECYCLE  Command failed.

@AID I get '[vite-plugin-sveltekit-compile] [vite]: Rollup failed to resolve import "three" from "/home/aliu/Documents/immich/src/immich-2.4.1/node_modules/.pnpm/@photo-sphere-viewer+markers-plugin@5.14.0_@photo-sphere-viewer+core@5.14.0/node_modules/@photo-sphere-viewer/markers-plugin/index.module.js".'

This error disappears when I add the --force flag back to line 127. I suspect this may be due to incorrect specification of optional dependencies in immich. But I don't have the time right now to investigate this properly, so I've added the --force flag back.

That's interesting. Since that seems like an issue with the helpers, I'll add an investigation to my todo list.

Both vectorchord>=0.3 and vectorchord<1 are listed as two separate entries in the depends array, and it seems that AUR helpers treat them as two different dependencies. paru install two packages for vectorchord, while yay prompts the user twice to choose packages.

accidentally pushed a dev version in the commit that added hatchling to makedeps, hence the comical pkgrel number

... please ignore-