On Sat, Jun 08, 2019 at 10:13:03PM -0400, Afif Elghraoui wrote:
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).
No, that's not the point; it's the consequence. There are
Hello,
On Fri, 24 May 2019 10:33:34 +0100 Jonathan Dowland 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:
On 5/24/19 4:33 PM, Jonathan Dowland wrote:
> Hi Arnaud - sorry I missed your messages until now.
No problem :)
>
> 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:
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
On 5/22/19 3:32 PM, Afif Elghraoui wrote:
> You hadn't Cc'd Jonathan (but I am, now) and I doubt that he's
> subscribed to this bug, so he probably never saw these messages. I'm
> just checking in here as a concerned maintainer of a reverse-dependency
> threatened with autoremoval.
Hmm I'm a bit
Hi, Arnaud
On Fri, 10 May 2019 09:03:41 +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
>
On Mon, 29 Apr 2019 07:46:22 +0700 Arnaud Rebillout
wrote:
> Actually this was fixed upstream lately, and the fix is in Debian
> testing already. See
> https://github.com/docker/libnetwork/pull/2339#issuecomment-487207550
>
> There's still other iptables related bugs, the most outstanding being
>
Actually this was fixed upstream lately, and the fix is in Debian
testing already. See
https://github.com/docker/libnetwork/pull/2339#issuecomment-487207550
There's still other iptables related bugs, the most outstanding being
#903635. If this bug could be solved, then users could just run docker
8 matches
Mail list logo
