1 |
El dom, 15-04-2012 a las 11:55 +0200, Pacho Ramos escribió: |
2 |
> El dom, 15-04-2012 a las 02:47 -0600, Ryan Hill escribió: |
3 |
> > > > > From time to time I see old bug reports that are still wrongly opened |
4 |
> > > > > and referring to old packages no longer in the tree. Would be possible |
5 |
> > > > > to add a way to periodically check for bugs referring in summary to |
6 |
> > > > > obsolete packages and, then, allow us to have a cleaner bug list? |
7 |
> > |
8 |
> > How exactly would you do this? Maintain a list of all packages ever removed |
9 |
> > from the tree? What if the package name is a common word? What about bugs |
10 |
> > requesting a previously removed package be re-added? Or a different |
11 |
> > project using the same name? |
12 |
> |
13 |
> Well, I currently manually do eix searching to check it, maybe would be |
14 |
> a way to compare eix outputs with "${CATEGORY}/${PKGNAME}" from bug |
15 |
> summaries (bugs without that naming structure would be uncovered by |
16 |
> this, but we would still be able to easily check for obsolete bug |
17 |
> reports). |
18 |
> |
19 |
> Regarding bugs asking package to be readded, that bugs should be |
20 |
> assigned to maintainer-wanted and, then, could be filtered. |
21 |
> |
22 |
> > |
23 |
> > > It's not for versions, only package names (there are still bugs |
24 |
> > > referring to already removed packages for months) |
25 |
> > |
26 |
> > The person dumping the package should be checking for open bugs at the time |
27 |
> > of removal. |
28 |
> > |
29 |
> > |
30 |
> |
31 |
> I agree... but it's usually forgotten as I have seen |
32 |
> |
33 |
|
34 |
Also, the idea is to simply generate a list with possible obsolete bug |
35 |
reports, closing would still be done manually after checking for false |
36 |
positives ;) |