[debian-mysql] 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 01:10:49 UTC 2016

On Tue, Oct 25, 2016 at 01:09:23PM +0100, Robie Basak wrote:
> On Tue, Oct 25, 2016 at 10:00:32PM +1100, Craig Sanders wrote:
> > it still seems very surprising to me that a package called
> > default-MYSQL-client would force the removal of mysql-client* and
> > mysql-server*
> I agree this is confusing. Unfortunately we don't have a common
> name that describes both MariaDB and MySQL. "MySQL-like"
> is perhaps the best we can do. The package name would be
> default-<something>-client. What do you suggest that <something>
> should be?

i would suggest that solving that problem is a job for the mysql team or at
least for someone who knows and cares more about mysql/mariadb, not a stick to
use for not-very-subtly telling random individual bug-reporters to shut up and
go away.

> > IMO іf it can't be sorted out with alternatives, then it should be a
> > completely separate package. and other packages that need a mysql-like db
> > should depend on mysql or mariadb or either with 'mysql | mariadb'.
> It is a completely separate package that conflicts with the MySQL packages
> as appropriate.

however, it uses that same data directory even though it's not 100% RW
compatible with the data files.

IMO, that's a serious bug.

> Packages that need a mysql-like db should depend on "default-mysql-server
> | virtual-mysql-server". In other words, this already works from the
> MySQL/MariaDB packaging end.

yes.  btw, this has been fixed with mythtv-common now.  a new package
has been built already after my report on the dmo-discuss list.

> I agree with you, but the release team have made their decision against our
> wishes. There's no point arguing with us. We know.

since when does the release team tell maintainers what they're allowed
to package?  or what solutions they're allowed to come up with for
easily-forseeable problems?

> > if this is the plan then there really needs to be a foolproof, automated,
> > thorougly tested migration script. and even then it should still be easy
> > to back out and revert to mysql.
> This does not exist, and currently nobody has the time to work on this.  I
> believe MySQL->MariaDB works right now, but the reverse direction certainly
> doesn't. Users should take backups before upgrading.

the problem is binary db-file compatibility, so the obvious method would be to
dump to text from mysql, possibly do some minor fixups to the text dump with
sed or pœrl if required, restore into mariadb.

and the reverse for converting from mariadb to mysql.


craig sanders <cas at taz.net.au>

More information about the pkg-mysql-maint mailing list