On Wed, 2006-01-18 at 00:38 +0100, Armin Berres wrote: > There was _never_ any version of Initng in unstable. The current version > (uploaded today) doesn't contain the bugs anymore. > > > - Can you point me to a bug which is counted as "open" for unstable when > > it's clearly clearly tagged fixed for some version? > > - Which statistics do you mean? > > I'm talking about this statistics: > http://packages.qa.debian.org/i/initng.html > http://qa.debian.org/developer.php?login=a.berres@onlinehome.de > > Have a look at the pending bugs. If I shouldn't close them I shouldn't > have them marked pending too (cause pending means pending to unstable as > I see now). > The bugs are still as pending in the satistic, but they are now fixed in > every Debian package (after tey've been built). > If I wouldn't have marked them pending they would now still appear as > opened... You should ask yourself the question here: why should I keep this bug open? A reason to keep a bug open is if there's another version in Debian still affected. But there isn't. The bug is not present in Debian for any release. It can safely be closed. This is of course for your special case where experimental is the only distribution containing your package. In a more general sense, it's important to note that the fixed-in-experimental tag is deprecated, and definately not necessary anymore. The BTS version tracking feature is just what you want. It allows for specifying exactly which versions of the package contain the bug. The BTS can than determine all by it self to which distributions (sid, etch, woody, experimental) this applies. So, the correct way to handle this is to mail to nnnnnn-done@bugs.debian.org with on the first line of your message "Version: <fixed-version>". You should close bugs like this for any you fix, regardless of in which distribution the fix will end up. bye, Thijs
Attachment:
signature.asc
Description: This is a digitally signed message part