1 |
On Sun, Nov 16, 2008 at 2:42 AM, Torsten Veller <tove@g.o> wrote: |
2 |
> It is time to finish the move of some new dual-lifed perl modules |
3 |
> from dev-perl to perl-core (plus virtual/). It involves updating of |
4 |
> 120 packages all over the tree but mostly in dev-perl. |
5 |
> |
6 |
> As this takes some time the tree will be inconsistent until it is |
7 |
> finished. I don't know how long it'll take. |
8 |
> |
9 |
> So the question is: |
10 |
> Can we stop updating the rsync mirrors during that time easily? |
11 |
|
12 |
I'm sure if you make a proposal to infra on a time window[1] they can |
13 |
possibly assist you. |
14 |
|
15 |
> Or even better: Can *I* stop it? |
16 |
|
17 |
not at this time, no. |
18 |
|
19 |
> |
20 |
> As there were problems while moving packages before, I remember we |
21 |
> were talking about a way to stop updating rsync mirrors from cvs. |
22 |
> I guess nothing was implemented? |
23 |
|
24 |
I lost interest in this proposal as it seemed to not needed very often. |
25 |
It would be trivial to implement if ebuild developers think it is a priority. |
26 |
|
27 |
> |
28 |
> Thanks. |
29 |
> |
30 |
> |
31 |
|
32 |
[1] 'Now - until I'm finished' is typically an invalid window. I |
33 |
suggest you make some estimates on how long the moves will take you. |
34 |
Also give yourself some cushion time and make sure you have enough |
35 |
time to back out of the chance in case something goes awry. |