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

[Jakub Wilk]

* 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

>hppa            /lib/ld.so.1
>m68k            /lib/ld.so.1
>mips            /lib/ld.so.1
>s390            /lib/ld.so.1

Provides: lib-ld-so-1
Conflicts: lib-ld-so-1
Replaces: lib-ld-so-1

>amd64           /lib64/ld-linux-x86-64.so.2

Provides: lib64-ld-linux-x86-64-so-2
Conflicts: lib64-ld-linux-x86-64-so-2
Replaces: lib64-ld-linux-x86-64-so-2

... and so on.

-- 
Jakub Wilk