On 18.07.26 11:56, Otto Kekäläinen wrote:
An itemized list of all changes in this release is visible at
https://salsa.debian.org/mariadb-team/mariadb-server/-/commits/debian/12-bookworm
This is probably a result of upstream commit
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/f1aaa7518461c346c06d4ed0701b42552129cfc5
The commit for the change in behavior is this one here:
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/9fa3f51f59f5b7a6d84c68a45e6a6579f55847b3
It adds the [Install] section to the socket unit, which then causes it
to be activated by debhelper, if I understand the mechanism correctly.
Reverting that commit is probably the correct way forward here.
I have no idea how to detect and revert the accidental activation in
systems that have installed the problematic mariadb-server package, as
there might be admins that do indeed have activated it manually before.
Apart from that, what I continue to see as a major problem here is the
lack of documentation about the fact that "bind-address" in your
mariadbd configuration will be silently ignored it you use the socket
activation.
This change is something that IMO needs a NEWS entry and big bold
letters plastered around that configuration item in the 50-server.cnf to
alert users to that fact.
And suddenly activating that feature also obviously needs to be avoided
to released version of Debian.
Grüße,
Sven.
