| 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) |
The patch below (reverting the changes to .gitignore from f4e0aad2c495) fixes the frontend css issues for me.
I do not know why, someone else can do more investigating (also figure out which ignore is causing the issue)
diff --git a/.gitignore b/.gitignore
index dcec8d8..f66fce1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -4,7 +4,3 @@ admin1CodesASCII.txt
admin2Codes.txt
cities500.zip
base-images/
-src/
-pkg/
-*.pkg.tar.zst
-LICENSES/
The official machine-learning/uv.lock from Immich was generated with Python v3.11, so it doesn't match Arch Linux's official Python (v3.13). All we need to do is delete the existing machine-learning/uv.lock and regenerate uv.lock using Arch Linux's Python with the uv lock command.
Also, you probably can't remove @img/sharp-libvips* just yet, but you can avoid depending on the system's libvips.
Uncommenting options=("!strip") did not fix the build on my end. The git checkout fix seems to work though.
Confirming @aliu's solution works for me, even without building in a clean chroot. I'm also very stumped as to why this would work...
Some users observe that the newest update breaks their webpages.
I don't know why, but here are some solutions people have found:
makepkg -si!git checkout 5888b9405f98 and then copying the newest PKBUILD and changelog file.What if you build the newest version of this package but uncomment the "options" line?
1.137.3-2 （06116e01e390） has been confirmed that this will cause problems with CSS styles.
I perform the build using a completely clean container docker.io/library/archlinux:base-devel
# allow root user
sed -i -e 's|EUID|65536|g' /usr/bin/makepkg
git clone https://aur.archlinux.org/immich.git
cd immich
makepkg -si
@karboncore Could you also send the broken package file so I can look at it later? Thanks.
Another thing you might want to try is restoring the deleted obsolete patch files.
@aliu I tried building this a dozen different ways tonight.
No matter what I seem to do, starting with the current AUR release the web frontend does not seem to work.
Reverting back to the AUR at v1.135.3 (git checkout 5888b9405f98), and then copying your current 1.137.3 PKGBUILD and changelog file into that, works. I don't understand why.
I am not using an AUR helper, so I don't think it's related to that.
@karboncore All I did in addition to the bump is add version requirements for some dependencies, delete files PKGBUILD no longer use, and modify some comments. Are you sure you didn't do anything else different? (I'm thinking it might be the difference between the clean tree done by makepkg and whatever the AUR helpers do.)
@CountMurphy Thanks, I'll check it out when I have time.
Pinned Comments
aliu commented on 2026-01-17 21:44 (UTC) (edited on 2026-01-17 21:46 (UTC) by aliu)
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:
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.1or 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.