[pkg-go] Bug#877146: update to runc (1.0.0~rc4) breaks docker

[Bálint Réczey]

Hi Tianon,

2017-10-02 20:19 GMT+02:00 Tianon Gravi <tianon at debian.org>:
> On 30 September 2017 at 08:37, Bálint Réczey <balint at balintreczey.hu> wrote:
>> Tianon, could you please switch to docker-runc in docker.io?
>>
>> I have the packaging commits in git for docker-runc but I did not want to
>> push it to the go packages' area so when I get approved to the Docker
>> Packaging Team I'll push the repo to their area and happily hand over
>> the package.
>
> Your team application should be approved for creating that
> "docker-runc" repo and pushing your sources.

I pushed the repo here: https://anonscm.debian.org/cgit/docker/docker-runc.git

>
> I went to go try to update "src:docker.io", but I'm having trouble
> pulling in the "golang-github-opencontainers-docker-runc-dev"
> dependency (which is oddly named, but past the FTP team so I guess not
> a big deal).  I believe it needs to both "Provides:" and "Conflicts:"
> of "golang-github-opencontainers-runc-dev" for the sake of
> "golang-github-docker-containerd-dev" (which is very much
> intertwined).
>
> We might end up needing to _also_ create a "docker-containerd" package
> to get out of this, which would indirectly unblock
> https://github.com/containerd/containerd/issues/1508 (updating
> "containerd" to 1.x, which Docker doesn't support yet).

I think it would be cleaner to go without the Provides: and adding
docker-containerd build-depending on
golang-github-opencontainers-docker-runc-dev, but feel free to go either way.

I think the most efficient way forward would be if you could adopt the
docker-runc
package for the Docker Team and updating it as you please without
waiting for me -
and I'm perfectly OK with that.

Cheers,
Balint


>
> I'll push up my WIP changes now.
>
>
> ♥,
> - Tianon
>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4