From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 65268138A1A for ; Mon, 16 Feb 2015 16:05:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1D662E0969; Mon, 16 Feb 2015 16:05:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1F48DE089C for ; Mon, 16 Feb 2015 16:05:19 +0000 (UTC) Received: from [192.168.1.34] (14.Red-2-137-247.dynamicIP.rima-tde.net [2.137.247.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 014073403A3 for ; Mon, 16 Feb 2015 16:05:16 +0000 (UTC) Message-ID: <1424102712.27408.46.camel@gentoo.org> Subject: Re: [gentoo-dev] About reducing or even removing stable tree for some arches From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Date: Mon, 16 Feb 2015 17:05:12 +0100 In-Reply-To: <54E20E8E.1020102@gentoo.org> References: <1424093690.27408.35.camel@gentoo.org> <54E20E8E.1020102@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: b2cc6947-a091-455b-979b-027f981128e5 X-Archives-Hash: 4bd6145079322a7fc95359c5b143abd8 El lun, 16-02-2015 a las 10:36 -0500, Anthony G. Basile escribió: > On 02/16/15 08:34, Pacho Ramos wrote: > > Hello > > > > Every day I am hitting tons of blockers stabilizations and keywording > > requests for alpha, sparc, ia64, ppc and ppc64. > > The powerpc team figured we'd deal with this by being "lax" about > keywording/stabilization and catch problems in subsequent bug reports to > increase our throughput. We didn't want to drop the entire arch to ~. > The team hasn't met since last august, and we should discuss this > again. But we decided then that ago would do stabilization and the rest > of us would do keywording. > > As far as I'm concerned, I'm happy to drop all desktop-ish packages to > ~arch, but keep the more server-ish, system-ish packages as stable. > Controlling @system with stable keywords is very useful for building > stages so I'm reluctant to give that up. So maybe we can just adopt the > policy that any ppc/ppc64 package which depends on X can be dropped to ~. > Would you mind generating a list of installed packages do you have now currently on your ppc* boxes? That would be a good start point to know what to preserve :) (I remember I was able to found the list of packages in stage3 some months ago but I am now unable to :S) > > Thanks a lot for your help > > > > No problem. Can you categorize where most of the blockers are coming > from? Are they mostly desktop? > They come from multiple places, for example I am now fighting with getting ipython finally stabilized after months of waiting because the deps hell in python packages (as package A needs package B, B needs C and D maintained by others... and the chain keeps growing and growing). With the current way of passing the stabilization responsibility to mostly Ago the problem is that he needs to do stabilization in a more "automatized" way as he needs to take care of a lot of arches (all but hppa). Then, most of this bugs get stalled forever as we cannot rely on any arch team member apart of him to take care of trying to do that job. And because of this not only minor arches, even amd64 is blocked by this. On the other hand, arm team has already being able to do that one as his arch team members have found all the needed packages to stabilize by themselves for ARM :| > Comments from other ppc people? >