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: Could the media-directory rule in immich.tmpfiles use nonrecursive z instead of Z? With immich-server 3.1.0-1, tmpfiles delayed boot by 6m 2s scanning approximately 174k files/directories on mergerfs over HDDs. My local override points the rule directly at /mnt/immich, the target of /var/lib/immich, to avoid a symlink-related unsafe-path warning. After boot, the full tmpfiles dry run took 0.058s excluding that tree; the tree alone took 9.04s with warm caches. Changing its Z to z reduced the full dry run to 0.054s. I haven't rebooted since the change. Could recursive permission repairs be handled separately when needed, instead of scanning the whole library at every boot?

I'm unable to build the latest version:

==> Starting prepare()...
patching file server/src/services/database-backup.service.ts
Hunk #1 succeeded at 211 (offset 6 lines).
patching file server/src/services/database-backup.service.spec.ts
Hunk #1 succeeded at 279 (offset 2 lines).
patching file server/bin/start.sh
warn: This version of pnpm requires at least Node.js v22.13
warn: The current version of Node.js is v20.20.2
warn: Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.
node:internal/modules/cjs/loader:1031
      throw new ERR_UNKNOWN_BUILTIN_MODULE(request);
            ^

Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqlite
    at Module._load (node:internal/modules/cjs/loader:1031:13)
    at Module.require (node:internal/modules/cjs/loader:1289:19)
    at require (node:internal/modules/helpers:182:18)
    at ../store/index/lib/index.js (file:///usr/lib/node_modules/pnpm/dist/pnpm.mjs:16128:25)
    at __init (file:///usr/lib/node_modules/pnpm/dist/pnpm.mjs:15:56)
    at ../resolving/npm-resolver/lib/index.js (file:///usr/lib/node_modules/pnpm/dist/pnpm.mjs:27715:5)
    at __init (file:///usr/lib/node_modules/pnpm/dist/pnpm.mjs:15:56)
    at ../workspace/projects-graph/lib/index.js (file:///usr/lib/node_modules/pnpm/dist/pnpm.mjs:27853:5)
    at __init (file:///usr/lib/node_modules/pnpm/dist/pnpm.mjs:15:56)
    at ../workspace/projects-filter/lib/index.js (file:///usr/lib/node_modules/pnpm/dist/pnpm.mjs:43762:5) {
  code: 'ERR_UNKNOWN_BUILTIN_MODULE'
}

Node.js v20.20.2
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: immich-exit status 4

I'm currently running immich-server 2.7.5-1 successfully, this is just while trying to update. Maybe a dependency I'm missing or something?

@aliu I was not aware of the official recommendation, was hit with the problem today as I had -iron installed. Still, perhaps there should be at least a post-upgrade warning, if a specific version can not be excluded.

I'm not comfortable adding that... I'm not willing to always test this against Jod and the only thing upstream mentions is 24.15.0 in their nvmrc. I feel like adding that would imply upstream supports/targets 22+ when 24 is all they claim to support.

perhaps a nodejs>=22 should be in place, as the 3.1 version no longer works properly with nodejs-lts-iron. Did not run into any issues yet, however, with -jod and -krypton.

@zkm2fw Thanks, does this look good?

Please append echo -e "\033[0m" to post_upgrade() in immich-server.install.

The \033[1m in the last \033[1m: immich-machine... should be cancelled.

https://aur.archlinux.org/cgit/aur.git/tree/immich.sysusers?h=immich

u   immich  -   "immich user"   /var/lib/immich /usr/bin/nologin
m   immich  redis

Package extra/valkey comes with neither user "redis" nor group "redis" anymore.

After installing extra/valkey and aur/immich-server, there is only a dangling group "redis" without a user "redis".

Modify immich.sysusers, either one of two options:

(1) Add immich to group "valkey", completely remove any reference to group "redis".

(2) Add immich to both solid group "valkey" and dangling group "redis". Keep both "aur/redis" fans and "extra/valkey" fans happy.

--- why? ---

current id immich

uid=946(immich) gid=946(immich) groups=946(immich),966(redis)

With the following /etc/valkey/valkey.conf, a sudo gpasswd -a valkey immich is required, otherwise immich cannot communicate with the socket.

unixsocket /run/valkey/valkey.sock
unixsocketgroup valkey
unixsocketperm 660

With the following /etc/valkey/valkey.conf, a sudo gpasswd -a redis valkey is required, otherwise valkey fails to create valkey.sock with group ownership "redis", because user valkey has no seat in group redis.

unixsocket /run/valkey/valkey.sock
unixsocketgroup redis
unixsocketperm 660

Please modify immich.sysusers, to ensure at least one scenario works ootb w/o manual gpasswd-ing.

ughhhh I really thought I'd committed that this time.

Your checksums need to be updated for this release.