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 think we need to ask the release team
to do that (and tag accordingly) but I'll double-check the procedure.
- 2 I import the patch from github, even though it's work in progress. I
will follow up and update the patch as soon as upstream release a proper
fix, and it will be included in a point release of buster.
If I don't get any feedback from you Jonathan in the following days,
I'll go for solution number 2 then.
I bow to your judgement as maintainer as to whether the partial fix is
worth applying on its own. Will the patch in #2339 address the specific
issue of what happens on package install?
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄⠀⠀⠀⠀
