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.

>=v1.91.0 requires pgvecto.rs extension of postgresql for search. For new and existing databases, the library needs to be loaded by adding the following to your /var/lib/postgresql/data/postgresql.conf:

shared_preload_libraries = 'vectors.so'

Or running the following command:

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

See upstream docs.

1.90.2-6 combines AUR packages immich and immich-cli packages, reflecting the approach now taken up-stream. immich (pkgbase) is now a split package with components immich-server and immich-cli - allowing each to be installed separately.

For those with immich-cli installed, it should be straight upgrade after building this package.

For those with immich installed, a normal system upgrade should automatically replace this with immich-server.

@hrdl thanks - should be sorted in 1.90.2-4

immich.conf mentions localhost:3003, which on IPv6-capable systems can resolve to ::1. This is not compatible with 0.0.0.0, which immich-machine-learning / gunicorn listens on.

Hi @DominikJasiok, I also maintain immich-cli as a separate package but haven't updated it since the CLI was brought into the main repository at v1.88.0. I'll look at either updating the separate package or bringing it into this one (as a split package). I'm keen to cater for the use-case where someone just wants to install the CLI without the server, i.e. to bulk upload photos from a desktop/laptop to a separate server.

I'll have a look at this after I've updated the package to the latest version v1.90.x released in the last 24hrs.

Hi, the latest AUR doesn't include the cli. It is possible to install it after with: npm i -g @immich/cli but maybe we could include it in the PKGBUILD

@pikl I've figured out what's my issue. I am not building in a chroot but on my desktop machine connecting remotelly over SSH. Poetry tries to use my gnome keyring because I am occassionally running gnome on that machine. I have worked it around by adding this just before poetry install. If it might be a good idea to also add it into the package, I don't really know. I guess for people not using clear chroot and not using poetry for their daily work this might be common.

export PYTHON_KEYRING_BACKEND=keyring.backends.fail.Keyring

I have found out about it here: https://github.com/python-poetry/poetry/issues/5250

@pvagner I don't think I've ever seen that. If you are not already, try building in a clean chroot? I use aurutils for this.

When building the package it hangs while installing python dependencies with poetry. Can you reproduce that or think about a possible fix / workaround?

@wabi now added these