Home My Page Projects Dose: library and tools
Summary Activity Tracker Lists SCM Files

[#18307] undetected conflict between m-a:same packages that provide a common package

2014-11-20 16:23
Submitted by:
Johannes Schauer (josch)
Assigned to:
Nobody (None)
undetected conflict between m-a:same packages that provide a common package

Detailed description
In Debian, the Provides field, provides the package for all architectures. This means that the following package cannot be co-installed (actual example):

Package: libbabl-dev
Multi-Arch: same
Source: babl
Version: 0.1.10-2
Replaces: libbabl-0.0-0-dev
Provides: libbabl-0.0-0-dev
Breaks: libbabl-0.0-0-dev

But dose3 does not see this problem and co-installs them anyways.

Here is the dpkg bugreport (which does it correctly): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770301

And here the relevant one for apt (which also suffers from this problem): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770345
Message  ↓
Date: 2014-11-20 17:21
Sender: Johannes Schauer


I agree with all you've said. That's why I posted both bug numbers, so that we have a pointer to the discussion that will probably happen in the apt bug. I filed this bug to keep track of the issue and not forget about it in case people agree that dpkg is right and apt is no.


Date: 2014-11-20 16:44
Sender: Roberto Di Cosmo

Hi Josch,
thanks for reporting this, but before making correction, it's better to be sure of what is the right behaviour here.

With Pietro, we spent an awful amount of time on the multi-arch specification (that admittedly has some ambiguous statements in it) to make sure dose3 implements it correctly.

Now, having apt and dose3 sayng the same thing, while dpkg says something else is not enough to conclude that dpkg is right, and the comments I see in the two bug reports you mention (thanks for providing them!) are unconvincing to me.

In particular, I remember we did special effort with Pietro to make sure that implicit self-conflict via provides/replaces/break are not produced for M-A: same, according to our understanding of MA spec.

One needs to go over the (natural language) multi-arch spec again to check what is really the intended behaviour here.

I also would not fix this unless apt maintainers also acknowledge and fix it.

No Changes Have Been Made to This Item