[debian-mysql] Bug#853972: Bug#853972: mariadb-10.1: upgrading from mysql-5.7 renders old data inaccessible with no option to abort

Robie Basak robie.basak at ubuntu.com
Thu Feb 2 16:36:02 UTC 2017

Hi Julian,

I'm not very keen on failing preinsts.

You seem to be making an assumption that your data will still be
readable after switching from MySQL to MariaDB. However, I don't make
that assumption if I switch from MySQL to Postgres.

One difference is that the MySQL and MariaDB packages do conflict, for
various reasons. This is fundamental as they both listen on the same
port (and pretty much speak the same protocol) by default. However, I
don't think this is enough of a reason to rely on a user assumption
which simply isn't true upstream, and that we don't advertise.

I think the right thing to do is the same as the MySQL->Postgres
scenario. The data should be able to stay put. The new daemon should
start (perhaps with a new empty database, as MariaDB is currently doing
if I understand correctly). And the user should be able to seamlessly
switch back. That the packages conflict shouldn't come in to it.

Separately, mysqldump isn't in mysql-server-core-5.7. Could it be, and
if it could, would this be conflict-free?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20170202/82a34366/attachment.sig>

More information about the pkg-mysql-maint mailing list