[debian-mysql] Bug#887007: my.cnf handling collides with MySQL

[Robie Basak]

Package: mariadb-client-10.1
Version: 1:10.1.29-6
User: ubuntu-devel at lists.ubuntu.com
Usertags: origin-ubuntu bionic

Steps to reproduce:

apt install mariadb-client-10.1
apt install mysql-server-5.7

The second command will cause mariadb-client-10.1 because of a conflict
with mysql-client-5.7, which is depended on by mysql-server-5.7 and is
expected. However, then we have:

# update-alternatives --display my.cnf
my.cnf - auto mode
  link best version is /etc/mysql/mariadb.cnf
  link currently points to /etc/mysql/mariadb.cnf
  link my.cnf is /etc/mysql/my.cnf
/etc/mysql/mariadb.cnf - priority 200
/etc/mysql/my.cnf.fallback - priority 100
/etc/mysql/mysql.cnf - priority 200

This is incorrect. Our /etc/mysql/my.cnf management system expects that
only one variant package will claim the file at one time. In this case
we have MariaDB claiming /etc/mysql/my.cnf -> /etc/mysql/mariadb.cnf
even though MySQL's mysql-server-5.7 is installed and supposedly active.

This happens because the code to claim /etc/mysql/my.cnf is in
mariadb-common, which is depended on my mariadb-client-10.1. I had
intended the claim to be made from mariadb-server-10.1 (and other
variants' counterparts) only.
-------------- 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/20180112/39e2b79b/attachment.sig>