> Hi > > As Release Team we would like to know for each buildd on what host it is > running, who is(are) the buildd admin(s), who is the local admin and for what > suites is the buildd configured. To make things more clear, I'll put a fictive > example below: > > hostname: foo.debian.org > architecture: m68k > buildd admin(s): John Doe <[EMAIL PROTECTED]> > local admin: Jane Baz <[EMAIL PROTECTED]> > configured suites: experimental, unstable, testing, testing-security > > Can you please provide us this information? Feel free to provide it in > whatever parseable format or whatever access method. Thanks in advance. > > Currently we are obviously most interested in the m68k buildds for oldstable > and oldstable-security. Though info about the other buildds would also be > appreciated.
Here's my list: hostname: crest.debian.org aka crest.biophys.uni-duesseldorf.de architecture: m68k buildd admin(s): Adam Conrad <[EMAIL PROTECTED]> local admin: Michael Schmitz <[EMAIL PROTECTED]> configured suites: unstable buildd chroots: woody, sarge, etch, sid user chroots: woody, sarge, etch, sid hostname: kullervo.debian.org aka kulllervo.biophys.uni-duesseldorf.de architecture: m68k buildd admin(s): Roman Hodek <[EMAIL PROTECTED]> local admin: Michael Schmitz <[EMAIL PROTECTED]> configured suites: oldstable-security testing unstable buildd chroots: woody, sarge, etch, sid user chroots: woody, sarge, etch, sid hostname: q650.biophys.uni-duesseldorf.de architecture: m68k buildd admin(s): Michael Schmitz <[EMAIL PROTECTED]> local admin: Michael Schmitz <[EMAIL PROTECTED]> configured suites: oldstable-security unstable buildd chroots: woody, sarge, etch, sid user chroots: sid hostname: hobbes.biophys.uni-duesseldorf.de architecture: m68k buildd admin(s): Michael Schmitz <[EMAIL PROTECTED]> local admin: Mark Duckworth <[EMAIL PROTECTED]> configured suites: unstable buildd chroots: sarge, sid user chroots: none hostname: washi (NAT at evil.dnsdojo.org) architecture: m68k buildd admin(s): Michael Schmitz <[EMAIL PROTECTED]> local admin: Michael Schmitz <[EMAIL PROTECTED]> configured suites: oldstable-security unstable buildd chroots: sid user chroots: sid, sid(distcc), woody Note: Regarding configured chroots, crest just needs some reconfiguration for stable and oldstable chroots before these can be re-added. I have only listed the primary buildd admin; I receive log copies for crest and kullervo as well Note2: crest, kullervo and q650 are currently hosted at the bioinformatics group at biophys.uni-duesseldorf.de. According to current schedule, their whole computer installation there will need to relocate to a new room sometime this October (meaning downtimes). I need to negotiate terms of this relocation with my colleagues there, as I'm not going to be in Duesseldorf past August. hobbes is going to relocate with me, this will incur two months of downtime at least. If we get washi fully automated, you should not notice a large backlog. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]