[debian-mysql] Request for collaborator: MariaDB 10.11.19 to Debian 12 "Bookworm" (LTS)

Sylvain Beucler beuc at beuc.net
Mon Nov 2 13:53:18 GMT 2026


Hi,

On 26/10/2026 11:09, Otto Kekäläinen wrote:
> Are you available to collaborate on a bugfix upload for Bookworm?
> 
> I am planning to merge
> https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/187
> and upload to Bookworm if you think it is OK.

(As answered privately I was not available until today.)

I checked !187 and !189.

One thing: I thought the last upload (.19) would revert the systemd 
socket activation from .18, hence the resulting network over-exposure 
(and now, the unexpected restart-on-connection during maintenance 
downtimes).

I was mistaken: .19 only prevented this from happening in new installs 
(or .17->.19 upgrades), but didn't fix impacted .18 systems. Given the 
serious issues above, in addition to the NEWS warning, is there a way to 
revert this socket activation automatically?

If not, should we unconditionally disable socket activation (which I 
believe is rarely used for MariaDB in the first place?), and have the 
NEWS explain how it can be re-activated if really needed?

Cheers!
Sylvain Beucler
Debian LTS Team



More information about the pkg-mysql-maint mailing list