Hello, On Fri, 24 May 2019 10:33:34 +0100 Jonathan Dowland <j...@debian.org> wrote: > Hi Arnaud - sorry I missed your messages until now. > > On Fri, May 10, 2019 at 09:03:41AM +0700, Arnaud Rebillout wrote: > >As I mentioned above, there's a discussion with a work in progress to > >fix that upstream: https://github.com/docker/libnetwork/pull/2339 > > > >I don't think it will be ready in time for buster though. So I see two > >solutions going forward: > > > >- 1 Jonathan lower the severity of the bug so that it's not RC. > > I'd rather not do that, because I think RC is the right classification; > *but* I don't feel necessarily (given the circumstances) that docker.io > should be removed from Buster, so can I instead suggest we request that > this bug is ignored for Buster?
I don't understand... I thought the whole point of making a bug release-critical is to keep the bug out of the release (either by having it fixed or removing the package). > I think we need to ask the release team > to do that (and tag accordingly) but I'll double-check the procedure. > It seems to me like the severity of this bug should just be lowered, but if you want to pursue a buster-ignore tag, someone please contact the release team and make it happen. https://www.debian.org/Bugs/Developer says explicit authorization is needed from the release managers, but I'd worry that an email to debian-rele...@lists.debian.org might get lost and it'd be weird to file a bug on release.debian.org asking to apply a tag to another bug. Again, I think it makes more sense to just lower the severity if you don't think it should affect the release. regards Afif -- Afif Elghraoui | عفيف الغراوي https://afif.ghraoui.name
