Hi, 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. Emilio
Hi Emilio, can you give me an example sbuild invocation that produces the effect you see? Thanks! cheers, josch
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
Control: tag -1 + unreproducible I tried this locally by passing a string with a newline to the --make-binNMU option and was unable to make it fail. Thus, tagging with 'unreproducible'. Maybe once somebody encounters this again we can have another try at debugging this? Thanks! cheers, josch