Package Details: immich-machine-learning 2.4.1-1

Git Clone URL: https://aur.archlinux.org/immich-machine-learning.git (read-only, click to copy)
Package Base: immich-machine-learning
Description: Machine learning server for the Immich photo management system
Upstream URL: https://github.com/immich-app/immich/tree/main/machine-learning
Licenses: AGPL-3.0-only
Submitter: aliu
Maintainer: aliu
Last Packager: aliu
Votes: 2
Popularity: 1.20
First Submitted: 2025-10-01 23:40 (UTC)
Last Updated: 2025-12-20 22:34 (UTC)

Latest Comments

1 2 Next › Last »

aliu commented on 2025-12-19 21:37 (UTC)

Also, I don't see how installing into site-packages could lead to more complex dependency issues as all Arch packages are the latest version, so the only kind of conflict I can think of (different versions simultaneously installed) wouldn't happen.

aliu commented on 2025-12-19 20:12 (UTC)

Arch Linux customs: use Pacman for dependency management, including to replace VENVs (for system-wide packages only, of course).

https://wiki.archlinux.org/title/Python?utm_source=chatgpt.com#Package_management

A large number of popular packages are available in the official repositories and AUR. This is the preferred way to install system-wide packages, and the only method officially supported on Arch Linux.

VENVs are for development or installing packages in the user scope, not system-scope, which is what Pacman does.

ExplodingDragon commented on 2025-12-19 08:41 (UTC)

Why do we need to use so many aur python packages instead of installing them with pip/uv, which may lead to even more complex dependency issues?

aliu commented on 2025-12-16 22:05 (UTC) (edited on 2025-12-16 22:06 (UTC) by aliu)

That means I included a dependency you didn't install, not that I didn't include the dependency. The --sync option in makepkg -s doesn't fetch packages from the AUR, so if a dependency is not available in the repos you'll have to make it from the AUR in advance, unfortunately. Thanks for reporting, though.

musta_ruhtinas commented on 2025-12-16 09:34 (UTC)

A few more dependecies need to be included (building in a clean chroot).

Installing missing dependencies...
:: There are 5 providers available for python-onnxruntime>=1.23.0:
:: Repository extra
   1) python-onnxruntime-cpu  2) python-onnxruntime-cuda  3) python-onnxruntime-opt-cuda  4) python-onnxruntime-opt-rocm  5) python-onnxruntime-rocm

Enter a number (default=1): 
:: There are 5 providers available for python-onnxruntime<2:
:: Repository extra
   1) python-onnxruntime-cpu  2) python-onnxruntime-cuda  3) python-onnxruntime-opt-cuda  4) python-onnxruntime-opt-rocm  5) python-onnxruntime-rocm

Enter a number (default=1): 
error: target not found: python-tokenizers>=0.15.0
error: target not found: python-tokenizers<1.0
error: target not found: python-rapidocr>=3.1.0

aliu commented on 2025-12-10 02:45 (UTC)

Good spot, thank you.

30p87 commented on 2025-12-09 16:03 (UTC)

Does not build due to an error:

* Getting build dependencies for wheel...

Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/pyproject_hooks/_impl.py", line 402, in _call_hook
    raise BackendUnavailable(
    ...<4 lines>...
    )
pyproject_hooks._impl.BackendUnavailable: Cannot import 'hatchling.build'

ERROR Backend 'hatchling.build' is not available.

Fix: add python-hatchling to makedepends

Wkennington commented on 2025-11-01 05:43 (UTC)

TY

aliu commented on 2025-11-01 00:39 (UTC)

@Wkennington That was fixed in 2.2.1. I'm in the process of shipping it.