On Tue, Mar 29, 2011 at 8:03 PM, Kurt Roeckx <firstname.lastname@example.org>
On Tue, Mar 29, 2011 at 07:54:59PM +0200, Wesley W. Terpstra wrote:So that in case various packages have to be build in an order,
> If I may ask, for what purpose do the buildds have a special list of
> packages above and beyond those in unstable?
where the seconds depends on the first being available and so on,
that it doesn't take weeks to get them all build. We would have
to wait at least a dinstall before the next one could be build,
assuming sometimes has the time to sign the package between
It basicly just avoids a whole lot of delays.
Unfortunately, it seems also to add quite some delays in the self-compiling case. :-/ Each time a buildd finishes, that buildd's Packages file gets updated due to the completed binary upload and all other buildds go back into the BD-Uninstallable state. (I assume this also means the package loses its place in line on the busy buildd queues)
I wonder if the same rules applied to the unstable package list (don't include the all for a package whose any is not done) could be applied also to the buildd's Packages?