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.

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).

It is supposed to be -gt. The default max-old-space-size is ~1.5G; the lines increase it to 4G.

Ok, it managed to build successfully. I can tell that 2GB ram + 1GB swap is sufficient.

There is an error on line 119 which leads to OOM errors: there should be -lt, not >.

Currently, lines 119-121 read as: if system has more than 5GB ram, limit nodes max-old-space-size to 4G (ignoring that bash syntax issue). Supposed to be: if system has less than 5GB ram, force nodes max-old-space-size to 4G.

This is a quite old problem -- I remember giving up building a year ago, I thought 10GB swap was not enough.

The escaping is not needed when using $(()) is what I meant. It's a bash builtin, so should generally be preferred

Thanks for the advice. Will try to play with that.

BTW is it possible to ship pre-built package?

Hmm, I thought I'd committed that. Apparently I forgot to while investigating the three thing. Currently I'm making sure the patch to package.json doesn't cause any weirdness of being out-of-lockstep with the lockfile and then I'll commit both.

(Also, for what it's worth, the escaping was needed if I use $(expr ) instead of $(()).)

As mentioned in https://aur.archlinux.org/packages/immich-server#comment-1052676, the condition is broken. You need to use -gt instead of >.

If this causes the built immich-web to break, you could try changing line 120 to an even higher value.

now it crashes with out of memory during UI build:

web build$ vite build
│ [dotenv@17.2.3] injecting env (0) from .env -- tip: ⚙️  enable debug logging with { debug: true }
│ vite v7.3.0 building ssr environment for production...
│ transforming...
│ ✓ 2348 modules transformed.
│ rendering chunks...
│ [dotenv@17.2.3] injecting env (0) from .env -- tip: ✅ audit secrets and track compliance: https://dotenvx.com/ops
│ [dotenv@17.2.3] injecting env (0) from .env -- tip: 🔐 encrypt with Dotenvx: https://dotenvx.com
│ vite v7.3.0 building client environment for production...
│ transforming...
│ <--- Last few GCs --->
│ [112244:0x558609727000]    92334 ms: Scavenge (during sweeping) 970.9 (980.9) -> 970.6 (981.9) MB, pooled: 0.0 MB, 9.51 / 0.00 ms (average mu = 0.406, current mu = 0.362) alloca…
│ [112244:0x558609727000]    93181 ms: Mark-Compact (reduce) 974.2 (984.1) -> 972.9 (982.4) MB, pooled: 0.0 MB, 463.66 / 0.00 ms (+ 259.5 ms in 50 steps since start of marking, bi…
│ FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
...

just watched the process closely:

• swap is not used at all, but this is definitely an OOM -- core dumper process is executed and node is killed with SIGABRT
• build process continues after this failure

Installing npm resolved ELIFECYCLE error. It seems I got same issue as in https://aur.archlinux.org/pkgbase/immich#comment-1052460