Package: dpkg-dev
Version: 1.18.10
Severity: normal

Dear Maintainer,

debootstrap 1.0.85 began deploying with --merged-usr by default in
response to #839046.  On i386, this causes dpkg-shlibdeps to fail on
(some?) shared libraries.

An example error:
dpkg-shlibdeps: error: no dependency information found for 
/usr/lib/ld-linux.so.2 (used by 
debian/libevas1/usr/lib/i386-linux-gnu/libevas.so.1.18.2)
Hint: check if the library actually comes from a package.

In this case:
# ls -l /usr/lib/ld-linux.so.2
lrwxrwxrwx 1 root root 25 Oct 18 21:10 /usr/lib/ld-linux.so.2 -> 
i386-linux-gnu/ld-2.24.so

To workaround with a pbuilder chroot, when creating, supply:
  --debootstrapopts --no-merged-usr.

I'm not sure if this is a debootstrap or dpkg-dev issue.  Apologies in
advance if I'm incorrect.  The same underlying problem was reported
against usrmerge in #810499.  For some reason, debootstrap does not
create this symlink on amd64.

Ross.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (40, 'unstable'), (30, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dpkg-dev depends on:
ii  base-files    9.6
ii  binutils      2.27-9+b1
ii  bzip2         1.0.6-8
ii  libdpkg-perl  1.18.10
ii  make          4.1-9
ii  patch         2.7.5-1
ii  tar           1.29b-1
ii  xz-utils      5.2.2-1.2

Versions of packages dpkg-dev recommends:
ii  build-essential          12.2
ii  fakeroot                 1.21-2
ii  gcc [c-compiler]         4:6.1.1-1
ii  gcc-5 [c-compiler]       5.4.1-3
ii  gcc-6 [c-compiler]       6.2.0-9
ii  gnupg                    2.1.15-4
ii  gnupg2                   2.1.15-4
ii  gpgv                     2.1.15-4
ii  libalgorithm-merge-perl  0.08-3

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2016.09.04

-- no debconf information

Reply via email to