Package Details: immich-cli 1.131.3-2

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
Licenses: MIT
Submitter: wabi
Maintainer: wabi (pikl)
Last Packager: pikl
Votes: 14
Popularity: 0.60
First Submitted: 2022-12-30 11:41 (UTC)
Last Updated: 2025-04-03 19:10 (UTC)

Pinned Comments

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

pikl commented on 2024-08-05 09:52 (UTC)

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

Latest Comments

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

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!

hrdl commented on 2025-03-28 21:58 (UTC)

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.

simona commented on 2025-03-27 22:05 (UTC)

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?

LandonDeam commented on 2025-01-28 02:28 (UTC) (edited on 2025-01-28 02:46 (UTC) by LandonDeam)

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

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

zynex commented on 2025-01-18 15:30 (UTC) (edited on 2025-01-19 10:33 (UTC) by zynex)

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.

CountMurphy commented on 2025-01-13 21:11 (UTC) (edited on 2025-01-14 06:12 (UTC) by CountMurphy)

Has anyone got the upgrade to work? I've updated the pgvecto.rs-immich-bin for postgres 17, copied the old vectors.so into /opt/pgsql-16/lib, but when I run pg_upgrade I get

pg_restore: error: could not execute query: ERROR: could not find function "_vectors_vecf16_operator_cosine_wrapper" in file "/usr/lib/postgresql/vectors.so"

Never had to upgrade postgres before, so might be missing something basic?

EDIT: Update was successful using the manual dump and reload method

Weby commented on 2025-01-13 07:10 (UTC)

@zynex pgvecto.rs-immich-bin has been updated a few hours ago and now works with postgres v17.

Mind that if you're using that package, you need the vectors extension, not the vector extension. Slight difference.