forwarded 526229 https://bugzilla.samba.org/show_bug.cgi?id=6301
thanks

Quoting Mario Lipinski (l...@gymszbad.de):
> Package: samba
> Version: 2:3.3.3-1.1
> Severity: normal
> 
> See https://bugzilla.samba.org/show_bug.cgi?id=6301
> Applying the patch solved the problem here.
> I experienced the problem with the current samba version in stable and 
> testing.

Well, OK.

So, what is really the value added by reporting in Debian BTS a bug
that has already been reported, analyzed and *fixed* upstream?

In don't want to sound rude, but what you're just asking us is to make
double work by  hooking up on upstream BTS,
check in what version this is fixed....and wait for an upcoming
version to fix the bug anyway.

I'm not in favor of applying the patch. Diverging from upstream is
pointless at this point of development. As they have a very regular
upload schedule that guarantees us that the bug will be fixed in an
upcoming 3.3.* version, there would be no point in applying this patch,
imho.

Really, please, this is a plea to all users of Samba in Debian: until
we are getting close to the release of squeeze, please *don't* make
double bug reports when issues are already dealt with and known by the
Samba Team....unless you think that the bug makes the samba package
completely unsuitable for release (ie is release critical).

Many thanks for your care reporting, still. Again, I don't want to be
rude but more try to save our scarce resources!



Attachment: signature.asc
Description: Digital signature

Reply via email to