On Thu, Sep 22, 2022 at 05:10:05PM +0200, nobody wrote: > * What outcome did you expect instead? > > installing a client library should not require anything on the server side > and should not modify server configuration of mariadb or other mysql flavors > (imho ;p)
Both MySQL/MariaDB client libraries and MySQL/MariaDB daemons expect and use /etc/mysql/my.cnf, and many common packages supplied by Debian link to a MySQL/MariaDB library. So Debian ends up needing to ship a working /etc/mysql/my.cnf essentially by default. It doesn't matter which side of the fork is in use - it's necessary either way. Maybe upstream could separate the two out, but they don't. MySQL and MariaDB Debian maintainers worked out a way to make it work regardless of the side of the fork in use using the update-alternatives mechanism. I think there might still be some implementation bugs in how they do that exactly, but I don't think they're relevant to what you're reporting here. If third parties are shipping apt packages that override some of this, they need to integrate with distribution packages, not the other way round. Issues with third party apt repositories aren't normally considered bugs in Debian. This sounds like an issue with a third party repository and a bug in their packaging, and not a bug in Debian. However I'm not entirely sure as you haven't provided a detailed analysis of why they've been unable to integrate. I suggest that this bug needs to be either moreinfo or wontfix.
signature.asc
Description: PGP signature
