Ingo Juergensmann wrote: > On Thu, Jun 28, 2007 at 08:38:04AM +0200, Luk Claes wrote: > >> 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. > > A first, quick overview, which lacks oldstable:
Thanks. What do the 't' and 'f' mean in the table? > I would be interested in keeping the database on buildd.net uptodate as well > (http://unstable.buildd.net/index-m68k.html), so if anything of the above is > wrong or missing, keep me updated as well, please. Is the above table available on http://unstable.buildd.net? > For the local admins, there's the following information on that page: > Some addition to the above: Thanks. > If there's need, release team can have direct access to the Buildd.Net > database. I still need to add etch-m68k and sarge-bpo/sarge-volatile to > Buildd.Net. I guess that would only make sense when the table above is not available http://unstable.buildd.net, but thanks anyway. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
