On Sun, Mar 28, 2010 at 09:28:43AM +0200, Wouter Verhelst wrote: > On Sat, Mar 27, 2010 at 11:13:20PM +0100, Kurt Roeckx wrote: > > On Fri, Mar 26, 2010 at 03:11:12PM +0100, Raphael Hertzog wrote: > > > On Fri, 26 Mar 2010, Marc 'HE' Brockschmidt wrote: > > > > You mean like the existing pages on buildd.debian.org? You just need to > > > > feed them the list of affected packages to get that. > > > > > > Good if it can be done with a simple link to buildd.debian.org! It would > > > still be nice to be able to attach some information like bug numbers near > > > FTBFS so that people managing the transitions know whether all failures > > > have been reported. > > > > If the buildd maintainer adds the bug number when he sets the > > package to failed state, you can see that and it will provide a > > link to the bug. But not all buildd maintainers have the time > > to follow up on all the failed build mails they get, see if there > > is an open bug or file a bug report, ... > > With old buildd, it was always possible to add this bug # after the > fact. I don't know what the case is with new buildd/new wanna-build, but > it might be a good idea to look into that...
You can still append messages to the failed messages. > ...and to allow random DD's to add to the description of a failure > state, so that those who want to can add bug numbers. Current random DDs don't have write access. Kurt -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100328155419.ga20...@roeckx.be
