On 03/04/16 06:57, Johannes Schauer wrote: > Hi Emilio, > > I noticed I wrote my reply only to the bts and forgot to CC you. Here it goes > again: > > On Thu, 10 Mar 2016 16:08:37 +0100 Emilio Pozuelo Monfort <po...@debian.org> > wrote: >> I scheduled a binNMU with a newline in the changelog entry (by mistake >> because of some copy&paste from an email), and that broke the buildds. >> >> It'd be good to either accept that or at least fail gracefully. > > can you give me an example sbuild invocation that produces the effect you see?
The problem was when scheduling a binNMU through wb: wb nmu gimagereader_3.1.2+git368fa8f-2 . ANY . unstable . -m "Rebuild against libtesseract3." As opposed to wb nmu gimagereader_3.1.2+git368fa8f-2 . ANY . unstable . -m "Rebuild against libtesseract3." Note the newline in the bad invocation. That newline confused the buildds, which got stuck in "building" state. Unfortunately there are no logs in e.g. https://buildd.debian.org/status/logs.php?pkg=gimagereader&arch=i386 so I can't provide that. Cheers, Emilio
