Bug#885219: /lib64 provision added in 9.1.1 prohibits multilib libc
Package: debian-policy
Version: 4.1.2.0
Severity: important
As explained by Aurelian Jarno:
>> 9.1.1
>> Only the dynamic linker may install files to /lib64/.
> How is that supposed to work for the multilib glibc? For example
> libc6-amd64:i386 installs all its libraries into /lib64. We don't want
> to install these files in the multiarch path, as they will collide with
> the libc6:amd64 package. This is actually forbidden by the same
> paragraph of the policy (and that's a good thing).
>
> In the long term we should get ready of multilib now that we have
> multiarch, but it seems it's not something we are ready to do yet.
The best fix appears to be to exempt libc from this requirement (confirmed
in a later message).
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debian-policy depends on:
ii libjs-sphinxdoc 1.6.5-3
debian-policy recommends no packages.
Versions of packages debian-policy suggests:
pn doc-base <none>
-- no debconf information
Reply to: