On 26/01/2025 1:16 PM, Reinhard Tartler wrote:
Thank you for the pointers. Indeed in the case of packages from
"docker/cli" and "docker/docker" it is just a matter of adding them to
the golang-github-docker-docker-dev.install file. But in the case of
"moby/buildkit", some of the packages are not present in the current
source packages, as they are there as part of the engine's vendor
directory, which is incomplete.
Cool, if these packages are easy to add and enable, let's start with that. Can you send me a MR?
So I figured "moby/buildkit" should really be fully packaged. I started
to do this in
https://salsa.debian.org/go-team/packages/golang-github-moby-buildkit/-/tree/debian/sid.
With a few patches [1] to disable some features dependent on some
missing packages, the number of missing dependencies is only 3 [2]
(golang-github-spdx-tools-golang is in NEW).
Awesome, thanks!
Then I realized that the docker.io package is in fact a "Multiple
Upstream Tarballs" package, and as the cli, engine and buildkit are all
inter-dependent of each other, I think it would probably be better to
add "moby/buildkit" in the docker.io source package.
The patches are not very descriptive and currently untested because of
the missing packages in golang-github-docker-docker-dev (see my two
MRs). But I also started to package the 3 missing dependencies. If you
are OK with this plan I can post the ITP for the 3 of them.
I've merged your MRs, let's upload that to experimental.
Let's proceed with the ITPs and get them into experimental as well.
Thanks!
[1]
https://salsa.debian.org/go-team/packages/golang-github-moby-buildkit/-/commit/b585a0c1a1b9f3b63628d16136e85904cda04b84
[2]
https://salsa.debian.org/go-team/packages/golang-github-moby-buildkit/-/commit/fbe71b63a2a712275c8e805f1529029988aaf9c3
--
Nicolas Peugnet