Excerpts from Nicholas Bamber's message of Mon May 21 12:47:19 -0700 2012:
> On 21/05/12 20:21, Julien Cristau wrote:
> > On Mon, May 21, 2012 at 11:34:16 -0700, Clint Byrum wrote:
> >
> >> mysql-common>> 5.5 will break 5.1 because there are new configuration
> >> options used in /etc/mysql/my.cnf that will *break* mysql 5.1, as in,
> >> it will refuse to run, libmysqlclient will throw errors, etc. This is
> >> an unfortunate, but necessary evil.
> >>
> >> We can upload a version of 5.1 that has no mysql-server, mysql-client,
> >> or mysql-testsuite packages, and also that depends on a mysql-common-5.1
> >> which breaks/replaces mysql-common<< ${binary:Version}, and conflicts
> >> with mysql-common>> ${binary:Version}, so that everything remains
> >> installable during the transition. mysql-common in 5.5 would also then
> >> need a Breaks/Replaces of that package to handle upgrades properly.
> >>
> > I'd rather see a new mysql-5.1 upload that builds *only*
> > libmysqlclient16.
<fixed top post>
> That should be trivial. We need only remove all the other binary
> stanzas, right?
>
You will also need to fold /etc/mysql/my.cnf into libmysqlclient16 as the
library needs that file for default settings, and then you need to make
it conflict with mysql-commont <= 5.5 so as to not pick up the broken
config options.
Either way, basically nothing that depends on libmysqlclient16 will be
able to be co-installed with anything that depends on libmysqlclient18.
Welcome the to the crack that is libmysqlclient. :)
I will do some tests, maybe we can get the two libs to share a common
transitional "library only" my.cnf.
But, I think really we just have to finish the transition ASAP.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
