My conclusion so far is this: As requested in the MariaDB MIR security review (LP#2122095) the systemd service file had additional hardening added in patch https://salsa.debian.org/mariadb-team/mariadb- server/-/blob/debian/latest/debian/patches/systemd-hardening-safe- defaults.patch.
The Ubuntu autopkgtest environment seems to be have some restrictions that systemd can't enable some of these hardening features, resulting in this error message "Could not execute systemctl: at /usr/bin/deb- systemd-invoke line 148." as described in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1076530. Perhaps it isn't even running the real systemd but the systemctl shim? It probably does not support any security features? To solve this we need someone with access to the autopkgtest environment to debug what limitations systemd there has. ** Bug watch added: Debian Bug tracker #1076530 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076530 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2143708 Title: mariadb 1:11.8.6-2 autopkgtest failures with multiple packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2143708/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
