That should be trivial. We need only remove all the other binary
stanzas, right?
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.
Cheers,
Julien
_______________________________________________
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
