Arch Linux User Repository

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

From v1.111.0, this package does not build with nodejs < v20.

@Mars160, Interesting. I thought systemctl edit is just other way to edit files without knowledge of their location. But as I now understand, this is just for adding something to service file, not removing, isn't it?

@ksj

Maybe you want to use

# systemctl edit immich-server

to create an override file to disable the immich-machine-learning.service?

you still haven't removed nginx from package_immich-server() required dependencies.

Also, I understand for someone can have convenience run other services too: BindsTo=immich-microservices.service immich-machine-learning.service After=immich-microservices.service immich-machine-learning.service But I don't use machine learning in immich (disable in config and web), so I don't even run them. They take only more ram, when used. So, after every new installed package I have to stop them, because they are useless for me. Can you remove this systemd dependency too?

@ksj of course - it was the intention only to provide nginx config as an example so it should be an optional dependency. Bumped to v1.98.2-2 for this.

Can you put nginx to optional dependencies? It is not needed. In my case I'm using nginx on separate server and using ssh forwarding from other private server, where is immich running.

use rustup and not rust :-(

Apologies I haven’t been able to look at packaging v1.93.3 due to combination of failed home broadband and work commitments. Thanks @hrdl for the patch - should have time later this week to look into it.

I'm testing 1.93.3. Here's my patch: https://paste.debian.net/hidden/bc63f6ed/

How to change the that immich-server run with? I want immich to manage the pictures in my nextcloud.

My nextcloud is running with ‘nextcloud’. So how can I run immich with nextcloud?

I tried to override the service file to change User and Group to nextcloud, and change ReadWritePaths to 755 directory. But It said that Immich have no permission to create upload/library.

After chmod to 777, I found immich created all directories with immich not nextcloud.

Anybody experiencing issues with photo previews (thumbnails and the smaller version served when clicked on) are black and white? https://github.com/immich-app/immich/issues/6046