[Aptitude-devel] Closing all remaining aptitude-gtk bugs?

Manuel A. Fernandez Montecelo manuel.montezelo at gmail.com
Thu Apr 26 08:41:04 UTC 2012

2012/4/26 Christian PERRIER <bubulle at debian.org>:
> Quoting Manuel A. Fernandez Montecelo (manuel.montezelo at gmail.com):
>> > For finding them again later, some user-tags could be appropriate,
>> > too, but only if someone tells it the potential resurrector.
>> Well, that's only my opinion.  I just find it awkward to close bug
>> reports affecting different releases just based on the status on the
>> most recent one (still in preparation, even if many people --including
>> me-- use it directly), when the other releases are going to stay
>> active still for a few years.  And specially in Debian, where stable
>> releases are so fundamental and embedded in the culture.
> IMHO? this is what version tagging is about.
> If the bugs are closed with a version uploaded in unstable, they'll
> still be visibnle to users looking at bugs affecting the version of
> aptitude-gtk in stable.

So when tools like reportbug make the request "give me the available
bugs" it passes a parameter with the current version of the package in
the request, and users of stable will still be presented with all of
these bug reports?

If so I think that it's a good solution, yes.


More information about the Aptitude-devel mailing list