2016-01-12 19:22 GMT+01:00 Guillem Jover <guil...@debian.org>:
> Hi!
>
> On Sat, 2016-01-09 at 21:39:08 +0100, Matthias Klumpp wrote:
>> Hmm, another package showing this behavior (and - unlike apparmor - in
>> a reproducible way) is linux-tools:
>
>> dpkg-shlibdeps: error: no dependency information found for
>> /usr/libx32/libc.so.6 (used by
>> debian/linux-perf-4.2/usr/lib/perf_4.2-core/perf-read-vdsox32)
>> Hint: check if the library actually comes from a package.
>
> dpkg-shlibdeps tries to map a pathname to a package by using
> «dpkg-query --search», if that fails then it will not be able to find
> the matching shlibs file, which seems to be what is happening here.
>
> I guess the combinaion of multilib (which IMO is a bad idea in
> general) plus usrmerge is confusing dpkg-shlibdeps, but I don't think
> this is in principle a bug in dpkg-shlibdeps.
>
> Check your /etc/ld.so.conf.d/* for anything included libx32, and check
> if «dpkg-query --search» knows about that pathname, and if it's the
> canonical one or a symlinked one.
Hmm, everything seems to be in order...
For amd64 sbuild chroot, error message:
dpkg-shlibdeps: error: no dependency information found for
/usr/libx32/libc.so.6 (used by
debian/linux-perf-4.2/usr/lib/perf_4.2-core/perf-read-vdsox32)
Hint: check if the library actually comes from a package.
```
(staging-amd64)root@tglbuild:/# cat /etc/ld.so.conf.d/*
/usr/lib/x86_64-linux-gnu/libfakeroot
# libc default configuration
/usr/local/lib
# Multiarch support
/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu
(staging-amd64)root@tglbuild:/# dpkg-query --search /usr/libx32/libc.so.6
dpkg-query: no path found matching pattern /usr/libx32/libc.so.6
(staging-amd64)root@tglbuild:/# dpkg-query --search /lib64/libc.so.6
dpkg-query: no path found matching pattern /lib64/libc.so.6
(staging-amd64)root@tglbuild:/# dpkg-query --search
/lib/x86_64-linux-gnu/libc.so.6
libc6:amd64: /lib/x86_64-linux-gnu/libc.so.6
```
On the i386 chroot, error message:
dpkg-shlibdeps: error: no dependency information found for
/usr/lib/ld-linux.so.2 (used by
debian/liblockdep4.2/usr/lib/i386-linux-gnu/liblockdep.so.4.2)
Hint: check if the library actually comes from a package.
```
(staging-i386)root@tglbuild:/# cat /etc/ld.so.conf.d/*
/usr/lib/i386-linux-gnu/libfakeroot
# Multiarch support
/lib/i386-linux-gnu
/usr/lib/i386-linux-gnu
/lib/i586-linux-gnu
/usr/lib/i586-linux-gnu
# libc default configuration
/usr/local/lib
(staging-i386)root@tglbuild:/# dpkg-query --search /usr/lib/ld-linux.so.2
dpkg-query: no path found matching pattern /usr/lib/ld-linux.so.2
(staging-i386)root@tglbuild:/# dpkg-query --search /lib/ld-linux.so.2
libc6:i386: /lib/ld-linux.so.2
```
Really weird...
This is also all reproducible on our machines.
Cheers,
Matthias
