Hi Josch, On Tue, Jul 04, 2017 at 09:45:06AM +0200, Johannes Schauer wrote:
> Or even more directly by: > > cat << END | dose-deb-coinstall --explain -f --deb-native-arch=amd64 > Package: perl-base > Version: 5.24.1-5 > Architecture: amd64 > Provides: libscalar-list-utils-perl (= 1:1.42.02) > > Package: libscalar-list-utils-perl > Version: 1:1.48-1 > Architecture: amd64 > END > > > The cudf representation of this problem (shortened to the relevant parts) is: > > package: perl-base%3aamd64 > version: 2 > conflicts: perl-base%3aamd64 , perl-base > provides: perl-base , --virtual-libscalar-list-utils-perl%3aamd64 = 3 , > libscalar-list-utils-perl%3aamd64 = 3 > > package: libscalar-list-utils-perl%3aamd64 > version: 4 > conflicts: libscalar-list-utils-perl%3aamd64 , libscalar-list-utils-perl > provides: libscalar-list-utils-perl > > > I suspect the problem to be the self-conflict of > libscalar-list-utils-perl%3aamd64 with itself. Because perl-base%3aamd64 > provides libscalar-list-utils-perl%3aamd64 = 3, > libscalar-list-utils-perl%3aamd64 conflicts with it. thanks for having figured that out. I tend to believe that dose is right in this case. Since it is not possible to install at the same time two different versions of the same real package, the same should IMHO hold when one is real and the other virtual. Why should this be possible? -Ralf.
