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.97
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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 32 Next › Last »

aliu commented on 2025-08-05 04:05 (UTC)

What does journalctl -efu for immich-server and postgresql say?

CountMurphy commented on 2025-08-05 03:24 (UTC)

@aliu, since the issue wont replicate on your system, if there is anything I can do to help debug please let me know.

CountMurphy commented on 2025-08-05 02:01 (UTC)

Also having web front end issues since updating to 137.3. Posted a bug report upstream, but it could be the same issue jettscythe was talking about (" the web front end specifically is broken"). Downgrading to 137.1 fixes it

https://github.com/immich-app/immich/issues/20663

cotsuka commented on 2025-08-03 22:49 (UTC)

I'm seeing the same issue as @sesser and @jettscythe. I've tried a complete rebuild of the package after deleting all sources and /usr/lib/immich just to ensure the vite build is using the newest files. I also don't see any errors popping up in logs.

sesser commented on 2025-08-03 14:10 (UTC)

Nothing really jumps out in the logs. I don't think there's anything I really needed to do going from 1.136 -> 1.137. 1.136 was the first version I had installed. I'll keep digging. So far, I've put nginx in front of it and enabled ssl, neither of which made a difference.

aliu commented on 2025-08-02 16:31 (UTC)

@jettscythe @sesser I don't have this problem. Does anything jump out to you in journalctl -xeu immich-server? Did you miss any of the migrations needed to adjust for the big things mentioned in BREAKING CHANGELOG.md?

P.S.: Haha, they certainly are fun.

sesser commented on 2025-08-02 14:55 (UTC)

@aliu - merge conflicts are fun! I've broken plenty of repos myself.

@jettscythe I'm seeing the same thing. Tried clearing cache, different browsers... no luck.

aliu commented on 2025-08-02 04:33 (UTC)

@sesser I swear I resolved a conflict personally to make sure those said SKIP. Should be fixed now.

sesser commented on 2025-08-01 23:04 (UTC)

The latest PKGBUILD is broken. Need to remove the checksums of those files from geonames.org if they change daily. I see they were SKIP in previous versions.

==> Validating source files with sha256sums...
    immich-1.137.3.tar.gz ... Passed
    base-images ... Skipped
    immich-server.service ... Passed
    immich-machine-learning.service ... Passed
    immich.sysusers ... Passed
    immich.tmpfiles ... Passed
    immich.conf ... Passed
    nginx.immich.conf ... Passed
    cities500.zip ... FAILED
    admin1CodesASCII.txt ... FAILED
    admin2Codes.txt ... FAILED
    ne_10m_admin_0_countries.geojson ... Passed
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'immich-1.137.3-1 (immich-server)':
error: packages failed to build: immich-1.137.3-1 (immich-server)

jettscythe commented on 2025-08-01 19:19 (UTC)

Okay so I managed to get everything migrated and the service is back up, but the web front end specifically is broken. It's almost like all the content is hidden behind the sidebar. I see a "jump to content" button at the top left of the sidebar that I don't normally see. Interestingly, the photos are both visible on mobile and at the /search endpoint on web. Uploading works fine. Any ideas?