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.

Hi everyone, sorry I was out for a few days, and thanks for your comments. I think I messed up the vectorchord part, so up_upgrade failed miserably. Anyway, I changed the machine learning model a month ago or so, so immich had to rebuild everything again and it was't much of a pain, so I think I'll just try and do it again with a new db. I'll keep you posted if I find anything interesting to improve the package.

Thanks again!

Note that dropping a table means you delete all of its data, and to recreate the database you would need to effectively reupload everything. I recommend using the pg_upgrade instructions I linked.

@caoticofanegas, I'd drop the table with sudo -u postgres dropdb databaseName. Then just make sure you got vectorchord for postgres 18 installed. Recreate the empty database and you should be good to go.

@CountMurphy As you wish. breaks down and cries /j

@hifiboombox I also recommend CountMurphy's solution as the simplest, but to fix the issue with the systemd service, you would simply add the RAID directory to ReadWritePaths in immich-server.service.

@aliu, cities500.zip is failing the checksum again. Might need to push it 5 times this time to fully alleviate said sins :p

@hifiboombox I have the same setup.

I just symlinked /var/lib/immich/upload to my raid. Problem solved.

How can I change the upload path from the default /var/lib/immich/upload to somewhere else? I have a RAID-Z array that I want to keep my photos on. I've made the following modifications:

• changed the IMMICH_MEDIA_LOCATION key in /etc/immich.conf
• given proper permission with chmod and chown to my new path
• changed the ReadWritePaths key of immich-server.service

But the systemd unit still complains about being unable to write to my new path. I feel like this has something to do with all the "protection" settings in immich-server.service. Anyone have any idea how to do this?

Have you tried the instructions I've pinned?

I really effed up my database with the postgres update. I don't know what I did wrong, but well, I've figured out I might as well start up fresh and rebuild the whole database from scratch, I still have a backup of all my pictures and videos. Can anyone help me to get rid of the old db and build it back with postgres 18?

Building now, check seemed to pass