@ckastner since you are the maintainer of these packages, do you want to weight in? Are these packages ready for general use?

@slaren, the packages are almost, but not quite, there. So I'd prefer not to advertise it quite yet. I just returned from DebConf and will work through my TODO queue. I expect to have everything finalized in the first half of August, so pretty soon.

I actually intended to file a PR for this myself, but a bit more extensive, most importantly with our release policy which will be at least monthly backports to the stable release. However I'd also like to briefly describe our testing setup, and how/where to report bugs from these packages.

Open issues:

• Split package llama.cpp into library, -dev, -tools packages -> done, just waiting for the another team's approval
• Switch ggml to GGML_BACKEND_DL=ON -> needs package dependency rework, will do it this week
• Need to automate more of my test stack (I have AMD and NVIDIA GPUs, and access to 96-core Graviton for arm64, for POWER I've opened discussions) before releasing package
• Need to talk to the Ubuntu people about backports there

From experience, users tend to report bugs they find in packages directly to upstream, ie: you. This causes friction/frustration for upstreams whenever it's not an upstream bug. Hence why I want to get my testing sorted out first, and why I'd like a few extra sentences of documentation.