Bug#877146: [pkg-go] Bug#877146: update to runc (1.0.0~rc4) breaks docker
Hi Bálint, > I have uploaded docker-runc to unstable (in NEW) for docker.io > containing previous runc version Thanks. It has now passed NEW. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#877146: [pkg-go] Bug#877146: update to runc (1.0.0~rc4) breaks docker
Control: block -1 by 877284 Hi, 2017-09-29 11:25 GMT-04:00 Bálint Réczey: > Hi Chris, > > 2017-09-29 10:52 GMT-04:00 Chris Lamb : >> Hi Bálint, >> >>> Which is the first docker.io version that works with runc 1.0.0 rc4? I >>> would like to add the proper Breaks:. >> >> With rc4? None that are in Debian AFAICT. Perhaps I'm misunderstanding. > > Yes, there is none AFAIK. > 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. Thanks, Balint > > https://anonscm.debian.org/cgit/docker/docker.io.git/tree/debian/patches/remove-docker-prefix.patch#n9 > > This would bring us closer to upstream. > > Cheers, > Balint > >> >> (As in, I was seeing this bug with docker.io 1.13.1~ds1-2, currently in >> sid). >> >> >> Regards, >> >> -- >> ,''`. >> : :' : Chris Lamb >> `. `'` la...@debian.org / chris-lamb.co.uk >>`-
Bug#877146: [pkg-go] Bug#877146: update to runc (1.0.0~rc4) breaks docker
Hey Bálint, > 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'm not qualified to comment on the implications of this, alas!) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#877146: [pkg-go] Bug#877146: update to runc (1.0.0~rc4) breaks docker
Hi Chris, 2017-09-29 10:52 GMT-04:00 Chris Lamb: > Hi Bálint, > >> Which is the first docker.io version that works with runc 1.0.0 rc4? I >> would like to add the proper Breaks:. > > With rc4? None that are in Debian AFAICT. Perhaps I'm misunderstanding. Yes, there is none AFAIK. 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?: https://anonscm.debian.org/cgit/docker/docker.io.git/tree/debian/patches/remove-docker-prefix.patch#n9 This would bring us closer to upstream. Cheers, Balint > > (As in, I was seeing this bug with docker.io 1.13.1~ds1-2, currently in > sid). > > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`-
Bug#877146: [pkg-go] Bug#877146: update to runc (1.0.0~rc4) breaks docker
Hi Bálint, > Which is the first docker.io version that works with runc 1.0.0 rc4? I > would like to add the proper Breaks:. With rc4? None that are in Debian AFAICT. Perhaps I'm misunderstanding. (As in, I was seeing this bug with docker.io 1.13.1~ds1-2, currently in sid). Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#877146: [pkg-go] Bug#877146: update to runc (1.0.0~rc4) breaks docker
Control: affects -1 docker.io Hi, 2017-09-29 10:23 GMT-04:00 Chris Lamb: > Hi, > >> update to runc (1.0.0~rc4) breaks docker > > I can confirm that downgrading to 1.0.0~rc2+git20170201.133.9df8b30-3 > "fixed" this for me. Before uploading I asked around on IRC if anyone had problems with uploading with 1.0.0~r4 but got no objection. I agree with blocking migration to testing and I'm wondering if docker.io packages could be updated quickly to either work with this runc version or provide docker-runc since it needs a fork based on older runc. Which is the first docker.io version that works with runc 1.0.0 rc4? I would like to add the proper Breaks:. Opengcs requires runc 1.0.0~rc4 thus IMO following runc upstream in the runc package would be better than freezing it in unstable much longer. I should have targeted experimental with runc 1.0.0~rc4 and I'm ready to add epoch and revert to previous version in unstable if upgrading docker.io takes too much time. Cheers, Balint > > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`- > > ___ > Pkg-go-maintainers mailing list > pkg-go-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers