Quoting Fabio Muzzi (kur...@kurgan.org):
> 
> Dear Christian,
> 
> I have reported this bug because I believed it to be a regression,
> maybe in the Debian version only, of a bug that was fixed upstream
> more than one year ago. So I thought "maybe it's a Debian-specific
> bug, somehow the patch that Samba applied a year ago did not make it
> into Debian".

Well, it's not a regression in the Debian package. It's a regression
in the upstream versions. This bug belongs to the series of bugs we
always have in the stable version (currently 3.5.6 plus a few fixes
backported from later 3.5 version, for important bugs). Unless I can
be convinced that the bug is at least of "important" severity, chances
are low that the fix is included in squeeze's samba.

> And anyway, I think it's a good idea to fix this bug in Squeeze,
> because even if it's not a security bug, it's quite crippling
> expecially for exotic software packages (complex CAD propgrams for
> example) that tend to trigger it a lot on shared library files, for
> example.


I didn't go into the details of the bug. It would help if we could
examine the fix: if it is not too invasive, then fixing the bug in
squeeze might be an option but, given the bug's severity, I might have
hard times convincing the Debian stable release managers that it's
worth fixing the bug in squeeze.


Attachment: signature.asc
Description: Digital signature

Reply via email to