Please
append echo -e "\033[0m"
to post_upgrade()
in immich-server.install.
The \033[1m in the last \033[1m: immich-machine... should be cancelled.
| 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 (server and web client) |
| 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: | 25 |
| Popularity: | 2.43 |
| First Submitted: | 2022-12-30 11:41 (UTC) |
| Last Updated: | 2026-07-18 21:47 (UTC) |
Please
append echo -e "\033[0m"
to post_upgrade()
in immich-server.install.
The \033[1m in the last \033[1m: immich-machine... should be cancelled.
https://aur.archlinux.org/cgit/aur.git/tree/immich.sysusers?h=immich
u immich - "immich user" /var/lib/immich /usr/bin/nologin
m immich redis
Package extra/valkey comes with neither user "redis" nor group "redis" anymore.
After installing extra/valkey and aur/immich-server, there is only a dangling group "redis" without a user "redis".
Modify immich.sysusers, either one of two options:
(1) Add immich to group "valkey", completely remove any reference to group "redis".
(2) Add immich to both solid group "valkey" and dangling group "redis". Keep both "aur/redis" fans and "extra/valkey" fans happy.
--- why? ---
current id immich
uid=946(immich) gid=946(immich) groups=946(immich),966(redis)
With the following /etc/valkey/valkey.conf,
a sudo gpasswd -a valkey immich is required,
otherwise immich cannot communicate with the socket.
unixsocket /run/valkey/valkey.sock
unixsocketgroup valkey
unixsocketperm 660
With the following /etc/valkey/valkey.conf,
a sudo gpasswd -a redis valkey is required,
otherwise valkey fails to create valkey.sock with group ownership "redis",
because user valkey has no seat in group redis.
unixsocket /run/valkey/valkey.sock
unixsocketgroup redis
unixsocketperm 660
Please modify immich.sysusers, to ensure at least one scenario works ootb w/o manual gpasswd-ing.
ughhhh I really thought I'd committed that this time.
Your checksums need to be updated for this release.
@notfire good catch. Should be fixed now. They are supposed to be skipped but updpkgsums keeps spending every dollar at the liquor shop. I hope Arch's libmakepkg maintainers come back from vacation to look at https://gitlab.archlinux.org/pacman/pacman/-/merge_requests/355 soon.
the three files downloaded from download.geonames.org have outdated hashes (and they're constantly changing so it should probably be set back to SKIP)
v3.0.1-1: core plugin installed under wrong directory name immich-plugin-core fails to load
The server hardcodes the core-plugin path as plugins/immich-plugin-core:
dist/repositories/config.repository.js:213:
corePlugin: join(buildFolder, 'plugins', 'immich-plugin-core')
and the plugin's own manifest.json declares "name": "immich-plugin-core". But the package installs it as /usr/lib/immich/build/plugins/immich-core-plugin/ (words transposed), so startup logs:
WARN [WorkflowExecutionService] Failed to import plugin from
/usr/lib/immich/build/plugins/immich-plugin-core
The core plugin (smart albums, workflows) is silently disabled as a result. The PKGBUILD's plugin install step should place it at immich-plugin-core/ to match.
Interim workaround: sudo ln -s immich-core-plugin immich-plugin-core in the plugins dir.
pnpm 11
Makes sense, fixed, thanks. Any idea which release/commit changed this?
Immich server no longer builds with the following error:
[ERROR] Unknown option: 'frozen-lockfile'
EDIT: Didn't see the previous comment but I can confirm the fix works.
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.