Arch Linux User Repository

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.

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 .

@Terrence You're correct! Should be fixed now. Sorry for the remiss.

While the server seems to build and run fine, the CLI doesn't seem to be built (i.e. no dist folder is generated or included in the package), which leads to:

$ immich
node:internal/modules/esm/resolve:274
    throw new ERR_MODULE_NOT_FOUND(
          ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/usr/lib/immich/cli/dist/index.js' imported from /usr/lib/immich/cli/bin/immich
    at ...
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///usr/lib/immich/cli/dist/index.js'
}

Node.js v24.9.0

The missing build step (to be done before deploy):

pnpm --filter @immich/cli build

If anybody like me has issues building the webui, try increasing the heap size node can use when building.

NODE_OPTIONS="--max-old-space-size=4096" yay -S immich-server

@pescepalla Vectorchord is listed as a dependency of this package that exists in the AUR, though?

The package won't pull vectorchord. It is necessary to install it separately.

@aliu confirmed. My immich-server.service is targeting redis.service, I didn't have any alias set up for redis, and I can start immich-server with no issue.

@aliu Working fine here. Updated without even noticing, thought I had an override in place :)

@musta_ruhtinas @caoticofanegas Valkey 8.1.4 has now been shipped. Can you confirm that immich starts correctly without manual intervention now?

While we're at it, I've decided that moving immich-machine-learning to a different PKGBASE was a bad idea. It's still gonna be a separate package but it'll use the same build steps after this package is accepted into Chaotic AUR where build times should no longer be an issue.