Hello, adding to my report:
The reason is that the mariadb.socket shipped with 10.11.18 now includes an [Install] part, which then makes dh-installsystemd act upon it and activating it.
The unit shipped in 10.11.14 did not include this and was therefor marked as "static" and inert.
To me the sensible way forward is to quickly ship a new package in Debian, reverting that change, restoring the old behavior.
And also be on the lookout for similar changes in Debian 13 and 14, since it is _not_ obvious to the admin, that "bind_address" is no longer respected when MariaDB is used via mariadb.socket.
Grüße, Sven.
