Re: buildd chroot creation: who should get notified of failures?

2017-12-23 Thread Peter Palfrader
On Sat, 23 Dec 2017, Peter Palfrader wrote: > > I think they should keep going to DSA and we should take care of them. > > Maybe we should just log them to disk. Continuing to send mails about > failures seems not too useful. And in turn also run the dsa-check-dchroots-current check not only on

Re: buildd chroot creation: who should get notified of failures?

2017-12-23 Thread Peter Palfrader
On Fri, 22 Dec 2017, Julien Cristau wrote: > On Thu, Dec 21, 2017 at 10:45:52 +0800, Paul Wise wrote: > > > Hi folks, > > > > Occasionally the buildd (and porterboxen) fail to debootstrap updated > > chroots. Sometimes these are Internet problems, sometimes local network > > problems, sometimes

Re: packages that FTBFS twice in a row ...

2017-12-23 Thread Mattia Rizzolo
On Sat, Dec 23, 2017 at 08:27:50AM +, Holger Levsen wrote: > On Fri, Dec 22, 2017 at 10:43:34PM +0100, Mattia Rizzolo wrote: > > So, yes, source packages can be built reproducibly! > > neat, thanks for pointing this out! In which version of dpkg was that > feature? dpkg (1.18.11) unstable; ur

Re: packages that FTBFS twice in a row ...

2017-12-23 Thread Holger Levsen
On Fri, Dec 22, 2017 at 10:43:34PM +0100, Mattia Rizzolo wrote: > Actually, Guillem went ahead and did this himself. He also thought it > would be hard, but after trying only few changes to dpkg were needed. > Look: [...] > So, yes, source packages can be built reproducibly! neat, thanks for poi