Buildd fun

So we've been setting up buildd machines for the armeb people (got some comments from some other people that it should actually have been armbe, but I'm not going to give my opinion on that one). After a few days, we now have a working wanna-build setup, and one buildd properly configured (a second one coming RSN^TM), though there's no working dak-enabled upload queue yet.

Of course, buildd had to be lazy again:

Sep 25 11:03:47 buildd: unstable: total 9222 packages to build.
Sep 25 11:03:49 buildd: Nothing to do -- sleeping 300 seconds

IOW, there's 9222 source packages in unstable ATM, but buildd decides it likes none of them and goes to bed for another 5 minutes. Crazy thing. So, I send it a USR1 as soon as I notice, and look:

Sep 25 11:08:34 buildd: My config file has been updated -- rereading it
Sep 25 11:10:12 buildd: unstable: total 9222 packages to build.
Sep 25 11:10:15 buildd: Updated source-dependencies
Sep 25 11:10:43 buildd: Updated apt sources for unstable
Sep 25 11:10:48 buildd: Autocleaned apt cache directory for unstable
Sep 25 11:10:48 buildd: Starting build (dist=unstable) of:
Sep 25 11:10:48 buildd: db3_3.2.9-22

Ahh, much better.

Joerg Jaspert suggested buildd was scared off by the insane amount of packages it had to work through. Well, possibly; but I couldn't care less. They have to be built, darn thing.