This bug was fixed in the package apparmor - 3.0.4-1ubuntu1
---------------
apparmor (3.0.4-1ubuntu1) jammy; urgency=medium
* Merge from Debian unstable; remaining changes:
- Drop the following patches that have been included in the upstream
release or which Debian has also included:
- d/p/ubuntu/adjust-for-ibus-1.5.22.patch
- d/p/ubuntu/0011-add-mctp-network-protocol.patch
- Refresh
d/p/regression-tests-fix-aa_policy_cache-when-using-syst.patch to the
official version from upstream
- d/p/u/samba-systemd-interaction.patch: allow smbd to interact with
systemd
- d/p/u/libnss-systemd.patch: allow accessing the libnss-systemd
VarLink sockets and DBus APIs
- Disable lto builds
- Fix autotest test-aa-notify.py
- d/p/ubuntu/fix-test-aa-notify.patch
- Drop outdated lintian-overrides
apparmor (3.0.4-1) unstable; urgency=medium
* New upstream release
* apparmor-profiles: install new samba-bgqd profile
* Drop backported patches that are now obsolete
* debian/allow-access-to-ibus-socket.patch: drop support for pre-Bullseye
ibus path
* Declare compliance with Policy 4.6.0.1
* Drop XS- prefix for adopted Python-Version control field
* Add new symbols
apparmor (3.0.3-6) unstable; urgency=medium
* debian/rules: let "set -e" take effect (Closes: #998843)
* Add support for Python 3.10 (Closes: #998686):
- upstream-ab4cfb5e-replace-distutils-with-setuptools.patch: new patch,
edited to drop changes to upstream .gitignore.
- Add build-dependency on python3-setuptools
apparmor (3.0.3-5) unstable; urgency=medium
[ Debian Janitor ]
* Remove constraints unnecessary since stretch.
[ Helmut Grohne ]
* Make the package cross-buildable (Closes: #984582):
- Multiarchify python Build-Depends
- Let dh_auto_build pass cross tools to make
- Annotate perl build-dependency with !nocheck
[ intrigeri ]
* Remove obsolete libapparmor-perl on upgrade
apparmor (3.0.3-4) unstable; urgency=medium
* Merge apparmor-easyprof into apparmor-utils (Closes: #972880)
* Make apparmor-utils and python3-apparmor arch:all (Closes: #972881)
apparmor (3.0.3-3) unstable; urgency=medium
* Adjust gbp.conf and Vcs-* control fields for 3.0.x now being in sid.
* Stop building the libapparmor-perl binary package (Closes: #993565)
* Update Lintian overrides
* Add B-D on dh-sequence-python3, to workaround #996089 in Lintian
* B-D: python3-all → python3-all:any, to appease Lintian
apparmor (3.0.3-2) unstable; urgency=medium
* Upload to unstable
apparmor (3.0.3-1) experimental; urgency=medium
* New upstream release
* Drop debian/Revert-libapparmor-fixing-setup.py-call-when-crosscompili.patch:
obsolete
* Refresh patches
* Merge changes from sid, up to 2.13.6-10
* upstream-6cfc6eee-python-3.10.patch: new patch,
for compatibility with Python 3.10
-- Alex Murray <alex.mur...@canonical.com> Tue, 22 Feb 2022 10:13:44
+1030
** Changed in: apparmor (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1961196
Title:
apparmor autotest failure on jammy with linux 5.15
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Jammy:
Fix Released
Bug description:
[Impact]
test-aa-notify is also checking if the output of `aa-notify --help`
matches a specific text. However it looks like this output has changed
in jammy so the autopkgtest is reporting errors like this:
05:17:31 ERROR| [stderr] === test-aa-notify.py ===
05:17:31 ERROR| [stderr] .ssF.
05:17:31 ERROR| [stderr]
======================================================================
05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
05:17:31 ERROR| [stderr] Test output of help text
05:17:31 ERROR| [stderr]
----------------------------------------------------------------------
05:17:31 ERROR| [stderr] Traceback (most recent call last):
05:17:31 ERROR| [stderr] File
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
line 178, in test_help_contents
05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output,
result + output)
05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n
-h, --help sh[746 chars]de\n' != 'usag[189 chars]ptions:\n -h,
--help show this hel[735 chars]de\n'
05:17:31 ERROR| [stderr] usage: aa-notify [-h] [-p] [--display DISPLAY] [-f
FILE] [-l] [-s NUM] [-v]
05:17:31 ERROR| [stderr] [-u USER] [-w NUM] [--debug]
05:17:31 ERROR| [stderr]
05:17:31 ERROR| [stderr] Display AppArmor notifications or messages for
DENIED entries.
05:17:31 ERROR| [stderr]
05:17:31 ERROR| [stderr] - optional arguments:
05:17:31 ERROR| [stderr] + options:
05:17:31 ERROR| [stderr] -h, --help show this help message and
exit
05:17:31 ERROR| [stderr] -p, --poll poll AppArmor logs and
display notifications
05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY
environment variable (might be needed if
05:17:31 ERROR| [stderr] sudo resets $DISPLAY)
05:17:31 ERROR| [stderr] -f FILE, --file FILE search FILE for AppArmor
messages
05:17:31 ERROR| [stderr] -l, --since-last display stats since last
login
05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
05:17:31 ERROR| [stderr] show stats for last NUM
days (can be used alone or with
05:17:31 ERROR| [stderr] -p)
05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
05:17:31 ERROR| [stderr] -u USER, --user USER user to drop privileges to
when not using sudo
05:17:31 ERROR| [stderr] -w NUM, --wait NUM wait NUM seconds before
displaying notifications (with
05:17:31 ERROR| [stderr] -p)
05:17:31 ERROR| [stderr] --debug debug mode
05:17:31 ERROR| [stderr] : Got output "usage: aa-notify [-h] [-p] [--display
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
05:17:31 ERROR| [stderr] [-u USER] [-w NUM] [--debug]
[Test case]
Simply run test-aa-notify.py from the autopkgtests.
[Fix]
Update the expected output returned by `aa-notify --help` in test-aa-
notify.py.
[Regression potential]
This is just an autopkgtest, we may see regressions if the test is
used with older version of apparmor-notify. With newer versions
there's no risk of regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
