1 |
El mié, 18-02-2015 a las 03:11 +0000, Duncan escribió: |
2 |
> Pacho Ramos posted on Mon, 16 Feb 2015 14:34:50 +0100 as excerpted: |
3 |
> |
4 |
> > The current policy of maintainers dropping keywords after 90 days is |
5 |
> > simply not applied because it leads up to that maintainer needing to |
6 |
> > kill himself that keyword and ALL the reverse deps keywords and, then, |
7 |
> > all that effort should probably be replaced by making the opposite, I |
8 |
> > mean, reducing the stable tree of that arches to a minimum and moving |
9 |
> > all the other packages to testing. The main advantage of this is that it |
10 |
> > needs maybe more effort in one round but it solves the problem for the |
11 |
> > future. On the other hand trying to kill keywords of a package *and all |
12 |
> > its reverse deps* requires a lot of work every time the problem appears. |
13 |
> |
14 |
> Perhaps my non-dev status prevents me from understanding the difficulty |
15 |
> here, but... I really don't see the problem. |
16 |
|
17 |
Maybe that explains it, I have personally suffered it when we needed to |
18 |
dekeyword most gnome stuff on all arches but amd64/x86 and even months |
19 |
later we were still needing to remember to either keep moving to testing |
20 |
other packages or finally postponing the move to testing for some and |
21 |
try to stabilize some again (as the chain of reverse dep kept growing |
22 |
forever). |
23 |
|
24 |
I don't want to have to repeat that for every package that is not |
25 |
attended in 90 days, and seeing that the arch teams that are unable to |
26 |
stabilize/keyword things are, consequently, also unable to make this |
27 |
huge work, the 90 days policy isn't going to start working any time soon |
28 |
(it has never worked indeed as nobody wants to do the manual job of |
29 |
checking all the reverse deps, move that deps to testing, recheck for |
30 |
the reverse deps of those, and repeat and repeat). |