Mailing List Archive: Gentoo: Dev

About adding a way to check for bugs referring to no longer existing packages in the tree

Index | Next | Previous | View Threaded

pacho at gentoo

Apr 14, 2012, 4:02 AM

Post #1 of 16 (278 views)
Permalink

About adding a way to check for bugs referring to no longer existing packages in the tree

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

Attachments:

signature.asc (0.19 KB)

aballier at gentoo

Apr 14, 2012, 8:42 AM

Post #2 of 16 (270 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

On Sat, 14 Apr 2012 13:02:27 +0200
Pacho Ramos <pacho [at] gentoo> 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.

pacho at gentoo

Apr 14, 2012, 10:54 AM

Post #3 of 16 (265 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

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 [at] gentoo> 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)

Attachments:

signature.asc (0.19 KB)

dirtyepic at gentoo

Apr 15, 2012, 1:47 AM

Post #4 of 16 (269 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

> > > 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

Attachments:

signature.asc (0.19 KB)

pacho at gentoo

Apr 15, 2012, 2:55 AM

Post #5 of 16 (268 views)
Permalink

Re: Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

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

Attachments:

signature.asc (0.19 KB)

pacho at gentoo

Apr 15, 2012, 3:00 AM

Post #6 of 16 (265 views)
Permalink

Re: Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

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 ;)

Attachments:

signature.asc (0.19 KB)

dirtyepic at gentoo

Apr 15, 2012, 3:21 AM

Post #7 of 16 (265 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

On Sun, 15 Apr 2012 12:00:45 +0200
Pacho Ramos <pacho [at] gentoo> 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

Attachments:

signature.asc (0.19 KB)

marcin at mejor

Apr 15, 2012, 8:47 AM

Post #8 of 16 (268 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

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

pacho at gentoo

Apr 15, 2012, 9:09 AM

Post #9 of 16 (265 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

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)

Attachments:

signature.asc (0.19 KB)

ssuominen at gentoo

Apr 15, 2012, 9:10 AM

Post #10 of 16 (265 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

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

pacho at gentoo

Apr 15, 2012, 9:30 AM

Post #11 of 16 (267 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

El dom, 15-04-2012 a las 19:10 +0300, Samuli Suominen escribió:
> 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
>
>

The problem is that, in reality, some bugs are forgotten and are keep
opened. Currently, I manually check for them, but it's sometimes hard to
do this manually. The idea of generating a QA report (like others in
http://qa-reports.gentoo.org/) would allow me to easily review that list
periodically to check that obsolete bugs are closed.

Attachments:

signature.asc (0.19 KB)

marcin at mejor

Apr 15, 2012, 9:46 AM

Post #12 of 16 (265 views)
Permalink

Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

W dniu 2012-04-15 18:10, Samuli Suominen napisał(a):
> 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.

Thanks for clarification, i was afraid sentence "cleaner bug list"
means remove/make unavailable in future.
Marcin

jer at gentoo

Apr 15, 2012, 6:04 PM

Post #13 of 16 (262 views)
Permalink

Re: Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

On Sun, 15 Apr 2012 11:55:04 +0200
Pacho Ramos <pacho [at] gentoo> wrote:

> 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).

I only started fixing summaries to include valid, canonical
cat/pkg[-ver] strings a few years ago because searching for a full
atom in bugzilla's search would otherwise (and still does) fail.

Before that it was mayhem, and it's mainly the older bugs you appear be
worried about. Having a list of bugs to fix the cat/pkg for would have
more uses than the one you're interested in.

jer

vapier at gentoo

Apr 15, 2012, 6:39 PM

Post #14 of 16 (262 views)
Permalink

Re: Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

On Sunday 15 April 2012 21:04:01 Jeroen Roovers wrote:
> On Sun, 15 Apr 2012 11:55:04 +0200 Pacho Ramos wrote:
> > 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).
>
> I only started fixing summaries to include valid, canonical
> cat/pkg[-ver] strings a few years ago because searching for a full
> atom in bugzilla's search would otherwise (and still does) fail.

+1

i'm a bit more anal and generally prefer it to be the first item in the summary
as it makes scanning through summaries much easier. having an arbitrary
series of words before it makes it a bit harder imo.
-mike

Attachments:

signature.asc (0.82 KB)

pacho at gentoo

Apr 16, 2012, 1:40 AM

Post #15 of 16 (264 views)
Permalink

Re: Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

El lun, 16-04-2012 a las 03:04 +0200, Jeroen Roovers escribió:
> On Sun, 15 Apr 2012 11:55:04 +0200
> Pacho Ramos <pacho [at] gentoo> wrote:
>
> > 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).
>
> I only started fixing summaries to include valid, canonical
> cat/pkg[-ver] strings a few years ago because searching for a full
> atom in bugzilla's search would otherwise (and still does) fail.
>
> Before that it was mayhem, and it's mainly the older bugs you appear be
> worried about. Having a list of bugs to fix the cat/pkg for would have
> more uses than the one you're interested in.
>
>
> jer
>
>

I obviously agree, but both suggestions are not mutually exclusive I
think :)

Attachments:

signature.asc (0.19 KB)

pacho at gentoo

Apr 18, 2012, 2:15 AM

Post #16 of 16 (234 views)
Permalink

Re: Re: About adding a way to check for bugs referring to no longer existing packages in the tree [In reply to]

El lun, 16-04-2012 a las 10:40 +0200, Pacho Ramos escribió:
> El lun, 16-04-2012 a las 03:04 +0200, Jeroen Roovers escribió:
> > On Sun, 15 Apr 2012 11:55:04 +0200
> > Pacho Ramos <pacho [at] gentoo> wrote:
> >
> > > 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).
> >
> > I only started fixing summaries to include valid, canonical
> > cat/pkg[-ver] strings a few years ago because searching for a full
> > atom in bugzilla's search would otherwise (and still does) fail.
> >
> > Before that it was mayhem, and it's mainly the older bugs you appear be
> > worried about. Having a list of bugs to fix the cat/pkg for would have
> > more uses than the one you're interested in.
> >
> >
> > jer
> >
> >
>
> I obviously agree, but both suggestions are not mutually exclusive I
> think :)

This is another example I hit today:
https://bugs.gentoo.org/show_bug.cgi?id=247750

that would benefit from this QA report

Attachments:

signature.asc (0.19 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads