| 1 |
El lun, 16-02-2015 a las 10:36 -0500, Anthony G. Basile escribió: |
| 2 |
> On 02/16/15 08:34, Pacho Ramos wrote: |
| 3 |
> > Hello |
| 4 |
> > |
| 5 |
> > Every day I am hitting tons of blockers stabilizations and keywording |
| 6 |
> > requests for alpha, sparc, ia64, ppc and ppc64. |
| 7 |
> |
| 8 |
> The powerpc team figured we'd deal with this by being "lax" about |
| 9 |
> keywording/stabilization and catch problems in subsequent bug reports to |
| 10 |
> increase our throughput. We didn't want to drop the entire arch to ~. |
| 11 |
> The team hasn't met since last august, and we should discuss this |
| 12 |
> again. But we decided then that ago would do stabilization and the rest |
| 13 |
> of us would do keywording. |
| 14 |
> |
| 15 |
> As far as I'm concerned, I'm happy to drop all desktop-ish packages to |
| 16 |
> ~arch, but keep the more server-ish, system-ish packages as stable. |
| 17 |
> Controlling @system with stable keywords is very useful for building |
| 18 |
> stages so I'm reluctant to give that up. So maybe we can just adopt the |
| 19 |
> policy that any ppc/ppc64 package which depends on X can be dropped to ~. |
| 20 |
> |
| 21 |
|
| 22 |
Would you mind generating a list of installed packages do you have now |
| 23 |
currently on your ppc* boxes? That would be a good start point to know |
| 24 |
what to preserve :) (I remember I was able to found the list of packages |
| 25 |
in stage3 some months ago but I am now unable to :S) |
| 26 |
|
| 27 |
> > Thanks a lot for your help |
| 28 |
> > |
| 29 |
> |
| 30 |
> No problem. Can you categorize where most of the blockers are coming |
| 31 |
> from? Are they mostly desktop? |
| 32 |
> |
| 33 |
|
| 34 |
They come from multiple places, for example I am now fighting with |
| 35 |
getting ipython finally stabilized after months of waiting because the |
| 36 |
deps hell in python packages (as package A needs package B, B needs C |
| 37 |
and D maintained by others... and the chain keeps growing and growing). |
| 38 |
|
| 39 |
With the current way of passing the stabilization responsibility to |
| 40 |
mostly Ago the problem is that he needs to do stabilization in a more |
| 41 |
"automatized" way as he needs to take care of a lot of arches (all but |
| 42 |
hppa). Then, most of this bugs get stalled forever as we cannot rely on |
| 43 |
any arch team member apart of him to take care of trying to do that job. |
| 44 |
And because of this not only minor arches, even amd64 is blocked by |
| 45 |
this. |
| 46 |
|
| 47 |
On the other hand, arm team has already being able to do that one as his |
| 48 |
arch team members have found all the needed packages to stabilize by |
| 49 |
themselves for ARM :| |
| 50 |
|
| 51 |
> Comments from other ppc people? |
| 52 |
> |
Archives