On 12/01/2008, Colin Tuckley wrote: > It's a bit of a historical thing, left over from the days when > everybody used i386 boxes. There is only one i386 buildd (which was > down recently). > > The idea is that since you should be test building your package in a > clean sid chroot anyway you might as well upload the results (after > signing it of course) to save time on Debian resources. But nothing ensures it is built in a chroot, which might occasion disparities between uploaded binaries and built-on-the-buildd-network binaries. And no log is available for that build. Not to mention the disparities between (build-)dependencies' versions in case the package stays in NEW for some time. I find it a shame to rely on everyone to upload binaries to save time on Debian resources, rather than having a comprehensive and reliable buildd network. About the above: it's not like i386 is a rare architecture and it isn't possible to find some machines that could act as build daemons. Remember Vancouver? Cheers, -- Cyril Brulebois
Attachment:
pgpbj69Z_fmnW.pgp
Description: PGP signature