[pkg-go] News on docker packaging, the work is in progress

[Michael Stapelberg]

[+cc josch, please see inline]

Thanks for the status update and your continued work on the package(s)!

On Mon, Apr 16, 2018 at 6:31 AM, Arnaud Rebillout <
arnaud.rebillout at collabora.com> wrote:

> Dear Go Packaging Team,
>
> I'm still on my way to package Docker. I actually have a working package
> right now, but not good enough to be submitted.
>
> I have two unresolved, oustanding issues, and I'd appreciate some advice
> to solve them.
>
> - docker-registry requires `golang-github-azure-azure-sdk-for-go-dev`
> v9, while Debian packages v10. Building docker-registry against v10
> fails. There's a bunch of errors, it doesn't seem trivial to fix. So my
> approach would be to package the azure-sdk v9 under a name such as
> `golang-github-azure-azure-sdk-for-go-v9-dev`, adding the suffix `v9` to
> the install path, and then patch docker-registry to use the v9 package.
> Does that sound OK?
>

If absolutely need be, we can do that, but I would prefer it if
docker-registry could be made to build with the newer version. Is there an
upstream issue already? Typically upstream should be interested in making
their code work with the latest dependencies.


>
> - there's always this problem of circular dependencies, ie. all these
> Docker dependencies that depend on Docker. I can't have them depend on
> Docker because the Docker package is outdated and fails the build. So
> right now I vendor. How to solve that? I didn't have any genius idea
> here, the only solution I see would be to create a package
> `golang-github-docker-docker-dev` that is different from the `docker.io`
> package (ie. another source package), and that just ships the docker
> bits that are used by other packages. Having a different source package
> would solve the circular dependency problem.
>

I think josch (cc'ed) either has experience in this area or knows who might
be able to answer this.


>
> Apart from that, I have around 20 packages that need reviewing, either
> new packages or new versions of existing packages. I can provide the URL
> of the git repositories where these packages live right now, or directly
> commit to the official packages in Salsa. Please tell me what's your
> preferred workflow.
>

Feel free to directly commit them to the proper repositories. If you need
sponsoring, please send an email with the list of repos to look at.

I’m hoping someone else could take a look at these, as my time is rather
sparse at the moment. If nobody steps up, I might eventually get around to
it as time permits.


>
> Best regards,
>
>   Arnaud
>
>
> _______________________________________________
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/
> pkg-go-maintainers




-- 
Best regards,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20180418/4c144ed1/attachment.html>