Bug#870257: Add conflicts for multilib development packages
control: tag -1 - patch
On 2017-07-31 13:36, Matthias Klose wrote:
> Package: src:glibc
> Version: 2.24-12
> Tags: patch
>
> Please add conflicts for the multilib development packages. There are bug
> reports with foreign architectures that try to install both libc6-dev-i386 and
> libc6-dev-amd64 packages, and then failing because of conflicts in /usr/include.
> This patch adds the conflicts for all the known multilib pairs/triples.
> * Add conflicts for multilib development packages.
>
> diff -Nru glibc-2.24/debian/control.in/amd64 glibc-2.24/debian/control.in/amd64
> --- glibc-2.24/debian/control.in/amd64 2017-06-18 16:13:52.000000000 +0200
> +++ glibc-2.24/debian/control.in/amd64 2017-07-31 13:03:42.000000000 +0200
> @@ -16,6 +16,15 @@
> Depends: libc6-amd64 (= ${binary:Version}), libc6-dev (= ${binary:Version}), ${misc:Depends}
> Recommends: gcc-multilib
> Provides: lib64c-dev
> +Conflicts: libc6-dev-i386,
> + libc6-dev-mips32,
> + libc6-dev-mips64,
> + libc6-dev-mipsn32,
> + libc6-dev-powerpc,
> + libc6-dev-ppc64,
> + libc6-dev-sparc,
> + libc6-dev-sparc64,
> + libc6-dev-x32
> Build-Profiles: <!nobiarch>
> Description: GNU C Library: 64bit Development Libraries for AMD64
> Contains the symlinks and object files needed to compile and link programs
If libc6-dev-amd64:i386 conflicts with libc6-dev-x32:i386, how do you
plan to get a package like gcc-7-multilib, which depends on both
packages to be kept installable?
Of course libc6-dev-x32:i386 can be dropped from the conflicts list, but
it defeats the purpose of your patch as on amd64 libc6-dev-x32 and
libc6-dev-amd64 will be failing to install on amd64 because of conflicts
in /usr/include.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: