From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SJ58g-00057z-FG for garchives@archives.gentoo.org; Sat, 14 Apr 2012 15:43:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 13C3EE0A59; Sat, 14 Apr 2012 15:43:32 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id AD77CE090F for ; Sat, 14 Apr 2012 15:42:52 +0000 (UTC) Received: from localhost (pc-19-219-86-200.cm.vtr.net [200.86.219.19]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aballier) by smtp.gentoo.org (Postfix) with ESMTPSA id B48941B4038 for ; Sat, 14 Apr 2012 15:42:51 +0000 (UTC) Date: Sat, 14 Apr 2012 12:42:45 -0300 From: Alexis Ballier 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 Message-ID: <20120414124245.323cba48@gentoo.org> In-Reply-To: <1334401347.3181.2.camel@belkin4> References: <1334401347.3181.2.camel@belkin4> Organization: Gentoo X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: e916bd2f-28ca-4370-9009-5dc9ac8458a1 X-Archives-Hash: 39010ed6590daec397969714283417a8 On Sat, 14 Apr 2012 13:02:27 +0200 Pacho Ramos wrote: > 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? -1, you really cant automate this. - for eg, keyword req, the version doesnt really matter and is usually just there to help but should really be read as latest version; closing/ignoring the bug while the latest version still lacks the keywords is just wrong. - for stablereq, that's a different story - for other bugs, some may have been fixed independently upstream, but usually, they dont fix by themselves, so if a bug didnt get attention, chances are its still valid. moreover, doing this, you'll just encourage people not to fill the version IOW: If you want a cleaner bug list, ignore stable/kw reqs, then pay attention to your bugs and fix them :) A.