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.

Oh, you're right, that is what you say it is. I'll look into the documentation for the flag, and if it doesn't seem to have adverse effects, I'll merge it.

https://aur.archlinux.org/pkgbase/immich?O=20#comment-1047390 has one possible error. It varies depending on when exactly the OOM occurs.

Could you show me the lines of console output? Maybe the .gitignore thing somehow contributed to running out of memory and I'd need to compare to the pnpm output to check if that's the case.

(Also, I haven't seen people comment on this. I've only seen the comments on the same site-breaking issue that was fixed after the .gitignore change.)

Yes, it's unrelated to the .gitignore issue. Multiple folks have commented on this here.

There is console output that indicates the build failure, but it's easy to miss or dismiss. I don't see the benefit of keeping the --force flag. A minimal diff between PKGBUILD and upstream is of course desirable, but docker compose and a PKGBUILD are entirely different environments, so some deviations should be expected.

Are you sure that's the cause of the problem and not the .gitignore lines that were removed? Is there a way to have output in the console when the memory issue is triggered?

Also, the --force flag comes from the upstream Dockerfile install instructions.

Several folks here over time have reported running into OOM issues during build that only manifest as broken web UI after installation. I think applying this patch would prevent this without introducing drawbacks for other systems:

diff --git a/PKGBUILD b/PKGBUILD
index 465ea12..a38bdc9 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -96,6 +96,8 @@ prepare() {

 # instructions adapted from relevant Dockerfile-s
 build() {
+       export NODE_OPTIONS=--max-old-space-size=4096
+
        cd "${srcdir}/${pkgbase}-${pkgver}"
        make clean
        for dir in machine-learning/.venv/ output/
@@ -119,7 +121,7 @@ build() {
     SHARP_FORCE_GLOBAL_LIBVIPS=true pnpm --filter immich --frozen-lockfile --prod --no-optional deploy output/server-pruned

        # build sdk and web
-       SHARP_IGNORE_GLOBAL_LIBVIPS=true pnpm --filter @immich/sdk --filter immich-web --frozen-lockfile --force install
+       SHARP_IGNORE_GLOBAL_LIBVIPS=true pnpm --filter @immich/sdk --filter immich-web --frozen-lockfile install
     pnpm --filter @immich/sdk --filter immich-web build

     # build CLI

I can't reproduce nor find any mention of glycin in the upstream repo; what's "on alarm"? Could you send the error message for when glycin is missing?

(omg it's notfire from hits hiiii)

glycin is also required for this to build now (at least for me on alarm)

Thanks for everyone's assistance, I was able to get the system up and running utilizing @hrdl's vectorchord-1.0 version patch for immich-server, modifying immich-server's PKGBUILD to work with v1.0, then I picked vectorchord-immich-bin's PKGBUILD as the base that I modified to install vectorchord-1.0 and bam, it all came to life.

Hopefully upstream adopts v1.0 formally soon but if they drag feet it might be worth it to remove the version deps for vectorchord and throw caution to the wind.

PS- This wasn't an upgrade, it was a fresh install, this is my first time ever test driving the product. Thanks!

Okay, so you upgraded to PSQL 18 from 17. Check out my pinned comment. The PostgreSQL upgrade instructions were also in the warning message when you first upgraded to 18 from 17, so if you still have the relevant Pacman logs you can check there too. In general, the information pacman prints during the installing {package_name}... are often very useful: https://wiki.archlinux.org/title/System_maintenance#Act_on_alerts_during_an_upgrade