From: Samuli Suominen <ssuominen@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 19:10:19 +0300 [thread overview]
Message-ID: <4F8AF2EB.7070501@gentoo.org> (raw)
In-Reply-To: <4F8AED77.20200@mejor.pl>
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
next prev parent reply other threads:[~2012-04-15 16:13 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 [this message]
2012-04-15 16:30 ` Pacho Ramos
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=4F8AF2EB.7070501@gentoo.org \
--to=ssuominen@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