public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure
Date: Sun, 25 Dec 2011 02:56:17 +0000	[thread overview]
Message-ID: <87A32641-7FB0-4B12-B7D7-F303B823256C@stellar.eclipse.co.uk> (raw)
In-Reply-To: <4EF4926A.3080102@gmail.com>


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. 

If you don't report it, then there'll just be a spate of users doing so when libpng15 is stabilised. 

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. 

The sum of your experience and mine is that devs will complain about this only when it suits them. 

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.) 




  parent reply	other threads:[~2011-12-25  2:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  7:00 [gentoo-user] GDM kbd/mouse lockup after emerge --update on a stable amd64 platform - need hints to cure Pintér Tibor
2011-12-22  8:02 ` G.Wolfe Woodbury
2011-12-22 12:58   ` Alex Schuster
2011-12-23  5:12     ` Michael Mol
2011-12-23  5:46       ` Dale
2011-12-23 12:55         ` Michael Mol
2011-12-23 14:02           ` Dale
2011-12-23 10:38       ` Mick
2011-12-23 12:57         ` Michael Mol
2011-12-23 14:05           ` Dale
2011-12-23 14:38             ` Michael Mol
2011-12-23 23:17               ` Dale
2011-12-23 23:47                 ` Neil Bothwick
2011-12-25  2:56               ` Stroller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-22  6:16 G.Wolfe Woodbury

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=87A32641-7FB0-4B12-B7D7-F303B823256C@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@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