From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JBJGC-0004xL-BZ for garchives@archives.gentoo.org; Sun, 06 Jan 2008 00:21:04 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id m060KC09004977; Sun, 6 Jan 2008 00:20:12 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id m060IGPK002572 for ; Sun, 6 Jan 2008 00:18:16 GMT Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 2437E65A18 for ; Sun, 6 Jan 2008 00:18:16 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -0.617 X-Spam-Level: X-Spam-Status: No, score=-0.617 required=5.5 tests=[AWL=-0.432, BAYES_40=-0.185] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n63YAyPLfHlP for ; Sun, 6 Jan 2008 00:18:10 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 532B865911 for ; Sun, 6 Jan 2008 00:18:08 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JBJDH-0004h4-IR for gentoo-dev@gentoo.org; Sun, 06 Jan 2008 00:18:03 +0000 Received: from static24-72-113-196.yorkton.accesscomm.ca ([24.72.113.196]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Jan 2008 00:18:03 +0000 Received: from dirtyepic by static24-72-113-196.yorkton.accesscomm.ca with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Jan 2008 00:18:03 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Ryan Hill Subject: [gentoo-dev] Re: Monthly Gentoo Council Reminder for January Date: Sat, 05 Jan 2008 18:17:55 -0600 Message-ID: References: <20080101103002.083C4652C4@smtp.gentoo.org> <54551.192.168.2.159.1199365359.squirrel@www.aei-tech.com> <477D75CA.1030003@gentoo.org> <20080104000155.23e056b4@snowcone> <20080104004653.039f488e@snowcone> <20080104012750.63f4f23a@snowcone> <63044.68.54.223.178.1199445791.squirrel@www.aei-tech.com> <20080104210213.50a99e6b@snowcone> <1199506450.7609.23.camel@inertia.twi-31o2.org> <477FBC0E.2090906@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: static24-72-113-196.yorkton.accesscomm.ca User-Agent: Thunderbird 2.0.0.9 (X11/20071218) In-Reply-To: <477FBC0E.2090906@gentoo.org> Sender: news X-Archives-Salt: 43f497ba-cba1-4a5d-86e4-d83d939c0e2a X-Archives-Hash: 7199ae1b00d59d5bf3aed2526670f019 Luca Barbato wrote: > Chris Gianelloni wrote: >> This has been an issue for quite some time. Of course, the impact is >> debatable, but it seems that we cannot agree ourselves on what is >> agreeable, so I see this as a point to bring to the Council simply so it >> can be resolved "once and for all" and things can resume normal >> operation. > > This thread so far spawned lots of reply from an external contributor > making the point of keeping stale ebuilds around and 4 developers > against the idea proposing different solutions ranging from force update > pending some remote testing to remove the stable keyword for such arches. > > Anything other suggestions? I don't know, I can kinda see both sides. Alt arches tend to be finicky so it's important that updates are well tested on them. Also they're more prone to break during upgrades, not only because they're more fragile but because upstream is far less likely to have tested on them, so I can see why having a stable tree is important. On the other hand, that stable tree is crufting up badly and also prone to breakage just due to being unmaintained. mips have 225 open bugs, 87 of which they are the assignee. i don't really care about open bugs, but some do, and it's making them crabby. I don't think any of the current suggestions are very good, but I don't have anything better, other than we get more mips/alt-arch ppl or access to hardware. Like I said, I'm willing to buy hardware if I can find any (must ship to Nowhere, Canada). Does anyone from the (current) mips team have anything to suggest? > PS: has anybody checked how viable is now qemu-system ? Does it build with GCC 4 yet? -- fonts, by design, by neglect gcc-porting, for a fact or just for effect wxwindows @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 -- gentoo-dev@gentoo.org mailing list