AUR (en) - immich

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: immich-cli 2.3.1-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/immich.git (read-only, click to copy)
Package Base:	immich
Description:	Self-hosted photos and videos backup tool
Upstream URL:	https://github.com/immich-app/immich
Keywords:	backup photos
Licenses:	AGPL-3.0-only
Submitter:	wabi
Maintainer:	aliu
Last Packager:	aliu
Votes:	20
Popularity:	1.00
First Submitted:	2022-12-30 11:41 (UTC)
Last Updated:	2025-11-25 23:50 (UTC)

Dependencies (6)

nodejs (nodejs-git^AUR, python-nodejs-wheel^AUR, nodejs-lts-hydrogen^AUR, nodejs-lts-iron, nodejs-lts-jod, nodejs-lts-krypton)
git (git-git^AUR, git-gl^AUR) (make)
jq (jq-git^AUR, jq-static^AUR, jaq-bin^AUR, jaq-git^AUR) (make)
mise (make)
pnpm (corepacker^AUR, pnpm-corepack^AUR, pnpm-bin^AUR) (make)
ts-node (make)

Required by (0)

Sources (12)

Pinned Comments

aliu commented on 2025-10-25 02:49 (UTC)

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 .

aliu commented on 2025-08-21 15:21 (UTC)

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.

aliu commented on 2025-06-30 02:49 (UTC) (edited on 2025-07-01 16:35 (UTC) by aliu)

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.

Latest Comments

1 2 3 4 5 6 .. 26 Next › Last »

AlD commented on 2025-12-09 23:48 (UTC)

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

aliu commented on 2025-12-09 14:00 (UTC) (edited on 2025-12-09 14:00 (UTC) by aliu)

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)

notfire commented on 2025-12-09 00:54 (UTC)

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

dhtseany commented on 2025-12-03 13:16 (UTC) (edited on 2025-12-03 13:17 (UTC) by dhtseany)

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!

aliu commented on 2025-12-03 02:49 (UTC) (edited on 2025-12-03 02:51 (UTC) by aliu)

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

hrdl commented on 2025-12-02 15:13 (UTC)

I've been using vectorchord 1.0 for almost two weeks now. Besides having to patch immich I haven't observed any issues.

--- a/server/src/constants.ts   2025-11-19 18:46:53.000000000 +0100
+++ b/server/src/constants.ts   2025-11-20 10:23:43.544756010 +0100
@@ -5,7 +5,7 @@
 import { ApiTag, DatabaseExtension, ExifOrientation, VectorIndex } from 'src/enum';

 export const POSTGRES_VERSION_RANGE = '>=14.0.0';
-export const VECTORCHORD_VERSION_RANGE = '>=0.3 <0.6';
+export const VECTORCHORD_VERSION_RANGE = '>=0.3 <1.1';
 export const VECTORS_VERSION_RANGE = '>=0.2 <0.4';
 export const VECTOR_VERSION_RANGE = '>=0.5 <1';

dhtseany commented on 2025-12-02 15:08 (UTC) (edited on 2025-12-02 15:09 (UTC) by dhtseany)

Thanks for everyone's help so far.

Do note that the vectorchord package's likely to update to 1.0.0 which immich hasn't marked as supported yet, though, while versions below 0.5.3 do not have official binaries for psql18.

This is where I'm presently stuck, after enabling the extension in psql I can no longer start it's service due to the version mismatch:

FATAL:  incompatible library "/usr/lib/postgresql/vchord.so": version mismatch
DETAIL:  Server is version 18, library is version 17.
LOG:  database system is shut down

Has anyone tried a newer version of vectorchord?

aliu commented on 2025-12-02 01:32 (UTC) (edited on 2025-12-02 01:33 (UTC) by aliu)

FWIW I didn't see that on the final pacman install output:

post_install does not run when the package is upgraded. Upgrades include when you reinstall a package that's already installed. You should see the message when installing immich-server on a fresh system or one with immich-server uninstalled.

Should I change the port in the provided conf example for nginx to reflect port 2283? Or should that stay at 8080?

It pretty much just depends on whether you want to expose port 8080 too or not. In theory you'd want to reserve 2283 for connections from the server and 8080 for access from outside the server but it doesn't matter too much unless your server is publicly accessible.

dhtseany commented on 2025-12-02 01:29 (UTC)