Quoting Christian PERRIER (bubu...@debian.org):
> Yes, and I find no free time for looking at this more deeply. :-(
>
> Of course, an easy fix would be using "my" patch without thinking
> further as the bug reporter said that this fixed the problem for
> him.
This is what I finally did. I'm wai
Quoting Adam D. Barratt (a...@adam-barratt.org.uk):
> On Sun, 2011-01-02 at 17:32 +0100, Christian PERRIER wrote:
> > So, in short, there shouldn't be any need for a freeze exception as
> > the bug is supposedly fixed. However, I would prefer that the
> > submitter of #606350 confirms that he does
On Sun, 2011-01-02 at 17:32 +0100, Christian PERRIER wrote:
> So, in short, there shouldn't be any need for a freeze exception as
> the bug is supposedly fixed. However, I would prefer that the
> submitter of #606350 confirms that he does no longer experience this
> bug with the version in squeeze.
Quoting Julien Cristau (jcris...@debian.org):
> On Sat, Jan 1, 2011 at 17:45:10 +0100, Christian PERRIER wrote:
>
> > I'm hereby requesting approval from the release team to upload a new
> > version of samba, meant to fix #574468...and, indeed, #606350
> > (originally reported against sasl2-bin).
On Sat, Jan 1, 2011 at 17:45:10 +0100, Christian PERRIER wrote:
> I'm hereby requesting approval from the release team to upload a new
> version of samba, meant to fix #574468...and, indeed, #606350
> (originally reported against sasl2-bin).
>
> #606350 is indeed an example of the consequences o
I'm hereby requesting approval from the release team to upload a new
version of samba, meant to fix #574468...and, indeed, #606350
(originally reported against sasl2-bin).
#606350 is indeed an example of the consequences of this file
descriptor leak, predicted in #57468. The leak could also, for
i
6 matches
Mail list logo
