Bug#820826: libc6-dev-amd64: Multiarch allows conflicting packages, and apt-get does not detect this
On 2018-01-11 11:19, Raphael Hertzog wrote:
> Control: forcemerge 702962 -1
> Control: severity 702962 important
>
> On Wed, 27 Apr 2016, Aurelien Jarno wrote:
>
> [ ... file conflicts between various libc6-dev-$ARCH ... ]
>
> > This has already been reported multiple time, for example in #702962.
> > Anyway apt-get simply do not support cross-architecture conflict, so
> > there is nothing that can be done on the libc side.
>
> It looks like this has been fixed in the mean time. I asked on #debian-apt
> and got this answer:
>
> 09:49 <buxy> Hum, is aurel32' assertion in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820826#10 still true? Is there no way to teach apt taht "libc6-dev-amd64:i386" and "libc6-dev-i386:amd64" are not co-installable?
> 09:50 <buxy> Not even with a conflict on a virtual package provided by both packages?
> 10:31 <juliank> buxy: cross conflicts work fine
> 10:31 <juliank> So, e.g. I can't install a package:i386 conflicting with apt:amd64
> 10:32 <juliank> So libc6-dev-amd64:i386 should Conflicts: libc6-dev-i386:amd64
> 10:32 <juliank> and vice versa
> 10:32 <juliank> Provides might be more tricky, not sure
>
> So it's probably time to revisit this.
Does it also now support cross-architecture "self"-conflicts? (see
bug#747261 for more details). With what you told me we can indeed fix a
few cases, but not the main ones. For example we need libc6-dev-x32:amd64
to conflict with libc6-dev-x32:i386.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: