Niko Tyni wrote: > dh_shlibdeps doesn't work on -dbg packages containing "real" unstripped > libraries in usr/lib/debug. This path is pruned from the search, > apparently to skip scanning split debugging symbols (see #215670). > > This looks like incorrect behaviour to me; policy 8.6 says to run > dpkg-shlibdeps on all shared libraries and compiled binaries. > > Are there problems scanning the debugging symbol files or is this > just an optimization? I can't see any NEEDED fields in eg. > /usr/lib/debug/bin/zsh4.dbg .
I'm unsure about older versions of dpkg-shlibdeps. The current, insanely smart version, doesn't get too upset when run on split debugging symbol files: [EMAIL PROTECTED]:~package/aalib>dpkg-shlibdeps /usr/lib/debug/usr/lib/libaa.so.1.0.4 objdump: /usr/lib/debug/usr/lib/libaa.so.1.0.4: Invalid operation (The return code is zero.) Raphael, is the objbump message above passed through intentionally? If dpkg-shlibdeps didn't print that message at all and silently skipped separated debug symbol files, I'd be inclined to make dh_shlibdeps not exclude anything in usr/lib/debug. If the message is intentional or cannot be gotten rid of, it seems that dh_shlibdeps should be changed to use a tighter exclude pattern, maybe including usr/lib/debug/*.so* while excluding anything else under usr/lib/debug .. -- see shy jo
signature.asc
Description: Digital signature
