Hello

From time to time I see old bug reports that are still wrongly opened
and referring to old packages no longer in the tree. Would be possible
to add a way to periodically check for bugs referring in summary to
obsolete packages and, then, allow us to have a cleaner bug list?

If the bug is referring to an overlay, it should state that in summary
(like we do with [gnome-overlay] bugs) and skip checking for them.

Thanks a lot

On Sat, 14 Apr 2012 13:02:27 +0200
Pacho Ramos <pacho@gentoo.org> wrote:

> Hello
>
> From time to time I see old bug reports that are still wrongly opened
> and referring to old packages no longer in the tree. Would be possible
> to add a way to periodically check for bugs referring in summary to
> obsolete packages and, then, allow us to have a cleaner bug list?

-1, you really cant automate this.

- for eg, keyword req, the version doesnt really matter and is usually
just there to help but should really be read as latest version;
closing/ignoring the bug while the latest version still lacks the
keywords is just wrong.
- for stablereq, that's a different story

- for other bugs, some may have been fixed independently upstream, but
usually, they dont fix by themselves, so if a bug didnt get
attention, chances are its still valid.


moreover, doing this, you'll just encourage people not to fill the
version


IOW: If you want a cleaner bug list, ignore stable/kw reqs, then pay
attention to your bugs and fix them

A.

El sáb, 14-04-2012 a las 12:42 -0300, Alexis Ballier escribió:
> On Sat, 14 Apr 2012 13:02:27 +0200
> Pacho Ramos <pacho@gentoo.org> wrote:
>
> > Hello
> >
> > From time to time I see old bug reports that are still wrongly opened
> > and referring to old packages no longer in the tree. Would be possible
> > to add a way to periodically check for bugs referring in summary to
> > obsolete packages and, then, allow us to have a cleaner bug list?
>
> -1, you really cant automate this.
>
> - for eg, keyword req, the version doesnt really matter and is usually
> just there to help but should really be read as latest version;
> closing/ignoring the bug while the latest version still lacks the
> keywords is just wrong.
> - for stablereq, that's a different story
>
> - for other bugs, some may have been fixed independently upstream, but
> usually, they dont fix by themselves, so if a bug didnt get
> attention, chances are its still valid.
>
>
> moreover, doing this, you'll just encourage people not to fill the
> version
>
>
> IOW: If you want a cleaner bug list, ignore stable/kw reqs, then pay
> attention to your bugs and fix them
>
> A.
>
>

It's not for versions, only package names (there are still bugs
referring to already removed packages for months)

> > > From time to time I see old bug reports that are still wrongly opened
> > > and referring to old packages no longer in the tree. Would be possible
> > > to add a way to periodically check for bugs referring in summary to
> > > obsolete packages and, then, allow us to have a cleaner bug list?

How exactly would you do this? Maintain a list of all packages ever removed
from the tree? What if the package name is a common word? What about bugs
requesting a previously removed package be re-added? Or a different
project using the same name?

> It's not for versions, only package names (there are still bugs
> referring to already removed packages for months)

The person dumping the package should be checking for open bugs at the time
of removal.


--
fonts, gcc-porting
toolchain, wxwidgets
@ gentoo.org

El dom, 15-04-2012 a las 02:47 -0600, Ryan Hill escribió:
> > > > From time to time I see old bug reports that are still wrongly opened
> > > > and referring to old packages no longer in the tree. Would be possible
> > > > to add a way to periodically check for bugs referring in summary to
> > > > obsolete packages and, then, allow us to have a cleaner bug list?
>
> How exactly would you do this? Maintain a list of all packages ever removed
> from the tree? What if the package name is a common word? What about bugs
> requesting a previously removed package be re-added? Or a different
> project using the same name?

Well, I currently manually do eix searching to check it, maybe would be
a way to compare eix outputs with "${CATEGORY}/${PKGNAME}" from bug
summaries (bugs without that naming structure would be uncovered by
this, but we would still be able to easily check for obsolete bug
reports).

Regarding bugs asking package to be readded, that bugs should be
assigned to maintainer-wanted and, then, could be filtered.

>
> > It's not for versions, only package names (there are still bugs
> > referring to already removed packages for months)
>
> The person dumping the package should be checking for open bugs at the time
> of removal.
>
>

I agree... but it's usually forgotten as I have seen

El dom, 15-04-2012 a las 11:55 +0200, Pacho Ramos escribió:
> El dom, 15-04-2012 a las 02:47 -0600, Ryan Hill escribió:
> > > > > From time to time I see old bug reports that are still wrongly opened
> > > > > and referring to old packages no longer in the tree. Would be possible
> > > > > to add a way to periodically check for bugs referring in summary to
> > > > > obsolete packages and, then, allow us to have a cleaner bug list?
> >
> > How exactly would you do this? Maintain a list of all packages ever removed
> > from the tree? What if the package name is a common word? What about bugs
> > requesting a previously removed package be re-added? Or a different
> > project using the same name?
>
> Well, I currently manually do eix searching to check it, maybe would be
> a way to compare eix outputs with "${CATEGORY}/${PKGNAME}" from bug
> summaries (bugs without that naming structure would be uncovered by
> this, but we would still be able to easily check for obsolete bug
> reports).
>
> Regarding bugs asking package to be readded, that bugs should be
> assigned to maintainer-wanted and, then, could be filtered.
>
> >
> > > It's not for versions, only package names (there are still bugs
> > > referring to already removed packages for months)
> >
> > The person dumping the package should be checking for open bugs at the time
> > of removal.
> >
> >
>
> I agree... but it's usually forgotten as I have seen
>

Also, the idea is to simply generate a list with possible obsolete bug
reports, closing would still be done manually after checking for false
positives

On Sun, 15 Apr 2012 12:00:45 +0200
Pacho Ramos <pacho@gentoo.org> wrote:

> Also, the idea is to simply generate a list with possible obsolete bug
> reports, closing would still be done manually after checking for false
> positives

Ah, okay. I thought you wanted something automatically closing them.


--
fonts, gcc-porting
toolchain, wxwidgets
@ gentoo.org

W dniu 2012-04-14 13:02, Pacho Ramos pisze:
> Hello
>
> From time to time I see old bug reports that are still wrongly
> opened and referring to old packages no longer in the tree. Would
> be possible to add a way to periodically check for bugs referring
> in summary to obsolete packages and, then, allow us to have a
> cleaner bug list?

Hi,
what about siutation package was removed from tree. After sometime
other maintainer wants to put this package to the tree again,
shouldn't fix those bugs before doing this?
Marcin

El dom, 15-04-2012 a las 17:47 +0200, Marcin Mirosław escribió:
> W dniu 2012-04-14 13:02, Pacho Ramos pisze:
> > Hello
> >
> > From time to time I see old bug reports that are still wrongly
> > opened and referring to old packages no longer in the tree. Would
> > be possible to add a way to periodically check for bugs referring
> > in summary to obsolete packages and, then, allow us to have a
> > cleaner bug list?
>
> Hi,
> what about siutation package was removed from tree. After sometime
> other maintainer wants to put this package to the tree again,
> shouldn't fix those bugs before doing this?
> Marcin
>

As that results will simply be used to generate a list, it will be a
good opportunity to really check that developer is taking care of it (I
have also seen a lot of cases where a dev has a bug for this assigned to
him for months without action)

On 04/15/2012 06:47 PM, Marcin Mirosław wrote:

W dniu 2012-04-14 13:02, Pacho Ramos pisze:

Hello

From time to time I see old bug reports that are still wrongly
opened and referring to old packages no longer in the tree. Would
be possible to add a way to periodically check for bugs referring
in summary to obsolete packages and, then, allow us to have a
cleaner bug list?


Hi,
what about siutation package was removed from tree. After sometime
other maintainer wants to put this package to the tree again,
shouldn't fix those bugs before doing this?
Marcin




When package foobar gets removed from Portage, the remaining bugs
affecting foobar gets closed with resolution WONTFIX/OBSOLETE/FIXED
depending on type of the bug.
When package foobar gets readded to Portage, the maintainer needs to
check also for closed bugs.

That's how it is now, and the workflow wouldn't change with this proposal.

So you are right, but irrelevant to the /topic in hand.

- Samuli