public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About adding a way to check for bugs referring to no longer existing packages in the tree
Date: Sun, 15 Apr 2012 18:30:36 +0200	[thread overview]
Message-ID: <1334507436.2557.16.camel@belkin4> (raw)
In-Reply-To: <4F8AF2EB.7070501@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]

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.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-04-15 16:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 11:02 [gentoo-dev] About adding a way to check for bugs referring to no longer existing packages in the tree Pacho Ramos
2012-04-14 15:42 ` Alexis Ballier
2012-04-14 17:54   ` Pacho Ramos
2012-04-15  8:47     ` [gentoo-dev] " Ryan Hill
2012-04-15  9:55       ` Pacho Ramos
2012-04-15 10:00         ` Pacho Ramos
2012-04-15 10:21           ` Ryan Hill
2012-04-16  1:04         ` Jeroen Roovers
2012-04-16  1:39           ` Mike Frysinger
2012-04-16  8:40           ` Pacho Ramos
2012-04-18  9:15             ` Pacho Ramos
2012-04-15 15:47 ` [gentoo-dev] " Marcin Mirosław
2012-04-15 16:09   ` Pacho Ramos
2012-04-15 16:10   ` Samuli Suominen
2012-04-15 16:30     ` Pacho Ramos [this message]
2012-04-15 16:46     ` Marcin Mirosław

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1334507436.2557.16.camel@belkin4 \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox