public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About reducing or even removing stable tree for some arches
Date: Mon, 16 Feb 2015 17:05:12 +0100	[thread overview]
Message-ID: <1424102712.27408.46.camel@gentoo.org> (raw)
In-Reply-To: <54E20E8E.1020102@gentoo.org>

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?
> 





  parent reply	other threads:[~2015-02-16 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 13:34 [gentoo-dev] About reducing or even removing stable tree for some arches Pacho Ramos
2015-02-16 15:09 ` Rich Freeman
2015-02-16 15:16   ` Pacho Ramos
2015-02-16 15:36 ` Anthony G. Basile
2015-02-16 15:59   ` Joshua Kinard
2015-02-16 23:28     ` Rich Freeman
2015-02-20  8:06     ` Christopher Head
2015-02-16 16:05   ` Pacho Ramos [this message]
2015-02-16 21:22     ` Anthony G. Basile
2015-02-16 22:45       ` Mike Gilbert
2015-02-16 16:37 ` William Hubbs
2015-02-17  4:49   ` Michał Górny
2015-02-16 22:47 ` William Hubbs
2015-02-18  3:11 ` [gentoo-dev] " Duncan
2015-02-18  9:25   ` Pacho Ramos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1424102712.27408.46.camel@gentoo.org \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox