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

Re: What to do with bug reports against non-existing/removed packages



Hi,

2012/5/18 Daniel Leidert <Daniel.Leidert.Spam@gmx.net>:
> Hi,
>
> Our bug tracker contains items for packages, which do (not longer) exist. What should happen to them? I see, that it might be a good idea to keep them for the case, a package is re-introduced. But this might happen only for a few packages. Most of them got removed because newer versions were released. What about closing those reports, if an RM-request is filed?
>
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=

As others have said, I asked the question only a few weeks ago:

  http://lists.debian.org/debian-devel/2012/03/msg00946.html

Reassigning 300 bugs from emacsX (X<23) to current emacs packages is
not very helpful, really.  What I did is to notify the maintainers (or
related mailing lists) of the three biggest groups (linux, gcc, emacs)
to decide what to do.

Ben Hutchings took care of the ones of the kernel, I'm especially
focusing on the ones of GCC right now (trying to reproduce, closing or
reassigning when appropriate), and the same with emacs ones (but I did
only one session of those or so, closing some tagged fixed-upstream).
I also handled other reports here and there from other packages.

I'm thinking that the "fix one orphan bug before posting to
debian-devel@ flame threads" would be helpful here :-)

Don't know what to suggest, really, but it's a shame that some very
helpful bug reports are lost in this process for Debian.  The are many
good bug reports about GCC, e.g. incorrect optimisations or wrong code
in some architectures that were closed so close as 1 month ago (so
they are not part of 4.7, they will be in 4.8), and which were
reported in Debian (and forwarded upstream by Debian maintainers) many
many years ago.  Some similar ones reported years ago are still not
forwarded, but I haven't yet handled them to see if they are valid,
reproducible or what (#448370, #470557).

So I wouldn't blindly close those bug reports, and that's why I'm
triaging and handling them in my spare time.

Cheers.


Reply to: