Package Details: immich-server 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
Conflicts: immich
Replaces: immich
Submitter: wabi
Maintainer: aliu
Last Packager: aliu
Votes: 22
Popularity: 1.00
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

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

aliu commented on 2026-04-01 18:00 (UTC)

;_;

musta_ruhtinas commented on 2026-04-01 15:36 (UTC) (edited on 2026-04-01 15:36 (UTC) by musta_ruhtinas)

Checksum issues again :)

==> Validating source files with sha256sums...
    immich-2.6.3.tar.gz ... Passed
    postgres-path.patch ... Passed
    sharp.patch ... Passed
    immich-server.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: Could not download sources.
❌ Error: makechrootpkg failed for 'immich'.

aliu commented on 2026-02-23 01:33 (UTC)

I don't think jellyfin-ffmpeg -> chromaprint -> ffmpeg is any sort of problem. jellyfin-ffmpeg is well-isolated from ffmpeg. (FWIW It's that way because jellyfin-ffmpeg compiles libavformat with chromaprint features, and chromaprint depends on libavcodec.)

As the PKGBUILD references (by date of the comment), reasons for using jellyfin-ffmpeg are explained at https://aur.archlinux.org/pkgbase/immich?O=230#comment-996238 .

I'm unsure immich-machine-learning -> immich-server is required

hmm, for that reason it should be listed as only an optional dependency, which is what i see on my end

dmig commented on 2026-02-22 12:06 (UTC)

Discovered a dependency mess:

immich-server -> jellyfin-ffmpeg -> chromaprint -> ffmpeg
immich-machine-learning -> immich-server -> ...
immich-machine-learning -> python-opencv -> opencv -> ffmpeg

Maybe it's worth removing jellyfin-ffmpeg since ffmpeg is installed anyway? There is ffmpeg-headless, which I use for this dependency. Also, I'm unsure immich-machine-learning -> immich-server is required. In theory, immich-machine-learning can be installed on a different machine.

aliu commented on 2026-02-07 14:34 (UTC)

@L0ric0 done!

@dmig It didn't work before I updated the service file on 5 Feb UTC. I updated it to add the relevant device groups (drm rw gives you rw access to /dev/dri/*) and the Mesa cache under the immich directory the logs initially said couldn't be accessed. Could you try it again?

L0ric0 commented on 2026-02-07 08:58 (UTC)

Hey, thank you for packaging. Could you add aarch64 to the list of architectures. I'm using immich currently on a rpi4 which works quite ok.

dmig commented on 2026-02-05 07:43 (UTC)

@aliu it probably works without hardware acceleration, check immich-server logs. with PrivateDevices=true ffmpeg can't see /dev/dri/renderD128

aliu commented on 2026-02-05 02:18 (UTC)

@dmig I did a little investigation and the current service file works with my VAAPI device.

aliu commented on 2026-02-04 23:55 (UTC)

@Terrrance They are supposed to be skipped; I just keep finding new ways to forget skipping them. (As you may know, updpkgsums currently doesn't preserve skips unless it's an unpinned VCS source. I plan to potentially contribute a patch to updpkgsums for this when I find the time...) Should be fixed now.

@dmig Good points; I'll check this out in an hour.

Terrance commented on 2026-02-04 17:58 (UTC)

As the GeoNames data file hashes are often invalidated by unversioned changes upstream, is it worth just setting their hashes as SKIP and/or commiting a fixed copy of the data and refreshing them every so often? (Their sizes are maybe just over the point where it'd be considered bloat to keep them committed here though.)

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