On 09/22/2010 06:39 AM, Christian PERRIER wrote: > Quoting Gaudenz Steinlin (gaud...@debian.org): > >> IMHO the most prominent gap is that there is no indication if a buildd >> fails to upload a log to d-i.debian.org at all. Like it is the case for >> several architectures since Aug 17th. >> >> I could not find any information about how the process of scheduling d-i >> builds on buildds works. Thus I don't know where to start to improve the >> status reporting there. I would really appreciate if someone could >> provide a pointer to existing documentation or scripts driving this >> process. > > > Luk Claes has been the person setting this up on the buildds. So, I > think having him in the loop is the best action. Luk?
The mips* buildds were changed, the promess was made to have the d-i builds moving to the new buildds, but due to several reasons that did not happen up to now. The hppa ones just failed miserably at the time and I did not get them working again, though I did not look since quite some time. The powerpc and s390 ones probably still work, though do not happen currently. I'll have a look when I'm back from VAC. Regarding the CD images it's probably a matter of changed machines (key issue). It does not currently happen differently on the buildd than on personal machines btw, it's just a separate environment on the buildd where the d-i builds happen as documented in the d-i repository. Cheers Luk -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c9a61df.90...@debian.org
