On 2019-07-15 08:35 +0200, Ole Streicher wrote: > I have a larger package (eso-midas) that built successfully over the > last years. However, a new binNMU failed last night on > mips/mipsel/mips64 with the cryptic error message > > dh_dwz -a > dh_dwz: dwz -q > -mdebian/eso-midas/usr/lib/debug/.dwz/mipsel-linux-gnu/eso-midas.debug > -M/usr/lib/deb[...lengthy argument list...] returned exit code 1 > make: *** [debian/rules:25: binary-arch] Error 255 > > full log: > https://buildd.debian.org/status/fetch.php?pkg=eso-midas&arch=mips&ver=19.02pl1.0-1%2Bb1&stamp=1563134252&raw=0 > > which I do not understand. > > Is this a bug in dwz?
Most likely yes. My hunch is that one or more of the input files is missing the .debug_info section, and the version of dwz used for the build (0.12.20190710-1) silently exits unsuccessfully on those. This has been fixed in the next dwz upload: ,---- | dwz (0.12.20190711-1) unstable; urgency=medium | | * New upstream snapshot. | - If .debug_info section not present, exit with 0. | | -- Matthias Klose <[email protected]> Fri, 12 Jul 2019 00:25:25 +0200 `---- However, that version did FTBFS on mips*. :-( > Can I just disable dh_dwz? Surely, dh_dwz is just an optimization tool to reduce the size of the debug information, so that the -dbgsym packages become smaller. Cheers, Sven
