From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=0.3 required=5.0 tests=DMARC_MISSING, MAILING_LIST_MULTI,RDNS_NONE autolearn=no autolearn_force=no version=4.0.0 Received: from mailres.fastwebnet.it (unknown [213.140.2.43]) by chiba.3jane.net (Postfix) with ESMTP id 983D1ABD86 for ; Tue, 23 Jul 2002 18:08:48 -0500 (CDT) Received: from fastwebnet.it (1.254.34.233) by mailres.fastwebnet.it (6.5.026) id 3D24621D001A0B0E for gentoo-dev@gentoo.org; Wed, 24 Jul 2002 01:08:47 +0200 Message-ID: <3D3DE202.6030409@fastwebnet.it> Date: Wed, 24 Jul 2002 01:08:50 +0200 From: Stefano Peluchetti Reply-To: pelux@fastwebnet.it User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020622 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gentoo-dev m-list Subject: Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity References: <3D3DDE5A.2080909@gentoo.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 566c6dde-1d09-49f1-a1e5-e70b87205785 X-Archives-Hash: 27f8097e94e75d2a478f5ebd8eda427a Doug Goldstein wrote: > All I ever hear or read about is people complaining about bugs or > stability issues or an ebuild problem. Granted I'm not complaining about > this, this is good... we need to know this. But there is one thing > missing... I go to http://bugs.gentoo.org and sort through the bugs and > there are hardly any bug reports for the problems people say. > > Here's a couple things I'd like to see our users do as far as bugs > 1) Fill out bug reports @ http://bugs.gentoo.org > 2) Provide us with all the necessary details... for example... if you > just tell me that libfoo's latest ebuild doesn't compile for you. That > is definetly not enough detail. Provide the FULL version including our > ebuild revision, such as libfoo-1.0.1-r1.ebuild is what we'd like to see. > 3) You NEED to tell us which version compiler you are using. > 4) You need to tell us your USE flags and your CFLAGS > 5) Provide us with a copy and paste of the exact error message. > 6) Any other data you feel might be revelant. > > If you do all that more bugs will be fixed and they will hopefully be > fixed faster. > > And if the person who sent me the patch against the latest version of > pcmcia-cs over IRC in a /query while I was gone is here.... please fill > out a bug report and lemme know what it fixes and include it. My battery > on the laptop ran out while I was gone. > > In conclusion, you need to submit your bugs and concerns in a reliable > fashion so that they can be properly addressed... the only way to do > that is to fill out a bug report. > I have already mentioned this, see my last reply to the previous thread. Bye Stefano Peluchetti