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: Wed, 18 Apr 2012 11:15:26 +0200	[thread overview]
Message-ID: <1334740526.4993.6.camel@belkin4> (raw)
In-Reply-To: <1334565624.2668.1.camel@belkin4>

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

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

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

  reply	other threads:[~2012-04-18  9:17 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 [this message]
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=1334740526.4993.6.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