On Fri, 05 Jun 2009, Luk Claes wrote: > The thing is that it is not a bug in the buildd chroot or buildd > setup, it's a porter issue...
I haven't really analyzed the bug (and only read this thread in the most superficial manner imaginable), so what I said previously (and say below) shouldn't be construed as categorizing this particular bug. That said, I have no problem creating pseudo packages for porter-specific issues as well, though presumably if they're porter-specific issues that primarily impact the buildds, they could be assigned to the buildds, and tagged with the appropriate porter usertag. [At least until the package which is causing the issue on the buildd that is porter specific is identified, anyway.] Don Armstrong -- In all matters of government, the correct answer is usually: "Do nothing" -- Robert Heinlein _Time Enough For Love_ p428 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
