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 2623A1381FA for ; Sun, 1 Jun 2014 13:13:16 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 714CFE08C1; Sun, 1 Jun 2014 13:13:11 +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 6FE83E08AC for ; Sun, 1 Jun 2014 13:13:10 +0000 (UTC) Received: from [192.168.1.34] (56.red-80-28-182.adsl.static.ccgg.telefonica.net [80.28.182.56]) (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 0696833FF44 for ; Sun, 1 Jun 2014 13:13:08 +0000 (UTC) Message-ID: <1401628384.790.28.camel@belkin5> Subject: Re: [gentoo-dev] alpha, ia64, ppc, ppc64, sparc developers, need your attention From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Date: Sun, 01 Jun 2014 15:13:04 +0200 In-Reply-To: <538B23B5.3000101@gentoo.org> References: <538B0C00.5010705@gentoo.org> <1401622402.790.16.camel@belkin5> <538B15C7.5070708@gentoo.org> <1401624467.790.21.camel@belkin5> <538B23B5.3000101@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.2 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: 73d644d1-0f21-41a7-9ace-6549c3502932 X-Archives-Hash: b3193035314dc65c76910958376928e4 El dom, 01-06-2014 a las 13:59 +0100, Markos Chandras escribió: > On 06/01/2014 01:07 PM, Pacho Ramos wrote: > > El dom, 01-06-2014 a las 13:00 +0100, Markos Chandras escribió: > >> On 06/01/2014 12:33 PM, Pacho Ramos wrote: > >>> El dom, 01-06-2014 a las 14:18 +0300, Samuli Suominen escribió: > >>>> http://bugs.gentoo.org/show_bug.cgi?id=505962#c6 is blocking > >>>> stabilizing the new virtuals, and thus, converting the tree, and > >>>> also blocking stabilization of the already converted packages > >>>> (gnome seems to have some) pending for 3 months already > >>>> > >>>> thanks, samuli > >>>> > >>> > >>> This makes me wonder about the real status of some of this arches. > >>> I know that now we will probably see how Agostino goes ahead and > >>> does all the work (that is nice and I really welcome his work > >>> trying to keep this arches in shape), but also makes me thing if > >>> makes sense to keep this agostino-dependency for this arches more > >>> and more time. What will occur if he is not around sometime? :/ > >>> > >>> > >> > >> We have been through the same discussion not so long ago and the > >> result was to start dropping the ~m68k, s390 and sh to ~testing[1]. In > >> the thread that started it all[2] there has been no resistance about > >> dropping the keywords of these arches on $subject and here we are > >> again discussing the problem. Here[3] you can see council's decision. > >> I quote here just for fyi: > >> > >> "In summary: > >> - m68k, s390, sh: will be dropped to unstable keywords globally. > >> - alpha, ia64: Maintainers can remove older stable versions according > >> to the "package-by-package" proposal. > >> - sparc: No action. > >> " > >> So unless I make a mistake, you are free to start dropping alpha, ia64 > >> to ~arch. For ppc,ppc64 and sparc it's probably best to resurrect the > >> old thread and possible have add it to the agenda for the next meeting. > >> > >> [1] http://permalink.gmane.org/gmane.linux.gentoo.devel/88183 > >> [2] http://www.gossamer-threads.com/lists/gentoo/dev/277054 > >> [3] > >> http://www.gentoo.org/proj/en/council/meeting-logs/20130917-summary.txt > >> > > > > The problem arrives when even core components like udev takes so long to > > be handled :/ (and situation would be much worse if Agostino doesn't > > have time to make his mass stabilizations... well, each time I report a > > stabilization bug that affects me I cross my fingers expecting ago has > > enough time to handle them ;)) > > > > > > Relying on a single developer handling all architectures clearly does > not scale and it is dangerous. We really need to be realistic and > consider how many stable alpha/sparc/ia64/ppc* users are out there. In > my mind the number is rather small, so does it really worth the effort > trying to keep them stable hurting the remaining stable architectures > and causing significant delays in publishing GLSAs? > The reason I suggested to move the discussion back to the old thread is > that some of these things have already been discussed in the past so I > would like to avoid restarting the discussion from scratch. > Yes, I agree. What I am trying to say is that this discussions usually ends when some people reports that "statistically" they don't take so long to stabilize and don't have so many opened bugs... but that statistics depends on ago being able to do the work recently and, then, it's a chicken-egg problem: we want and need him to stabilize on that arches... but that makes other think the arches are ok in that area while they are really relying on one man work :(