On Fri, Dec 06, 2013 at 11:13:56AM +0000, Thorsten Glaser wrote: > > >> Can somebody remind me how to increase the timeout on a per package base? > > Meh, just crank it globally.
Ok, I set it to 1800 now. But maybe somebody can still tell me how to do it per package nowadays? > >> Or how to tell the build which packages I do not want him to build? Or this? > > Back then we used a unified list that were downloaded from Stephens webspace > > and used by some @includes in the config. I don't know whether this @include > > still works, but when it does we should use that approach again instead of > > maintaining on each buildd such a list. > > That would certainly be welcome. I???m putting packages into Not-For-Us > but then _no_ buildd will pick them up; we have cases where packages > can only reasonably be built on ARAnyM (huge, etc.) or cannot be built > on ARAnyM at all (that thing with L2 caches recently), so we can still > use per-buildd overrides then. I suggest to put kate into not-for-us, and all other (huge) packages that fail due to timeout. If the contents of that list (too-big-for-us) is available, maybe you can pick them on aranym, or all buildds can pick them when all other packages have been built. Or maybe only buildds with >=512MB RAM pick them (the Falcons and aranyms). Which brings me back to my question, how to I exclude packages on one buildd nowadays? Christian -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131206113724.ge26...@chumley.earth.sol
