Quoting wy...@volny.cz (wy...@volny.cz):

> > I'm not in position to check upstream's BTS, but I guess this is fixed
> > > in 3.3.*, right?
> 
> No, i don't think so. But will be included in next samba release.
> 
> 
> > It seems like everybody is trying to make us fix each and every bug
> > > found after 3.2.5....slowly turning it into a fake 3.2.8...:-)
> 
> My IQ led me to think myself, that if there is a bug, it should be fixed.
> But now i understand why the "bug graph" for stable only grows. Nobody
> is willing to fix stable and when there is enough bugs for stable, it's
> right time for new stable with just few bugs :-))

That is not exactly true.

The Debian way to do things is to keep stable stable..:-). So, we
generally fix release critical and "important-enough" bugs in
stable. Most teams even only fix release critical bugs.

When it comes at samba, we already did two updates to lenny packages,
fixing 4 bugs that were judged as important. That's why, in the case
of this very bug, we need to figure out its impact on users, to decide
whether we fix it or not...

What lead to my remark is seeing the quite high number of bugs that
are reported while their reporters know they're fixed in pos-3.2.5 releases...


> 
> 
> > If that bug is really severity normal, I don't really see enough
> > reasons to tag it for lenny.
> 
> It's fine for me not to fix it. I've read how to make own package and
> made patched one.

What would be interesting is your input about the *potential* impact
on users.

> 
> > I'd like to get more rationale to convince me that this is worth
> > trying to fix this in lenny.
> 
> I'm not going to do that. Severity is probably not higher than normal.
> 
> PS: If sombody got pissed off by my second paragraph - sorry. It was
> just a stupid sarcasm. I'm satisfied Debian user and appreciate that
> so many peoples gives their spare time for such a good OS as Debian
> is.


No problem. We like Debian users who report bugs. Sometime we mumble a
little because we don't like too many bug reports at the same time,
but that's fine..:-)


Attachment: signature.asc
Description: Digital signature

Reply via email to