[1:01pm] ij: NCommander: hi... I've read your mail, but I'm a little bit reluctant, because I don't know if your buildd is somewhat an official one, that accesses the same wanna-build db as the existing buildd...
[1:01pm] NCommander: The existing buildd been down for awhile
[1:02pm] ij: but you're using aurel32s wanna-build db?
[1:03pm] NCommander: I'd be using the offical one to my knowledge (I'm setting up the autobuilder per the offical instructions)
[1:13pm] NCommander: The main reason I wanted it listed so there would be a centralized list of autobuilders, but I'll run it separate if that's a problem
[1:22pm] ij: NCommander: aurel32 said that there was a new buildd called raptor added lately... basically I don't mind adding new buildds to the database, but adding a buildd that doesn't work on the official w-b database won't make sense, so it would be better if you try to get it added to the w-b that is run by aurel32
[1:27pm] NCommander: oh I see
[1:30pm] ij: NCommander: the problem is: when there a two buildds listed on different w-b databases, you'll get inconsistency between those things on buildd.net like "Hey, I saw on buildd.net that the package is being built on foo, but it's still not uploaded!"
[1:30pm] NCommander: Oh I see
[1:30pm] NCommander: and since Hurd is using kfreebsd/armel wanna-build vs the offical
[1:30pm] NCommander: It's going to blow up in our faces
[1:33pm] ij: sort of... aurel32 is operating w-b for some archs, like hurd-i386, kfreebsd-amd64 and -i386 and armel... that's the official w-b so long, because these archs are not included on buildd.debian.org
[1:33pm] ij: but basically all buildds for one arch should work on one single w-b database
[1:35pm] NCommander: Right