Hi Shengjing,

2017-09-30 2:34 GMT-04:00 Shengjing Zhu <i...@zhsj.me>:
>>> I see activity in docker.io's packaging repository in the v17.05.0-ce.new
>>> which may work with rc4 but according to the control file it does not.
>>> How about I upload docker-runc with previous runc version shipping
>>> docker-runc binary and make docker.io use it by removing this patch hunk?:
>> I have uploaded docker-runc to unstable (in NEW) for docker.io
>> containing previous runc version
>> with fixes to make it build.
> I really think uploading this is not a good approach.
> At least I find docker master branch is using a runc version newer
> than 1.0.0-rc4.
> Packaging the lasted docker release is hard, but eventually we will
> do. And the runc/docker-runc in Debian will become duplicated.
> CCing docker.io maintainers, so they will be aware of this.

I agree that this is not an ideal approach due to duplication of code but
I think this is still the best approach since it allows following runc upstream
in runc and freeze the version for docker the same way docker upstream does.

When docker.io starts supporting latest runc in a timely manner it can
switch back from docker-runc and docker-runc can be removed from
the archive.

Before uploading the package I discussed it with Tianon from the docker.io
maintainers and he agreed that this would be the way to go in Debian.

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.


> --
> Best regards,
> Shengjing Zhu

Pkg-go-maintainers mailing list

Reply via email to