[debian-mysql] Bug#842011: Bug#842011: Bug#842011: default-mysql-client forces removal of mysql-server* and mysql-client*

Craig Sanders cas at taz.net.au
Wed Oct 26 04:31:58 UTC 2016

On Wed, Oct 26, 2016 at 04:52:38AM +0200, Clint Byrum wrote:
> The point of the stable release is security updates with minimal impact.

well, no.  that's ONE of its points, not THE point.

Another point is to refrain from breaking existing systems - that's at
least as important as security updates, even if for no other reason than
that you should be able to trust your distro to not arbitrarily break
your system on upgrade either due to carelessness or for some misguided
and just-plain-wrong claim that breaking your system is for your own good.

> > [ re: dump to text and restore ]
> You can definitely do that as a user. But automating it just isn't
> something anybody has had time to do and feel good about it, given
> that we're talking about peoples' data.

yet allowing mariadb to use the same data directory as mysql (even
though it's not completely RW compatible with mysql) is somehow

automated export and import is safe. blindly using incompatible binary
data files is not.

the postgresql packages manage to successfully - flawlessly - upgrade
even through binary-incompatible major releases and have done so for
many years. any mysql -> mariadb transition should be handled at least
as well as that.  it's not impossible, it's not even "too hard".


craig sanders <cas at taz.net.au>

More information about the pkg-mysql-maint mailing list