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. I'm reporting this because a Kali user has been bitten by this problem (https://bugs.kali.org/view.php?id=4462) and I was wondering why there was no explicit conflicts. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
