@aliu, cities500.zip is failing the checksum again. Might need to push it 5 times this time to fully alleviate said sins :p
Search Criteria
Package Details: immich-cli 2.7.5-1
Package Actions
| 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) |
Dependencies (5)
- nodejs (nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogenAUR, nodejs-lts-iron, nodejs-lts-jod, nodejs-lts-krypton)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- mise (mise-gitAUR, mise-binAUR) (make)
- pnpm (pnpm-corepackAUR, pnpm-binAUR) (make)
- ts-node (make)
Required by (0)
Sources (13)
- https://download.geonames.org/export/dump/admin1CodesASCII.txt
- https://download.geonames.org/export/dump/admin2Codes.txt
- https://download.geonames.org/export/dump/cities500.zip
- https://raw.githubusercontent.com/nvkelso/natural-earth-vector/v5.1.2/geojson/ne_10m_admin_0_countries.geojson
- immich-2.7.5.tar.gz
- immich-server.service
- immich.conf
- immich.sysusers
- immich.tmpfiles
- nginx.immich.conf
- postgres-path.patch
- sh-serverhome.patch
- sharp.patch
Latest Comments
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 32 Next › Last »
CountMurphy commented on 2025-11-04 15:59 (UTC)
CountMurphy commented on 2025-11-04 15:57 (UTC)
@hifiboombox I have the same setup.
I just symlinked /var/lib/immich/upload to my raid. Problem solved.
hifiboombox commented on 2025-11-04 08:44 (UTC)
How can I change the upload path from the default /var/lib/immich/upload to somewhere else? I have a RAID-Z array that I want to keep my photos on. I've made the following modifications:
- changed the IMMICH_MEDIA_LOCATION key in
/etc/immich.conf - given proper permission with
chmodandchownto my new path - changed the
ReadWritePathskey ofimmich-server.service
But the systemd unit still complains about being unable to write to my new path. I feel like this has something to do with all the "protection" settings in immich-server.service. Anyone have any idea how to do this?
aliu commented on 2025-11-02 23:35 (UTC)
Have you tried the instructions I've pinned?
caoticofanegas commented on 2025-11-02 22:17 (UTC)
I really effed up my database with the postgres update. I don't know what I did wrong, but well, I've figured out I might as well start up fresh and rebuild the whole database from scratch, I still have a backup of all my pictures and videos. Can anyone help me to get rid of the old db and build it back with postgres 18?
LandonDeam commented on 2025-11-02 00:00 (UTC)
Building now, check seemed to pass
aliu commented on 2025-11-01 21:55 (UTC)
You are correct. To alleviate for my sins, I have pushed the changes four times. That'll do it.
CountMurphy commented on 2025-11-01 17:42 (UTC)
Those files still fail on a clean build. I don't think the updated PKG was pushed?
aliu commented on 2025-11-01 16:20 (UTC)
Ugh, I forgot to mark them SKIP again. Fixed.
Wkennington commented on 2025-11-01 05:43 (UTC) (edited on 2025-11-01 05:44 (UTC) by Wkennington)
On a clean builddir
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha256sums...
immich-2.2.1.tar.gz ... Passed
backup.service.ts.patch ... Passed
base-images ... Skipped
immich-server.service ... Passed
immich.sysusers ... Passed
immich.tmpfiles ... Passed
immich.conf ... Passed
nginx.immich.conf ... Passed
cities500.zip ... FAILED
admin1CodesASCII.txt ... Passed
admin2Codes.txt ... FAILED
ne_10m_admin_0_countries.geojson ... Passed
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.