Package: apparmor Version: 4.1.6-2 Latest MariaDB introduced a AppArmor profile as requested in #875890 (initially now only in 'complain' mode).
>From >https://ci.debian.net/data/autopkgtest/testing/amd64/a/apparmor/68800998/log.gz 96s autopkgtest [19:34:26]: test command1: bash -e debian/tests/compile-policy 96s autopkgtest [19:34:26]: test command1: [----------------------- ... 102s Warning from /etc/apparmor.d/usr.sbin.libvirtd (/etc/apparmor.d/usr.sbin.libvirtd line 149): profile libvirtd network rules not enforced 102s Warning from /etc/apparmor.d/usr.sbin.libvirtd (/etc/apparmor.d/usr.sbin.libvirtd line 149): profile qemu_bridge_helper network rules not enforced 102s Addition succeeded for "qemu_bridge_helper". 102s Addition succeeded for "libvirtd". 102s Testing usr.sbin.mariadbd 102s Cache read/write disabled: interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.) 102s File /etc/apparmor.d/usr.sbin.mariadbd not found, skipping... 102s autopkgtest [19:34:32]: test command1: -----------------------] 102s autopkgtest [19:34:32]: test command1: - - - - - - - - - - results - - - - - - - - - - 102s command1 FAIL non-zero exit status 2 Seems the test assumed there is a profile named usr.sbin.mariadbd. However, that was always empty, and compiling it kind of moot. Maybe it should just have been removed from AppArmor's autopkgtest? The new AppArmor profile that was implemented is just called 'mariadbd' based on suggestion from Georgia Garcia in https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/150 That should be OK and seems the best fix here is simply to adjust the autopkgtest in AppArmor?
