Hi, > I checked !187 and !189.
Thanks for the additional reviews on those and attention to detail! > 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? I think the current maintainer script version sufficiently addresses the regression and also results in sensible behavior when users in the future upgrade to .20. The explanations in the latest NEWS version as updated yesterday should be enough to support users. I would favor uploading the current version from https://salsa.debian.org/mariadb-team/mariadb-server/-/tree/debian/12-bookworm if that is OK with you.
