Your message dated Wed, 25 Feb 2026 10:18:26 +0000
with message-id <[email protected]>
and subject line Bug#1128456: fixed in apparmor 4.1.6-3
has caused the Debian Bug report #1128456,
regarding AppArmor autopkgtest 'command1' fails with MariaDB 1:11.8.6-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1128456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128456
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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?

--- End Message ---
--- Begin Message ---
Source: apparmor
Source-Version: 4.1.6-3
Done: intrigeri <[email protected]>

We believe that the bug you reported is fixed in the latest version of
apparmor, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
intrigeri <[email protected]> (supplier of updated apparmor package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 25 Feb 2026 10:01:19 +0000
Source: apparmor
Architecture: source
Version: 4.1.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian AppArmor Team <[email protected]>
Changed-By: intrigeri <[email protected]>
Closes: 1128456
Changes:
 apparmor (4.1.6-3) unstable; urgency=medium
 .
   * README.source: simplify thanks to git debpush
   * dh_apparmor: add introspectable comment to document
     we don't react to any configuration file
   * autopkgtests: adjust to renamed MariaDB profile (Closes: #1128456)
Checksums-Sha1:
 eab50db58000f3d0588c01977dd82d4f2e91d5b7 3709 apparmor_4.1.6-3.dsc
 33752feb23e909cedfacf3306c0e19d4fa018022 106157 apparmor_4.1.6-3.diff.gz
 25f9faec0f7b34ef9e004afc74e8b4a23a2f1d71 8743724 apparmor_4.1.6-3.git.tar.xz
 9c24858952d7ddf48c1780676fa9ab347a127eb8 17298 
apparmor_4.1.6-3_source.buildinfo
Checksums-Sha256:
 4af297892290620ba2fe8865dbe4cb83b027b94410dfabbb9d30f3643e98df8f 3709 
apparmor_4.1.6-3.dsc
 ad39e1ccebc367521f3437b94c48b1203fce05b9029731966c149500fe198b3b 106157 
apparmor_4.1.6-3.diff.gz
 cda94d054e4f677daa73bb8fc13d5d5f5584fa6f9845a45ddd1dc3c51bebc348 8743724 
apparmor_4.1.6-3.git.tar.xz
 3f503c048517cbb8d0ec19de89ffefa7146df214597c137c4baea427dd46ff29 17298 
apparmor_4.1.6-3_source.buildinfo
Files:
 a7c7a2689b12ef8cd472c5f3397b1955 3709 admin optional apparmor_4.1.6-3.dsc
 8bad4393d39fab205e46f5ca12e8ca85 106157 admin optional apparmor_4.1.6-3.diff.gz
 cb158a67378885d7dc0e2a64f88a34ee 8743724 admin None apparmor_4.1.6-3.git.tar.xz
 15ac0717d35021a3161027f4d8be66ac 17298 admin optional 
apparmor_4.1.6-3_source.buildinfo
Git-Tag-Info: tag=6489fbccde4896f25053f090645799055f6db9ee 
fp=61b4345c66efc790fed859c69f8fa72f6954c3a3
Git-Tag-Tagger: intrigeri <[email protected]>

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmmeyP0ACgkQYG0ITkaD
wHndiRAA3xsak1lw/Yu12V0o8AzlkSmluFvytyHrLUGiSyQsKox+wQag0h6/7dt4
iMQH1yUghEXvyU/DIwlATCvbVDlZPWmXIh4vqt5OSyzTGWB9QLVj00yg/Y9XSzvq
a2weDjB7rZcFahH7NHpNoJlk7KbRsGUWvURSeyuOTzLk19TZpTjQ9g5IpyXJUWwc
Q3FitHsfVNGh3XF/lOtK3LMn2IfeN00y+k35/jWI5+93Po2Nstv296k5KHMR+gA3
tICmA3B3Xzk3ylEInZVNUiw+yE5J9SML/l3bzNj9VVi8bveyQhuf4NVCatPaAnEj
mTpj8kbqbK83irffzkl5dDqYuuZBM8zdsqUK/uWpYd0K3CbkKU2Cs/KcihmkwBIV
d/zCI5F0fZ/onbiiVY70XEU3GvzUTeBOU2/AtJPVA/hfbBmrK++BZrRNu8YN6wRe
da4nSOVhLX1xdCbUr4NnfvpsmNVrA6Z9klQzfLqkGrxkRdi0id7RCMGEKg+8+z8G
vHtvqCS7HCfrI0lLXa7LEMcxu19XiGmNwhyLL3CmzLKXq3wPu3Tx9KVYaVYJhA57
DfdU5Py8GtqcwTH/d7993YJMvWkEchNWmZKHk8w8mjIpKk94qLFQ69NsCRtI2j7M
lvWl0pANqa7f/MyESAOebxIpXIe8sesOCVrLf03c6IqEGlLkMuY=
=i4iZ
-----END PGP SIGNATURE-----

Attachment: pgpQFmJmZaVA4.pgp
Description: PGP signature


--- End Message ---

Reply via email to