On Tue, Sep 01, 2015 at 01:38:26PM -0000, 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 mechanism by which it could be done.
I don't think it's acceptable for a crossgrade from MySQL to MariaDB to
take place in a way that cannot be reversed by MariaDB effectively
clobbering the MySQL packaging's data files, when otherwise removing and
re-installing the MySQL packaging only with no MariaDB involved would
work.
It is certainly non-trivial to fix in a way that works for everybody,
and we will need to talk more about how we can resolve this, but that
doesn't stop the issue from existing.
On Tue, Sep 01, 2015 at 01:38:26PM -0000, 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 mechanism by which it could be done.
I don't think it's acceptable for a crossgrade from MySQL to MariaDB to
take place in a way that cannot be reversed by MariaDB effectively
clobbering the MySQL packaging's data files, when otherwise removing and
re-installing the MySQL packaging only with no MariaDB involved would
work.
It is certainly non-trivial to fix in a way that works for everybody,
and we will need to talk more about how we can resolve this, but that
doesn't stop the issue from existing.