Ah, never mind me. It was the very last change I made that seems to have tickled this problem. Uploading shortly.
On Mon, 12 Aug 2019 at 22:19, Brendan O'Dea <b...@c47.org> wrote: > This is due to a sanity check that I've added to ensure that everything is > prepared for an "upstream" release to both Debian and GNU. This is the > first time in ~16 years of the package containing an arch-specific binary > that I've come across a case where a bin-NMU has been required for > help2man. Out of curiosity, why? libc update? > > I'll upload a change shortly to skip these checks if the version number > matches the bin-NMU pattern. > > On Mon, 12 Aug 2019 at 22:03, Ivo De Decker <iv...@debian.org> wrote: > >> package: src:help2man >> version: 1.47.10 >> severity: serious >> tags: ftbfs >> >> Hi, >> >> The latest version of help2man in unstable fails on i386 because it was >> binNMUed there: >> >> https://buildd.debian.org/status/package.php?p=help2man >> >> dpkg-buildpackage >> ----------------- >> >> Command: dpkg-buildpackage -us -uc -mamd64 / i386 Build Daemon >> (x86-ubc-02) <buildd_amd64-x86-ubc...@buildd.debian.org> -B -rfakeroot >> dpkg-buildpackage: info: source package help2man >> dpkg-buildpackage: info: source version 1.47.10+b1 >> dpkg-buildpackage: info: source distribution sid >> dpkg-source --before-build . >> dpkg-buildpackage: info: host architecture i386 >> fakeroot debian/rules clean >> test -x configure # autoconf has been run >> grep -qF 'help2man-1.47.10+b1.tar' README # exists and up to date >> make: *** [debian/rules:122: check-maint-prep] Error 1 >> dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned >> exit status 2 >> >> Cheers, >> >> Ivo >> >
