2016-01-09 21:41 GMT+01:00 Marco d'Itri <m...@linux.it>: > On Jan 09, Matthias Klumpp <matth...@tenstral.net> wrote: > >> Hmm, another package showing this behavior (and - unlike apparmor - in >> a reproducible way) is linux-tools: > I see x32, what are you doing here exactly?
That indeed is a great question, I was wondering the same - I think I need to read dpkg-shlibdeps code to find out. The builds are standard sbuild builds in an amd64 or i396 chroot. Full buildlogs here: http://buildd.tanglu.org/data/linux-tools_4.2-2tanglu3/build_i386/362510/linux-tools_4.2-2tanglu3_i386.273864.log http://buildd.tanglu.org/data/linux-tools_4.2-2tanglu3/build_amd64/362533/linux-tools_4.2-2tanglu3_amd64.273863.log It tries /libx32 only on amd64, /lib otherwise. Chances are there is something else that's busted, but I get the same issue in a plain Stretch chroot...
