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