[debian-mysql] Bug#1020518: Bug#1020518: Bug#1020518: libmariadb3 is a client library that include marriadb-common that will mess with /etc/mysql/my.cnf

[Robie Basak]

On Thu, Sep 22, 2022 at 11:32:05PM +0200, Ghislain Adnet wrote:
> in fact /etc/mysql/mariadb.cnf does not exist as there is a mysql server and not a mariadb one.

mariadb-common ships /etc/mysql/mariadb.cnf.

> I have a perconna mysql server running and i want to install mytop that require a perl lib that require libmariad3b, that then, want to replace /etc/mysql/my.cnf with a link to /etc/mysql/mariadb.cnf,

Not necessarily. It integrates with update-alternatives. It will link
from /etc/mysql/my.cnf to /etc/mysql/mariadb.cnf unless overridden by
another package or by the user.

> but /etc/mysql/mariadb.cnf does not exist while /etc/mysql/my.cnf exist from the percona packages.

You're entitled to remove /etc/mysql/mariadb.cnf and I think in that
case the packaging should respect that and not break. So there might be
something that could be improved here.

However, I did some investigation, and found that if you set
update-alternatives correctly to use a different my.cnf (in my testing I
used my.cnf.fallback as it was already there), then the packaging does
not break. So, as far as I can tell, the problem here lies with your
third party packaging not correctly integrating with distribution
packaging by using update-alternatives correctly to supply my.cnf. I
think you need to report this bug to them, and it isn't an issue in
Debian.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20220926/0cca7829/attachment.sig>