> Dear -devel list,
> Looks like dh_dwz was recently added into debhelper and it is causing some
> FTBFS on one of my packages. It could be a bug of dwz itself but I'm looking
> for some help inside Debian first.
> Please try to build package marisa from its git packaging repo
> https://salsa.debian.org/input-method-team/marisa/commit/f5ff598466266b230d68c9db9f8e31281604b7a6 > ). The following error will pop up when dwz is called:
> dwz: debian/ruby-marisa/usr/lib/x86_64-linux-gnu/ruby/2.5.0/marisa.so: Found
> compressed .debug_aranges section, not attempting dwz compression
> dh_dwz: dwz -q -- debian/ruby-marisa/usr/lib/x86_64-linux-
> gnu/ruby/2.5.0/marisa.so returned exit code 1
> make: *** [debian/rules:30: binary] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned
> exit status 2
> I don't have much experience of dealing with debugging symbols so any hints
> would be appreciated.
dwz currently doesn't handle compressed debug sections. There is some
discussion, if dwz should decompress, do it's work and compress it again.
However until then, don't use compressed debug sections. Apparently these are
turned on by the upstream build system. debhelper maybe could warn about
compressed debug sections in general. Would would you want to have those anyway?
The packages are compressed, and you shouldn't care about the on-disk space
There's also discussion, about errors:
https://sourceware.org/bugzilla/show_bug.cgi?id=24766 Apparently the RPM based helpers ignore the return value of dwz, and leave the
debug symbols unhandled. Again, debhelper could warn about such packages when
built in compat12 mode.