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.

Looks like V1.133.0 switched from pgvecto to VectorChord, but the current PKG files do not have that listed as a dependency. Keeping pgvecto will work for now, but a future release will remove support for it.

Latest (1.133) version introduced migration from pgvecto.rs to vchord database extension. For it to work, pgvector is also needed. Similarly to vectors, vchord must be preloaded via the postgres config.

Also, since valkey is now the default, perhaps the service file should reflect that as well.

Only machine-learning/immich_ml/log_conf.json is needed since 1.131, as immich_ml is now part of the virtual environment. Alternatively, /opt/immich-machine-learning/venv/lib/python3.12/site-packages/immich_ml/log_conf.json could be used directly.

I'm new to this and I'm having a problem installing the app. Issue is really a dependency.

Immich > pgvecto.rs>clang16>llvm16

When compiling, I get the error: signature not found

Thanks hrdl - much appreciated. I've used your patch verbatim for now!

immich 1.130 switched to uv, which changes the tooling a bit. python 3.13 is not supported yet as some of the dependencies are pinned to older versions, but python 3.12 still works. I'm sure there's room for improvement, but https://paste.sr.ht/~hrdl/a57fb8dfdb3a292f9181b78daa9e29a415ff510f is at least a start to avoid duplicate work.

Running command "/home/simona/.rustup/toolchains/nightly-2024-01-14-x86_64-unknown-linux-gnu/bin/cargo" "build" "--release" "--features" "pg17" "--no-default-features" "--message-format=json-render-diagnostics" error: none of the selected packages contains these features: pg17, did you mean: pg12, pg13, pg14, pg15, pg16?

I'm unable to start my immich server due to the following error around the upload/encoded-video/.immich file

Jan 27 21:00:07 desktop immich-server[1494334]: [Nest] 1494334  - 01/27/2025, 9:00:07 PM     LOG [Api:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}
Jan 27 21:00:07 desktop immich-server[1494334]: [Nest] 1494334  - 01/27/2025, 9:00:07 PM   ERROR [Api:StorageService] Failed to write /mnt/storage/Servers/immich-media/upload/encoded-video/.immich: Error: EROFS: read-only file system, open '/mnt/storage/Servers/immich-media/upload/encoded-video/.immich'

I'm running a ZFS pool that these files are stored on. It was working at install, but after an update a month or so ago, it hasn't worked. I also had some trouble with the postgres update, and I've reinstalled it a couple times, so maybe one of my configs got out of wack, but I'd be happy to see if there's any ideas as to what might be causing this.

EDIT: I had to update the service file with the new path with the following change using systemctl edit immich-server.service:

[Service]
ReadWritePaths=/tmp /var/tmp /mnt/storage/Servers/immich-media/upload

Upgrading to postgresql-17 is awkward because of pgvecto.rs if you have been using 0.2.0 as provided by AUR package pgvecto.rs-immich. If you have been using 0.3.0 as provided by AUR package pgvecto.rs-immich-bin then these extra steps are likely not required and I suggest the wiki instructions for upgrades for major version increments of postgresql are followed.

If you would like to stick at postgresql-16 please add the following to pacman.conf:

IgnorePkgs = postgresql postgresql-libs

Following the manual dump and reload in the wiki does appear to work, with a few extra steps to consider the pgvecto.rs upgrade.

Starting point is postgresql-old-upgrade installed with pgvector.rs-0.2.0. Symlink the installation outputs of pgvecto.rs into the directories used by the parallel installation of postgresql-old-upgrade.

ln -s /usr/share/postgresql/extension/vectors.control /opt/pgsql-16/share/extension/vectors.control
ln -s /usr/share/postgresql/extension/vectors--0.2.0.sql /opt/pgsql-16/share/extension/vectors--0.2.0.sql
ln -s /usr/lib/postgresql/vectors.so /opt/pgsql-16/lib/vectors.so

Then perform the database start (/opt/psql-16/bin/pg_ctl .. start), "dump" (pg_dumpall...) and database stop (/opt/psql-16/bin/pg_ctl .. start) steps in the wiki.

Upgrade to postgresql-17 and pgvecto.rs-0.3.0 (provided by pgvector.rs-immich-bin). Clear out /var/lib/postgresql/data then initialise the database (initdb...) as per the wiki.

Start the service using systemctl start postgresql and install the pgvecto.rs using the following command:

psql -c 'ALTER SYSTEM SET shared_preload_libraries = "vectors.so"'

Finally restart the postgresql service and perform the reload (psql...) steps in the wiki.

EDITED: Various clarifications

Just removed my forced downgrade, and had postgresql-old-upgrade installed. This fixed the upgrade issue I had before. It handled the upgrade process on the fly when upgrading :) All good now.

[EDIT] Seems like it didn't work after a reboot. Still version error, and run into same issue as @CountMurphy when trying to upgrade the database. Postgresql is a but of a nightmare to work with it seems.