Joined forces maintaining debian package(s)?

[dionysius]

Hi @arter97, would you be willing to maintain debian package(s) together?

I'm fed up with all that docker stuff and the currently existing snaps also come with drawbacks - or builds just steal the artefacts from the images. I started to write a debian package and am glancing more and more at this repo on what the needed steps are.

In the end I want an easy time managing my installation and if others can profit as well would be nice. I'm currently maintaining vaultwarden and its web-vault and it has been a breeze to maintain so far - I admit, it is also a lot easier to build.

What do you think? In the meantime I'll continue writing the package source(s).

[arter97]

I don't think a project as big as Immich can be packaged neatly into a debian package(s).

Immich server and its Node modules, probably yes, but for Python-based machine-learning server, I don't see a path.

I hate debian packages that tries to do too much in the install script with passion. With Immich requiring uv and a fixed Python version (3.12), I don't think shipping those in a debian package makes sense.

[dionysius]

I did a thing and maybe you'd like it: https://github.com/dionysius/immich-deb

And yes you were right, python is tricky. I'll investigate that further but right now I let uv do the full thing at runtime. I don't like it either but this works for now. I've read that debian is working on uv, but time will tell when and how its available.

There are some rough edges I need to sleep over whether I keep it the way it is (we could discuss) and also need to make sure that all licenses are appropriately labelled - most of it is done.

Except for uv there's no fancy script happening.

Every component is single pickable and everything is configurable, there is no config option inaccessible, all dependencies are locked.

It is still alpha and will throw my library at it soon.

Feel free to close this issue if I annoy here.