[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e")

Manoj Srivastava <srivasta@debian.org> wrote:
> On Wed, 04 Jun 2003 18:38:18 +1000, Herbert Xu <herbert@gondor.apana.org.au> said: 
>> Please read my paragraph that you quoted above.  I'm talking about
>> the case where the user has filed a bug against version x.y-1.  Now
>> suppose for a moment that this bug is already fixed in x.z-1.  Do
>> you have any objections to the maintainer sending a message to
>> xxx-done@bugs.debian.org with the explanation that the bug is
>> already fixed in x.z-1?
>        I see. In this case, there was no change in the package, so it
> did not belong in the Changelog; but even then the bug closing
> message has to have an adequate explanation for the bug submitter to
> be satisfied. 

Well, IMHO a message saying that the bug is fixed and giving a reference
to the version in which it is fixed is sufficient.  After all, it doesn't
matter what detailed explanation developer gives in the message, they may
have made a mistake (after all, we're not perfect) and the bug may still
be there.  Users should not be satisfied until they've verified that the
bug is indeed gone with the new version.

>        Is this related to the inadequate Changelog topic somehow?

Now assuming that you accept that closing it by hand with such a
message is OK, we can then take this one step further.  Suppose
that I setup a mechanism whereupon the reception of the accepted message
from debian-installer, a message containing exactly what I described
above is sent to the BTS for bugs which is fixed by a given upstream

My question is, would that be acceptable? And if not why is that
fundamentally different from my first scenario.  After all, the user
sees exactly the same result and the debian/changelog contains identical
information in both cases.

Now suppose that you accept that as well, then then point is obviously
what is so different between this approach and using the debian/changelog
to close bug reports upstream bug reports without further explanation.

Please note that this argument does not apply to bugs which are fixed
by Debian changes since the latter should always be listed in
debian/changelog regardless of whether they fix bugs or not.
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Reply to: