Re: Why is ggml not migrating?
Hi,
On 2025-12-09 21:41, Christian Kastner wrote:
> Since there is no clear Policy support in favor of the process, but a
> few arguments against, with one of them pretty clear ("should be
> represented as separate source packages"), I'll revert to the
> src:ggml-cuda approach.
a final update, just to summarize for posterity:
I recently did one final upload of src:ggml, and of
bin:libggml0-backend-cuda built from a build profile.
The migration is still listed as "BLOCKED" but without an excuse [1].
Building on Adam's first analysis [2], this could be because the 0.9.4-6
binary packages were built (and signed?) from two different uploads, one
by the buildds, and one by me.
Paul found hints in the britney2 code that suggest that this should
still be supported.
But we seem to have reached agreement that regardless of britney2, the
build profile approach does not appear to be Policy-conform [3].
I uploaded src:ggml-cuda, and will remove bin:libggml0-backend-cuda from
src:ggml in the next upload.
Best,
Christian
[1]: https://tracker.debian.org/pkg/ggml
[2]: https://lists.debian.org/debian-release/2025/12/msg00313.html
[3]: https://lists.debian.org/debian-release/2025/12/msg00343.html
Reply to: