From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HvgqB-0003LC-RP for garchives@archives.gentoo.org; Tue, 05 Jun 2007 21:45:24 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l55LhKGp031742; Tue, 5 Jun 2007 21:43:20 GMT Received: from aa012msr.fastwebnet.it (aa012msr.fastwebnet.it [85.18.95.72]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l55LaEfV020533 for ; Tue, 5 Jun 2007 21:36:15 GMT Received: from [37.1.3.90] (37.1.3.90) by aa012msr.fastwebnet.it (7.3.118.6) (authenticated as cyclopia) id 4665767F0006D374 for gentoo-user@lists.gentoo.org; Tue, 5 Jun 2007 23:36:14 +0200 Message-ID: <4665F834.3000302@gmail.com> Date: Tue, 05 Jun 2007 23:56:36 +0000 From: "b.n." User-Agent: Thunderbird 2.0.0.0 (X11/20070520) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Again: Critical bugs considered invalid References: <20070605150742.GB7993@nibiru.local> <20070605160739.GA21746@crowfix.com> In-Reply-To: <20070605160739.GA21746@crowfix.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 89382dd2-e361-4bcc-8837-c12db003199e X-Archives-Hash: a45f0e08ce0dcd26bd860daa9f624257 felix@crowfix.com ha scritto: > I filed a bug which was promptly closed > for no good reason, only the bogus answer that the new configuraion > files layout took care of it. I reopened it with a more detailed > description of the problem and included the URL of the apache > documentation which explains that the suexec binary has to be compiled > with the USERDIR values known at compile time. A week later, the bug > was properly closed with a better solution than the old 2.2 solution, > and a more permanent solution than my home grown work around. So complaining, in the end, actually worked, isn't it? You had your bug solved in one week. Doesn't look bad at all to me. > Some may remember me from whining a month or two ago about the > atrocious color philosophy with emerge. The reaction both times from > the gentoo community was merely a repeat of what I have come to expect > from several years of my own and from friends' and colleagues' > experiences: blame the messenger. Lash out at the poster, don't > bother to even investigate the problem. When in doubt, scream and > shout, run in circles, pull a pout. No. I remember that thread and as far as I remember you were simply told that there were a lot of things you could do to solve the issue, but that whining of the users mailing list wasn't one of that. And when told to contact emerge developers you just told that their coding style showed they're too dumb people to dishonor yourself going down the stairs from the heavens to earth and talk to them. How it's different that from "When in doubt, scream and shout, run in circles, pull a pout." ? Note that the "atrocious color philosophy" wasn't even actually a bug: was just an annoying usability problem. Given that you were one of the very few to complain about it (not that you didn't have the right to complain, of course: I remember what the problem was and I'm quite sympathetic to you about it: but still, you were one of the few thinking it was actually really important) while other gentoo users happily use emerge and like (or at least do not find "atrocious") its colors, maybe the developers have a point in shifting the color problem down in the priority list. This is a clear case of "The world does not revolve around you" awareness. > I seldom complain any more. It's not worth the hassle and feedback, > and it accomplishes nothing. You just posted an example where you told us that it accomplished a lot in solving the apache bug. > The gentoo developers have enough bad > eggs to tasint everybody. There are plenty of good eggs, but they > need to speak up and stop the bad eggs from ruining their reputation. > I liken it to cops: as long as the good ones won't turn in the bad > ones for framing people, taking bribes, and general corrupt practices, > the good cops are going to be tarred with the same brush as the bad > ones. Oh, please. Gentoo developers are just human beings. Developers are not renowned for their friendliness, and (like everyone else) sometimes they can be rude, nasty, unhelpful or plain stupid. I know that, I understand that. But how can one of the "bad" ones taint the other ones, is beyond my comprehension. Do you think Gentoo developers are a gang of teddy boys? You (and the OP) IMHO suffer of having not enough patience. Patience is a hard virtue to build, and it's painful to deal with. Still, you have to use it to gain something. You can't just do one, two attempts and then throw the towel. If the developer does not understand, try to understand why he does not. Probably your situation resembles a common problem that he's used to see people complain but that it is not a bug (like yours could be instead): explain carefully it. Try to get someone else to reproduce the bug and let him/her add up to your bug report. Show some will to collaborate in solving the problem. Have respect for their work, always: they owe you nothing, they're doing it for *free*, for you. When I did it, the few times I had to report a bug, I had my problems solved in hours or days at most. m. -- gentoo-user@gentoo.org mailing list