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 1OHCVJ-0004SL-U8 for garchives@archives.gentoo.org; Wed, 26 May 2010 09:02:22 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9C06DE0B64; Wed, 26 May 2010 09:02:07 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 67128E0B2B for ; Wed, 26 May 2010 09:01:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id F1E231B41E1 for ; Wed, 26 May 2010 09:01:41 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 required=5.5 tests=[AWL=0.049, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M24ZBYVqEzgS for ; Wed, 26 May 2010 09:01:34 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by smtp.gentoo.org (Postfix) with ESMTP id 681E31B41E3 for ; Wed, 26 May 2010 09:01:33 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OHCUP-0006mc-Fb for gentoo-dev@gentoo.org; Wed, 26 May 2010 11:01:25 +0200 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 May 2010 11:01:25 +0200 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 May 2010 11:01:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org connect(): No such file or directory From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: bug wrangler queue is large... Date: Wed, 26 May 2010 09:01:16 +0000 (UTC) Message-ID: References: <201005180802.09430.mail@akhuettel.de> <20100525200807.GA1515@boostbox> <4BFC3BDF.8060608@gentoo.org> <201005251803.20423.vapier@gentoo.org> <87typvi5r0.fsf@newton.gmurray.org.uk> 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=UTF-8 X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies; GIT 9895ed0 branch-testing) Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 9157be35-d700-4e2b-a1c8-ce26e262ca66 X-Archives-Hash: 98d9e6568a9759e0a77081ee36b933a7 Graham Murray posted on Wed, 26 May 2010 06:36:35 +0100 as excerpted: > Mike Frysinger writes: >=20 >> the bug reporter can open their own bugs. gentoo developers can open >> any bug. that's about it. >=20 > Which can be a pain for other users who suffered the same bug (and are > probably on the CC list), the maintainer says to re-open if the problem > is not fixed, the user finds the problem is still there but the bug > reporter does not re-open the bug. All you can do is add a comment and > hope that a developer sees it and re-opens the bug. That's what clone bug is for... or at least what /I/ use it for. If I'm=20 not the bug OR/owner and I'm still seeing the bug, I can't open the=20 existing one, but I can clone it, with an explanation why, about the best= =20 that can be done under the circumstances. It's then upto the wranglers whether they want to reopen the old one and=20 make the new one a dup, or occasionally there's different minor details=20 (maybe a patch didn't get applied or doesn't apply to a new version), and= =20 it can be argued to be a new bug, simply related to the old one. Either=20 way, the wranglers or package maintainer get to decide. --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman