Henning Makholm wrote: > Scripsit Bastian Blank <[EMAIL PROTECTED]> > > > Yes, it was a broken autobuilder, the only autobuilder, the others are > > blocked by the w-b admins. > > How can something really be "blocked by the w-b admins"? The buildds > build .debs from publicly available source packages, don't they? They > upload to the upload queues that are avaiable to every DD, don't they? > > If a DD has a machine with cpu cycles to spend on an architecture > that's lagging behind, what's to stop them from just beginning to > build packages and upload them?
It needs e.g. to take P-a-s into account, for example. > The worst that could happen is a bit > of duplicated work, but that's hardly worse than having the box > sitting around idle until the big evil w-b admin takes pity on it. > If the architecture is _really_ lagging behind, the probability of > duplication work will not be large anyway. > > For real cleverness one could try to second-guess the wanna-build > ordering (UTSL!) and build from the other end of the list. Then cycles > would only be wasted when the queue is nearly empty anyway. Not that clever. The list is ordered for a reason. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]