FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo Development

 
 
LinkBack Thread Tools
 
Old 04-15-2012, 04:30 PM
Pacho Ramos
 
Default About adding a way to check for bugs referring to no longer existing packages in the tree

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.
 
Old 04-15-2012, 04:46 PM
Marcin Mirosław
 
Default About adding a way to check for bugs referring to no longer existing packages in the tree

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
 
Old 04-16-2012, 01:04 AM
Jeroen Roovers
 
Default About adding a way to check for bugs referring to no longer existing packages in the tree

On Sun, 15 Apr 2012 11:55:04 +0200
Pacho Ramos <pacho@gentoo.org> 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
 
Old 04-16-2012, 01:39 AM
Mike Frysinger
 
Default About adding a way to check for bugs referring to no longer existing packages in the tree

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
 
Old 04-16-2012, 08:40 AM
Pacho Ramos
 
Default About adding a way to check for bugs referring to no longer existing packages in the tree

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@gentoo.org> 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
 
Old 04-18-2012, 09:15 AM
Pacho Ramos
 
Default About adding a way to check for bugs referring to no longer existing packages in the tree

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@gentoo.org> 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
 

Thread Tools




All times are GMT. The time now is 06:23 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org