The title is still misleading. The problem can be fixed by changing the
mysql package code. The part that the mariadb package does is not
anything new, it is exactly the same code as in the mysql packages and
originates from there.
** Summary changed:
- MariaDB writes to /var/lib/mysql after
** Changed in: mysql-5.6 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1490071
Title:
MariaDB writes to /var/lib/mysql after
** Tags added: mysql-packaging-policy
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1490071
Title:
MariaDB writes to /var/lib/mysql after crossgrade, preventing users
from
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.6 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
"I expect a user to be able to switch from MySQL to MariaDB and back
again."
It works for MySQL 5.5 and MariaDB 5.5, the latter promising to be
binary compatible wiith 5.5 The Debian packaging flag system in MySQL
packages is compatible with this. The preinstall flag check will allow
installation
> From MySQL x.x to 5.5 to 5.6 users / database admins have been
responsible for backing up their data and upgrading the database without
having the option to go back.
I expect every release to ship with only one version of (Oracle) MySQL,
and reverting an upgrade across two releases is certainly
On Tue, Sep 01, 2015 at 01:38:26PM -, Otto Kekäläinen wrote:
> The bug is about the user experience: how users are notified what
> happens and how dpkg is aborted into a broken state.
I disagree. I'm treating this bug as tracking the fact that it cannot be
done, whereas I have proposed a
