Hello, Thanks for the information on upstream issue!
Yes, the installation completes after that. But I guess that because setcap failed, it won't start with --memlock switch. I guesstimate this based just on the error message during install, which suggest on why it tried to setcap on server binary.
As a temporary workaround until upstream addresses this issue, it can be easily fixed after install by running setcap manually on mariadbd binary.
16.03.2025 9:24, Otto Kekäläinen - otto at debian.org wrote:
Hi! Thanks for reporting. This is a regression from https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/db57c0d8f20ebfe9f54f98941eabb1c774e696a3 The warning is just a warning and the installation/upgrade still completes, right? Seems upstream is aware of this issue and reworking this for next MariaDB minor releases in https://github.com/MariaDB/server/pull/3873
