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 1ReeHK-00066U-52 for garchives@archives.gentoo.org; Sun, 25 Dec 2011 02:57:38 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D4A5D21C03D; Sun, 25 Dec 2011 02:57:26 +0000 (UTC) Received: from smtpout.karoo.kcom.com (smtpout.karoo.kcom.com [212.50.160.34]) by pigeon.gentoo.org (Postfix) with ESMTP id 8B166E00C2 for ; Sun, 25 Dec 2011 02:56:16 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.71,405,1320624000"; d="scan'208";a="580951511" Received: from 213-152-39-89.dsl.eclipse.net.uk (HELO compaq.stroller.uk.eu.org) ([213.152.39.89]) by smtpout.karoo.kcom.com with ESMTP; 25 Dec 2011 02:56:13 +0000 Received: from [192.168.1.100] (unknown [192.168.1.100]) by compaq.stroller.uk.eu.org (Postfix) with ESMTP id 74A5012666 for ; Sun, 25 Dec 2011 02:52:30 +0000 (GMT) Content-Type: text/plain; charset=us-ascii Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 (Apple Message framework v1251.1) Subject: Re: [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure From: Stroller In-Reply-To: <4EF4926A.3080102@gmail.com> Date: Sun, 25 Dec 2011 02:56:17 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <87A32641-7FB0-4B12-B7D7-F303B823256C@stellar.eclipse.co.uk> References: <20111222135813.42263034@weird.wonkology.org> <201112231038.54812.michaelkintzios@gmail.com> <4EF48AC2.3090105@gmail.com> <4EF4926A.3080102@gmail.com> To: gentoo-user@lists.gentoo.org X-Mailer: Apple Mail (2.1251.1) X-Archives-Salt: c8ba403c-b88a-402a-9769-280d2ce456e9 X-Archives-Hash: 5d39aa4ae1eed32a4ec998b00dd28761 On 23 December 2011, at 14:38, Michael Mol wrote: > ... > Devs don't seem to like bug reports involving mixes of stable and = unstable. I was mildly scolded for filing a bug report against xemacs' = failing to build with libpng15, when xemacs was stable, and libpng15 = wasn't, yet. I'm trying to being slightly more conservative about what I = unmask. The devs are just sometimes grumpy and, as a group, inconsistent. Assuming there isn't already an existing bug report for that issue (just = makes sure you check *thoroughly* - duplicate bug submissions is a pet = peeve of mine) it's perfectly legitimate to report it.=20 If you don't report it, then there'll just be a spate of users doing so = when libpng15 is stabilised.=20 It may very well be that libpng15 hasn't been stabilised for this very = reason, but in that case there should be an existing bug so you don't = waste time reporting the problem. I report bugs all the time saying "please mark this ~x86 package as = stable, works for me on an otherwise mostly stable system" and I never = get any complaints.=20 The sum of your experience and mine is that devs will complain about = this only when it suits them.=20 Gentoo devs are over-worked volunteers, so we must accept such = idiosyncrasies. But please don't stop fling useful bug reports. Stroller. (Searching shows that your report *was* found valuable, and that your = bug was set as a blocker to bug 354479 until bug 385207 was created. = This is *exactly* how it should have been handled, and if you hadn't = reported the issue then someone else would have had to find out the hard = way. The dev's chiding was a poor choice of words - please continue = filing such useful bug reports.)=20