| 1 |
On Tue, Nov 30, 2010 at 8:02 PM, Jorge Manuel B. S. Vicetto |
| 2 |
<jmbsvicetto@g.o> wrote: |
| 3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> Hash: SHA1 |
| 5 |
> |
| 6 |
> On 29-11-2010 10:34, Sebastian Pipping wrote: |
| 7 |
>> On 11/29/10 09:35, Arfrever Frehtes Taifersar Arahesis wrote: |
| 8 |
>>> There will probably be no active version of Python set. |
| 9 |
>> |
| 10 |
>> You had two weeks to come up with this. |
| 11 |
>> |
| 12 |
>> Please find my on IRC to team up on an agreed fix. |
| 13 |
> |
| 14 |
> As Arfrever noted, this is likely the cause of the broken automated |
| 15 |
> weekly stages for this past week. By not having a python symlink / |
| 16 |
> wrapper, stages generation failed on stage2 run. |
| 17 |
> I'd like to take this chance to recall this is the 2nd time on the last |
| 18 |
> few months where stage generation was broken by python changes. Also, |
| 19 |
> we've been unable to create hardened stages for over 8 weeks because of |
| 20 |
> a sandbox issue. |
| 21 |
> The weekly stages generation depends on the quality and stability of the |
| 22 |
> "stable" tree. Therefore, the RelEng team kindly asks all maintainers to |
| 23 |
> pay attention to the stable ebuilds in the system set and to please fix |
| 24 |
> any failures asap as they may / can prevent stage generation. Be sure to |
| 25 |
> think carefully about changes that can impact the stage generation, in |
| 26 |
> particular when they involve python. |
| 27 |
|
| 28 |
Two issues: |
| 29 |
|
| 30 |
proj/en/releng is old as hell and doesn't even mention stage generation. |
| 31 |
|
| 32 |
How does a developer know when the stage generation is broken? Is |
| 33 |
there a dashboard? At work we have a guy who is basically a build cop |
| 34 |
and checks our build dashboard once a day or so and if it is broken he |
| 35 |
goes and finds the guy who broke it and punches him in the face until |
| 36 |
he fixes it. I imagine we do not have staff for this (and no one has |
| 37 |
invented punching over the internet.) |
| 38 |
|
| 39 |
I am curious how often stage builds fail (how long can they be broken |
| 40 |
until we actually care?) |
| 41 |
|
| 42 |
> |
| 43 |
>> Sebastian |
| 44 |
>> |
| 45 |
> |
| 46 |
> - -- |
| 47 |
> Regards, |
| 48 |
> |
| 49 |
> Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
| 50 |
> Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng |
| 51 |
> -----BEGIN PGP SIGNATURE----- |
| 52 |
> Version: GnuPG v2.0.16 (GNU/Linux) |
| 53 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 54 |
> |
| 55 |
> iQIcBAEBAgAGBQJM9cjoAAoJEC8ZTXQF1qEPdC0QAK0HLSse/T3XUL9+vjp3VHro |
| 56 |
> xXED/VsiXLlJtwlEsfWLf5kkMhejEXTO5gbLWZmqaJynOCFBk55eqQz04YXZQqWv |
| 57 |
> XmtEnXzaf+394chTaWV3hPIzuVayZzJRtVJhEj1imbgLIa3Qyx7XJjpC4NwH2MVo |
| 58 |
> 1Odef7Eh8vhpE2bD48BxJfp9KGIf+MQf0TPex/4TACirYzJ60J4aGZ627gbzyaym |
| 59 |
> 3o9DoLD1DRRrURO66buLyV2eXvnMrNrO3UYKPP1M93uW1hq4RXZRGJ4oGePbBfwQ |
| 60 |
> JuoGNc227lixeaivlLA83AOQbfYM3OW8zuM1l2kVMNSvzeVyh/wEx9U9ptvLhhLR |
| 61 |
> nd0FJNt8RsIH8Yzi5NUfv4JMJoAQK5km2kNVFH1bE8vVp+RwyTVFPnuCtdNL1uLJ |
| 62 |
> rVl+ptrF/Aiey5u/gVXpYSZGjU/lYtp73EebZhO+Bn1mymGMNVr2/UU9HWgCowmN |
| 63 |
> so0AIcKa5NkT5L4Y3kI+bSokcrm/5bLbjZQ5MayWsRuEwJkWyt1vxfW2B2DaQbjQ |
| 64 |
> +hRezNy/GwnfLM21yEYn46h5RnArdtV3vT6J6vksG+4aepa6WNAFnw47ABJW63z0 |
| 65 |
> jAL8n/qjrsi2PJlUdrbZ230iqIFV1RmPtP5Z7M9gAM4VAtb8dNPWxB2ooEYOqg6u |
| 66 |
> 8yAYnSVjKv/dTK7nPhSk |
| 67 |
> =gX34 |
| 68 |
> -----END PGP SIGNATURE----- |
| 69 |
> |
| 70 |
> |
Archives