Package Details: immich-server 1.135.3-1

Git Clone URL: https://aur.archlinux.org/immich.git (read-only, click to copy)
Package Base: immich
Description: Self-hosted photos and videos backup tool
Upstream URL: https://github.com/immich-app/immich
Keywords: backup photos
Licenses: MIT
Conflicts: immich
Replaces: immich
Submitter: wabi
Maintainer: aliu
Last Packager: aliu
Votes: 16
Popularity: 0.89
First Submitted: 2022-12-30 11:41 (UTC)
Last Updated: 2025-06-30 02:49 (UTC)

Pinned Comments

aliu commented on 2025-06-30 02:49 (UTC)

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.

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.

pikl commented on 2025-01-25 21:54 (UTC) (edited on 2025-01-26 08:23 (UTC) by pikl)

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

Latest Comments

1 2 3 4 5 6 .. 13 Next › Last »

aliu commented on 2025-06-30 02:49 (UTC)

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.

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.

aliu commented on 2025-06-29 01:56 (UTC)

hola soy vuestro mantenedor nuevo

I'm planning to migrate to vectorchord instead of pgvecto.rs in the next update. This probably requires manual intevention, which could be automated if I knew your postgresql home directory and password, which means it can't be automated. I think this should be how the next version of this AUR package should be released as this AUR package has not been updated in a month, and releasing a long-awaited update is a great way for users to pay attention and clue them in to needed manual intervention, I think. I'll figure out the best way to approach this as soon as possible.

aliu commented on 2025-06-20 03:09 (UTC)

I'm planning to adopt the package. Pikl disowned after I filed the orphan request, but we still have to wait another week before the request processors remove wabi from the list of maintainers as well.

musta_ruhtinas commented on 2025-06-19 14:50 (UTC)

@jettscythe it is working just fine if you change the version in the PKGBUILD to current one, even with vectorchord 0.4.2, which is now supported

jettscythe commented on 2025-06-19 12:21 (UTC)

upstream is now at v1.135.0

CountMurphy commented on 2025-05-27 20:30 (UTC)

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.

musta_ruhtinas commented on 2025-05-24 13:51 (UTC)

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.

hrdl commented on 2025-04-04 09:33 (UTC)

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.

ChuckHL commented on 2025-03-31 13:37 (UTC)

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

pikl commented on 2025-03-30 13:45 (UTC)

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

1 2 3 4 5 6 .. 13 Next › Last »