[debian-mysql] Bug#686803: Bug#686803: upgrade from 5.5.24+dfsg-4 to 5.5.24+dfsg-7 failed: "dependency problems - leaving unconfigured"

[Nicholas Bamber]

On 06/09/12 21:35, Wookey wrote:
> +++ Nicholas Bamber [2012-09-06 21:20 +0100]:
>> I cannot reproduce the issue but I have a theory what is required is
>> adding a breaks clause to mysql-server-core-5.5
>>
>> Breaks: mysql-server-5.5 (<< ${binary:Version})
> 
> Maybe - I've always been a bit vague aboiut the details of this work.
> 
>> As far as I undersyand it the background is that mysql-server-core-5.5
>> was split out from mysql-server-5.5 because a certain dependent
>> application wanted to use the binaries but use its own management
>> scripts. So mysql-server-5.5 has a clause
>>
>> Depends: mysql-server-core-5.5 (= ${binary:Version})
>>
>> So maybe everything is okay when mysql-server-5.5 gets looked at before
>> mysql-server-core-5.5 but not vice versa.
> 
> Yes a naive view makes one think that that depends should be all
> that's required. But clearly it isn't as dpkg keeps trying to
> consider installing mysql-server-5.5 rather than forgetting about that
> any upgrading it to latest, which would be fine. I wonder if all those
> Replaces: have somehting to do with it. FInd a dependency expert :-)
> 
>> In your case I would try:
>>
>> apt-get install mysql-server-5.5
> 
> Nope - doesn't do the trick (sam eimpasses as before. Even apt-get
> install mysql-server-5.5=5.5.24+dfsg-7 doesn't get it to do the right
> thing, but uninstalling mysql-server (and mysql-server-5.5 and
> mysql-server-core-5.5) and re-installing sorts it out. 
> 
> Wookey

I am coming to the conclusion that the safest course of action is to
replace the '=${binary:Version} dependency with >=${source:Version}. The
latter model is used elsewhere in the control file and I cannot really
see why the strict dependency is required. (Though no doubt in the
future there will be upstream incompatibilities).