Upstream maintainer say it's safe to use Python 3.12 now *. We may simply patch pyproject.toml to use Python 3.12 before them remove the constraint.
edit: python version constraint has been removed on main branch
| 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 (command-line client) |
| Upstream URL: | https://github.com/immich-app/immich |
| Keywords: | backup photos |
| Licenses: | AGPL-3.0-only |
| Submitter: | wabi |
| Maintainer: | aliu |
| Last Packager: | aliu |
| Votes: | 25 |
| Popularity: | 2.43 |
| First Submitted: | 2022-12-30 11:41 (UTC) |
| Last Updated: | 2026-07-18 21:47 (UTC) |
« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 33 Next › Last »
Upstream maintainer say it's safe to use Python 3.12 now *. We may simply patch pyproject.toml to use Python 3.12 before them remove the constraint.
edit: python version constraint has been removed on main branch
This is now a real problem as the client will logout and refuse to login with mismatched version - if you don't have time (which is understandable) can you add me so I can at least update it and get it working again?
Versions from 1.106 renamed a few environment variables:
SERVER_PORT, MICROSERVICES_PORT, and MACHINE_LEARNING_PORT were renamed to IMMICH_PORTHOST and MACHINE_LEARNING_HOST were renamed to IMMICH_HOSTI also found that i had to specify MACHINE_LEARNING_CACHE_FOLDER. I opted for /var/cache/immich added via CacheDirectory=immich directive in immich-machine-learning.service
Hope it helps with updating!
For v1.103 DB_HOSTNAME needs to be set to in immich.conf, as its default value changed from localhost to database: https://github.com/immich-app/immich/commit/7ea539b753b1993cd0735db408e5954288bf6b68
Upgrade to python 3.12 breaks immich-machinelearning. v1.102.3-3 adds version dependency for either python 3.10 or python 3.11. Note that python 3.11 is available on the AUR and can be installed alongside the default 3.12 but build appears broken at the moment. See python311 for a workaround.
pgvecto.rs-immich exists for the occurrence when the required version for immich is different to the latest release from upstream. At the moment both are at the same version but this hasn't been the case in the past. The dependency is defined with a version pgvecto.rs=0.2.0, both pgvecto.rs and pgvecto.rs-immich can provide that dependency at the moment.
And is there needed pgvecto.rs or pgvecto.rs-immich package as dependency? If pgvecto.rs-immich, why it is not as dependency? I'm using build from docker too and this is confusing, what to install. It always choose pgvecto.rs as it is in dependency.
@ksj orc is included as dependency due to liborc dep in the upstream Dockerfile. I've removed it completely in 1.101.0-2 and it builds and runs OK.
I was checking security of my server and I have found that immich-server is dependent on orc package (compiler). Is it necessary to have it as dependency or can it be moved under make dependency?
Also, is there needed pgvecto.rs or pgvecto.rs-immich package as dependency?
yes... fixed. thx
Pinned Comments
aliu commented on 2026-01-17 21:44 (UTC) (edited on 2026-01-17 21:46 (UTC) by aliu)
Upstream recommends using docker, for which they have pre-built images (that might also work with podman).
aliu commented on 2025-10-25 02:49 (UTC)
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 .
aliu commented on 2025-08-21 15:21 (UTC)
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:
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.
aliu commented on 2025-06-30 02:49 (UTC) (edited on 2025-07-01 16:35 (UTC) by aliu)
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.1or 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.