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=1.2 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI, RDNS_NONE autolearn=no autolearn_force=no version=4.0.0 Received: from winkin.phpwebhosting.com (unknown [64.239.40.196]) by chiba.3jane.net (Postfix) with SMTP id B7E03AC797 for ; Tue, 23 Jul 2002 17:55:18 -0500 (CDT) Received: (qmail 23771 invoked by uid 508); 23 Jul 2002 22:55:17 -0000 Received: from unknown (HELO gentoo.org) (128.227.142.237) by winkin.phpwebhosting.com with SMTP; 23 Jul 2002 22:55:17 -0000 Message-ID: <3D3DDE5A.2080909@gentoo.org> Date: Tue, 23 Jul 2002 18:53:14 -0400 From: Doug Goldstein User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020722 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gentoo-dev@gentoo.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [gentoo-dev] Bugs Bugs Bugs & Unstablity 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: 946ece0f-8318-4acc-879e-6f53e4c31b1c X-Archives-Hash: 97af404a2ed4f89cb8b65609b8af70c3 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. -- Doug Goldstein Developer (Laptops, WiFi, GCC-3.1) Gentoo Linux http://www.gentoo.org/~cardoe/