On 18 Feb 2017, at 5:33 AM, Evgeni Golov <evg...@debian.org> wrote: > > Hi Tim, > > On Wed, Feb 15, 2017 at 10:52:22PM +0000, Potter, Tim wrote: >>> I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me. >> >> Hi everyone. This upload is part of updated build dependencies for Docker >> 1.13.0. >> Currently the pipeline is stalled while a few things sit in the NEW queue. >> When >> that's all sorted out everything should build again. > > Can we in the meantime have proper Breaks in place, so that people don't > accidentally update runc without docker/containerd/etc?
Hi Evgeni. Thanks for the reply. I had totally missed the fact that people could be doing individual package upgrades of runc (also containerd) and this would muck up the docker.io package. What particular Break lines would you think appropriate for this situation? My initial guess would have been adding Depends = in docker.io, containerd and runc to ensure that everything is upgraded in lockstep, but I don't see where Breaks can be applied. Thanks, Tim. > > Thanks > Evgeni
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Pkg-go-maintainers mailing list Pkgfirstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers