-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01-12-2010 19:13, Alec Warner wrote: > On Tue, Nov 30, 2010 at 8:02 PM, Jorge Manuel B. S. Vicetto > <jmbsvice...@gentoo.org> wrote: > 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.
Yeah, as everywhere else in Gentoo we could use more man power in RelEng. >> 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.) Lately I've become that guy for the amd64 and x86 builds. I've been going after maintainers to get the issues that are breaking stages fixed. I haven't tried "punching" anyone yet, though ;-) >> I am curious how often stage builds fail (how long can they be broken >> until we actually care?) They've been failing a bit in the past 6 months or so. We have some issues that affect all arches and others that affect specific arches. The worst and longest issue in the recent past was the mess with python-3.1 that lead to catalyst to die when python3 was becoming the main interpreter in stage1. We lost stages for a few months before we acted on that one. The previous issue that still affected this weeks stages build was the issue with sandbox that prevented any stages from being built for the past 2 months. This last issue with python was first reported for the ppc builds on 20101128. I only found out yesterday when I was poked by Raúl (armin76) as I missed all Gentoo emails for the previous 10 days. For random issues I generally start worrying on the 2nd email. - -- 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/ iQIcBAEBAgAGBQJM9uYXAAoJEC8ZTXQF1qEPJkcP/jMau8sJ5UObjIGrGHeXODgB k76hNPm5j64jjqiQnqByevukIYQ0VfZhEbCcvRRdlMRzVfDoukmDx26372bZVO8d VkkS5JUmWxVR392W9flZqJw85DlrOB4p7HlxfjamgcsCxzrKVkKAqVDQcQkDGQOB qCOeDfLlijWOuc1bLMDUsQo1dYCr1XSKvsuY37lC6oQf5oCHr5a1+4xdhto1EbGr ASq3O9aKu/J+YLGI7rZtet5Lm8kAS803j6DLz0t15/I8obHzx+CeIzFLyr9Bly72 yL9DqU3aQ7xGFEI/GvCcS0vEOiile1VAT/YDLJAE3e24fs6r7Bf6PD1bUXoTiuAR tOGEJNwpj0Pa5lQoEs7Xe/xaY7W3YkoHe5QmyA8MNa2VyDpoMEm9HJkNH8IumyIn to68EOc4lHLHCYnm3CFa3C83jP6l3oq04VRlrs/D+geDP2rdTCCXvU8eg8O+c1NV buca8gK7iuA1sqHZWmInKSKp679Suw82rh7AxPJgXPc/YOzinhtBcMad3XmGmU4g XdoAXm5VWmO7/fj7ssCK9lzAWGn9ZaDKqGSl3rgpDkSTn7p7/Pih3OCcdcwoI/Gp uoJ/QD0eI8KAn6OTMN6UWr/i6P/Ys58m7dStKODsyboLejjtZMANbu1KiUKuumix AYLQ86te5Evz78MaFxeb =Yo6Y -----END PGP SIGNATURE-----
