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] Re: About adding a way to check for bugs referring to no longer existing packages in the tree
Date: Sun, 15 Apr 2012 11:55:04 +0200	[thread overview]
Message-ID: <1334483704.2557.3.camel@belkin4> (raw)
In-Reply-To: <20120415024729.52e5d909@gentoo.org>

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

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


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

  reply	other threads:[~2012-04-15  9:56 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 [this message]
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
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=1334483704.2557.3.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