Arch Linux User Repository

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.

Package confirmed fixed on my end

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.

@musta_ruhtinas That's because redis.service isn't symlinked to valkey.service, which will be fixed in the next release of the valkey package.

No frontend css issues for me. But I still have to override the server service in order to use it with valkey.

The patch below (reverting the changes to .gitignore from f4e0aad2c495) fixes the frontend css issues for me. I do not know why, someone else can do more investigating (also figure out which ignore is causing the issue)

diff --git a/.gitignore b/.gitignore
index dcec8d8..f66fce1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,7 +4,3 @@ admin1CodesASCII.txt
 admin2Codes.txt
 cities500.zip
 base-images/
-src/
-pkg/
-*.pkg.tar.zst
-LICENSES/

The official machine-learning/uv.lock from Immich was generated with Python v3.11, so it doesn't match Arch Linux's official Python (v3.13). All we need to do is delete the existing machine-learning/uv.lock and regenerate uv.lock using Arch Linux's Python with the uv lock command.

Also, you probably can't remove @img/sharp-libvips* just yet, but you can avoid depending on the system's libvips.

Uncommenting options=("!strip") did not fix the build on my end. The git checkout fix seems to work though.

Confirming @aliu's solution works for me, even without building in a clean chroot. I'm also very stumped as to why this would work...

Some users observe that the newest update breaks their webpages.

I don't know why, but here are some solutions people have found:

1. https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot . This is NOT the same as simply a manual makepkg -si!
2. git checkout 5888b9405f98 and then copying the newest PKBUILD and changelog file.

What if you build the newest version of this package but uncomment the "options" line?