Arch Linux User Repository

is it possible to ship pre-built package?

Upstream recommends using docker, for which they have pre-built images (that might also work with podman).

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 .

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.

@aliu, if you still need the bad build, https://random-hackery.net/immich-server-1.137.3-2-x86_64.pkg.tar.zst

I was having trouble with the frontend as well.

I rebased back to the 1.135.3 PKGBUILD (last version I had built), and from there changed the version to 1.137.3 and added the build-lock.json generation. That built successfully, and the frontend corruption was gone, without using a clean chroot.

Not sure what specific change between then and now is causing the issue, but maybe this data point will help...

That makes me curious! Could you send me the faulty package somewhere?

Spent a bit of time yesterday on this. Unfortunately I have more questions than answers. I diffed the two built packages. The CSS files are randomly named, but there was a size difference of about 100k with the package that built correctly. So the node generated CSS in the broken builds are definitely missing something. I tried building the package on three different machines to rule out a configuration issue. That said, here is what I tried:

Plain yay build: failed
switching versions of node (LTS, and main): no change
building by hand on a fresh VM (git clone and makepkg -si): failed
building in a fresh chroot: Success

Theoretically, the build by hand and the CHROOT should be identical, but they aren't, and I'm a bit stumped by that. If anyone needs a good build, follow the chroot build instructions here: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot. Its the only way I've seen to consistently get a good build.

I'll be traveling the rest of the week so I wont be able to dedicate more time to digging into it for a bit.

please keep us updated @CountMurphy!

per @musta_ruhtinas's suggestion I built the package using a clean chroot. Now its working perfectly. It looks like building with yay (which is how I built it before) might be the issue. I'll try to diff the clean build and yay built packages when I have time after work and see if I see the source of the problem

I do not experience the web front issues, immich behaves normally on all devices / browsers. If it helps, I build manually in a clean chroot. @CountMurphy: perhaps it may help to take a look at nginx/apache access and error logs, if available.

Browser Console log is blank, the network tools section show no errors downloading resources.

The journal log for immich pretty big, but nothing seems out of place: https://pastebin.com/7iZiuQQZ

postgresql looks normal as well:

Aug 04 23:08:22 harbinger systemd[1]: Starting PostgreSQL database server...
Aug 04 23:08:22 harbinger postgres[401387]: 2025-08-04 23:08:22.563 PDT [401387] LOG:  starting PostgreSQL 17.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 15.1.1 20250729, 64-bit
Aug 04 23:08:22 harbinger postgres[401387]: 2025-08-04 23:08:22.563 PDT [401387] LOG:  listening on IPv6 address "::1", port 5432
Aug 04 23:08:22 harbinger postgres[401387]: 2025-08-04 23:08:22.563 PDT [401387] LOG:  listening on IPv4 address "127.0.0.1", port 5432
Aug 04 23:08:22 harbinger postgres[401387]: 2025-08-04 23:08:22.563 PDT [401387] LOG:  could not bind IPv4 address "127.0.0.1": Address already in use
Aug 04 23:08:22 harbinger postgres[401387]: 2025-08-04 23:08:22.563 PDT [401387] HINT:  Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
Aug 04 23:08:22 harbinger postgres[401387]: 2025-08-04 23:08:22.571 PDT [401387] LOG:  listening on Unix socket "/run/postgresql/.s.PGSQL.5432"
Aug 04 23:08:22 harbinger postgres[401407]: 2025-08-04 23:08:22.592 PDT [401407] LOG:  database system was shut down at 2025-08-04 23:08:22 PDT
Aug 04 23:08:22 harbinger postgres[401387]: 2025-08-04 23:08:22.616 PDT [401387] LOG:  database system is ready to accept connections
Aug 04 23:08:22 harbinger systemd[1]: Started PostgreSQL database server.
Aug 04 23:08:23 harbinger postgres[401469]: 2025-08-04 23:08:23.001 PDT [401469] LOG:  PID 401037 in cancel request did not match any process

Also, what does the browser console say on the broken website?