[Multiarch-devel] cross-architecture conflicts or equivalent for libc packages

[Aurelien Jarno]

On Mon, May 19, 2014 at 01:16:36PM +0200, Jakub Wilk wrote:
> * Aurelien Jarno <aurelien at aurel32.net>, 2014-05-19, 12:25:
> >We currently have a problem with the libc{0.1,0.3,6,6.1} packages,
> >which are marked as Multiarch:same, but are in practice not
> >co-installable due to the ELF interpreter path being the same on
> >various architectures. For example libc6:i386 and libc6:sparc are
> >not co-installable, causing dpkg to exit complaining onifile
> >overwrite.
> 
> Sounds like a job for Provides+Conflicts+Replaces.
> 
> >Here is the list of the different ELF interpreters for the various
> >architectures we have in Debian or floating around:
> >
> >i386            /lib/ld-linux.so.2
> 
> Provides: lib-ld-linux-so-2
> Conflicts: lib-ld-linux-so-2
> Replaces: lib-ld-linux-so-2

So following your way, it would be exactly the same for libc6:sparc.

libc6-i386 also provides /lib/ld-linux.so.2. It should be co-installable
with libc6:i386, but libc6:sparc should not be co-installable with
libc6:i386 or libc6-i386.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien at aurel32.net                 http://www.aurel32.net