Package Details: immich-cli 2.7.5-1

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: 23
Popularity: 1.93
First Submitted: 2022-12-30 11:41 (UTC)
Last Updated: 2026-04-16 23:52 (UTC)

Pinned Comments

aliu commented on 2026-01-17 21:44 (UTC) (edited on 2026-01-17 21:46 (UTC) by aliu)

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

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

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 32 Next › Last »

aliu commented on 2025-12-01 03:41 (UTC)

Did you set your firewall to allow traffic through port 2283? What does immich-healthcheck on your server say?

dhtseany commented on 2025-11-30 19:06 (UTC)

Apologies if I'm missing something obvious but was I expected to start/enable any services after install?

I've tried running the immich-server.service, which appears to be running, but http://<ip-of-server>:2283 isn't responding to requests.

I picked vectorchord-immich-bin when asked which package to provide vectorchord.

aliu commented on 2025-11-26 20:14 (UTC) (edited on 2025-11-26 20:14 (UTC) by aliu)

(I fixed the checksums yesterday, too. Happy thanksgiving and a merry new- month!)

caoticofanegas commented on 2025-11-26 14:55 (UTC)

@CountMurphy in my case, the admincodes files failed also. After fixing the checksums it worked all right, so no big deal.

CountMurphy commented on 2025-11-25 20:05 (UTC)

Happy thanksgiving (if you're state side). I come bearing bad news: cities500.zip is failing checksum

aliu commented on 2025-11-24 03:12 (UTC) (edited on 2025-11-24 03:13 (UTC) by aliu)

There's groundwork in 2.3.0 on a plugin-based architecture which modifies the installation instructions. I'll hopefully finish this tomorrow night.

Note that the update-checker bug does not affect the mobile app, so use that in the meantime ig.

Edit: Okay, I didn't see @cebtenzzre's edit, but still I don't have enough time today.

cebtenzzre commented on 2025-11-24 02:13 (UTC) (edited on 2025-11-24 02:51 (UTC) by cebtenzzre)

There's a pretty serious bug in v2.2.3 that causes the web interface to lock up if there is an update (which triggered when v2.3.0 came out).

v2.3.1 provides the fix, everyone should update to it immediately: https://github.com/immich-app/immich/releases/tag/v2.3.1

patch which worked for me:

diff --git a/PKGBUILD b/PKGBUILD
index 4524f47..5444888 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -6,13 +6,14 @@
 pkgbase=immich
 pkgname=('immich-server' 'immich-cli')
 pkgrel=1
-pkgver=2.2.3
+pkgver=2.3.1
 pkgdesc='Self-hosted photos and videos backup tool'
 url='https://github.com/immich-app/immich'
 license=('AGPL-3.0-only')
 arch=(x86_64)
 # ts-node required for CLI
-makedepends=('git' 'pnpm' 'jq' 'ts-node')
+# mise required for building plugins
+makedepends=('git' 'pnpm' 'jq' 'ts-node' 'mise')

 # combination of server/CLI deps, see split package functions
 # for individual deps and commentary
@@ -72,7 +73,7 @@ source=("${pkgbase}-${pkgver}.tar.gz::https://github.com/immich-app/immich/archi
         'https://download.geonames.org/export/dump/admin1CodesASCII.txt'
         'https://download.geonames.org/export/dump/admin2Codes.txt'
         'https://raw.githubusercontent.com/nvkelso/natural-earth-vector/v5.1.2/geojson/ne_10m_admin_0_countries.geojson')
-sha256sums=('aa7fe92d8ff38a97de8d1252c1e73d2c1cbd32cac5796dade2c4648bbca7557c'
+sha256sums=('20bd60862447e7e369189f9390f8e013b50101cf2fb7561ed47793bcb63c6cc8'
             '475291c45ec0a20b52f7ff927ddd7299f6f9e848e01145817066ff194cd50f07'
             'SKIP'
             'f7821053ceb6f0cf3a2b9a53b7795a7c56a74d3e0239ac38fa734642e9faf833'
@@ -127,6 +128,17 @@ build() {
     rm cli/LICENSE  # deploy would've picked this up, duplicating standard /usr/share/licenses/spdx/AGPL-3.0-only
     pnpm --filter @immich/cli build
     pnpm --filter @immich/cli --prod --no-optional deploy output/cli-pruned
+
+    # build plugins
+    cd plugins
+    export MISE_TRUSTED_CONFIG_PATHS="${PWD}/mise.toml"
+    export MISE_TRUST_PROMPT=false
+    # Install tools via mise (extism CLI, binaryen, etc.)
+    mise install
+    # Install pnpm dependencies for plugins (mise run build will also do this, but ensure workspace is available)
+    pnpm install --frozen-lockfile
+    # Build plugins (mise run build runs: pnpm run build)
+    mise run build
 }

 package_immich-server() {
@@ -154,6 +166,11 @@ package_immich-server() {
     install -dm755 "${pkgdir}/usr/lib/immich/build"
     cp -r web/build "${pkgdir}/usr/lib/immich/build/www"

+    # install corePlugin
+    install -dm755 "${pkgdir}/usr/lib/immich/build/corePlugin"
+    cp -r plugins/dist "${pkgdir}/usr/lib/immich/build/corePlugin/dist"
+    install -Dm644 plugins/manifest.json "${pkgdir}/usr/lib/immich/build/corePlugin/manifest.json"
+
     cd "${srcdir}"

     # install reverse-geocoding data

caoticofanegas commented on 2025-11-12 15:43 (UTC) (edited on 2025-11-12 15:44 (UTC) by caoticofanegas)

Hi there, I finally ended up rebuilding the database, but I now understand how this thing with the postgres libraries work. Now I think I'll be ready for the next db upgrade. Thanks everyone!

codified_mantel commented on 2025-11-12 04:33 (UTC) (edited on 2025-11-12 04:40 (UTC) by codified_mantel)

I can see that. :) I'm trying now to understand how to adjust that so that makepkg -si can take some environment variable or setting into account. EDIT: figured that one out. edited original post. another error follows about tsconfig.json but it may not be critical.

aliu commented on 2025-11-12 04:26 (UTC)

Looks like you simply ran out of memory allocation: https://stackoverflow.com/questions/38558989/node-js-heap-out-of-memory