Hi, I tried to solve this problem but reached the limits of what I know about how multiarch and dependency resolution in Debian in general is supposed to work.
On Mon, Sep 10, 2012 at 12:52:13PM +0200, Johannes Schauer wrote: > Example: when crosscompiling for armel on amd64. > > linux-libc-dev is M-A: Same and Provides the virtual package > linux-kernel-headers. Indeed what linux-libc-dev actually does is: Replaces: linux-kernel-headers Provides: linux-kernel-headers Conflicts: linux-kernel-headers The question arises how I can install linux-libc-dev from different architectures at all if they all provide and conflict with linux-kernel-headers at the same time? Even though linux-libc-dev is M-A: Same, looking at those Replaces/Provides/Conflicts suggests that linux-libc-dev can not be co-installable? Apt is happy with co-installing them... Me saying that dose3 commit 47c818 is a regression in my last email comes from comparing apt-get behaviour to dose3. It might of course as well be an apt bug. Just writing those lines because they might provide more insight into the problem to people who know more about how things are actually supposed to work. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
