[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
This bug was fixed in the package apparmor - 4.0.1really4.0.1-0ubuntu0.24.04.6 --- apparmor (4.0.1really4.0.1-0ubuntu0.24.04.6) noble; urgency=medium * This is an SRU, tracked in LP: #2143863 * Add patch to remove the busybox and nautilus profiles (LP: #2142792): - d/p/u/delete-the-busybox-and-nautilus-profiles.patch * d/apparmor.install, d/apparmor.maintscript: account for removal of the busybox and nautilus profiles * Add patches to fix socketpair regression test (LP: #2124206): - d/p/u/-0002-tests-regression-fix-regression-test-for-upstream.patch - d/p/u/-0001-tests-regressions-fix-unix_socket_pathname.sh-for.patch - d/p/u/-tests-regression-increase-unix-socket-test-timeout.patch - d/p/u/0001-tests-regression-Update-socketpair-test-for-upstream.patch - d/p/u/0002-tests-regression-update-socketpair-tests-to-detect-d.patch - d/p/u/0003-tests-regression-update-tests-requires-for-v9-af_unix.patch - d/p/u/0004-tests-regression-Improve-output-of-require_any_of_k.patch - d/p/u/0005-tests-regression-update-network-requirements-for-v9.patch - d/p/u/0006-regression-tests-update-logic-to-support-v9-af_unix-.patch - d/p/u/0007-tests-regressions-Fix-socket-pair-for-v7-semantics.patch * Add patches to fix libapparmor features parsing (LP: #2105986): - d/p/u/libapparmor-feature-match-prefixes.patch - d/p/u/libapparmor-bump-patch-version-for-features-prefix.patch - d/p/u/libapparmor-add-test-for-libapparmor-features-prefix.patch * Add patch to fix parser handling of norelatime mount flag (LP: #2110688): - d/p/u/parser-fix-handling-of-norelatime-mount-rule-flag.patch * Add patch to fix incorrect man page information (LP: #2110630) - d/p/u/fix-incorrect-mount-flag-apparmor.d-docs.patch * Add patch to add regression tests for the above two patches: - d/p/u/regression-verify-documented-mount-flag-behavior.patch -- Ryan Lee Fri, 20 Feb 2026 15:51:51 -0800 ** Changed in: apparmor (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
$ apt-cache policy apparmor apparmor: Installed: 4.0.1really4.0.1-0ubuntu0.24.04.6 Candidate: 4.0.1really4.0.1-0ubuntu0.24.04.6 Version table: *** 4.0.1really4.0.1-0ubuntu0.24.04.6 100 100 http://archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.0.1really4.0.1-0ubuntu0.24.04.5 500 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages 4.0.0-beta3-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages The apparmor.d man page now lists the flags correctly. QRT test results: $ sudo ./test-apparmor.py -v Running test: './test-apparmor.py' distro: 'Ubuntu 24.04' kernel: '6.17.0-19.19~24.04.2 (Ubuntu 6.17.0-19.19~24.04.2-generic 6.17.13)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ryan-lee') Skipping private tests WARN: kernel rate limiting in effect Disabling ratelimiting until the next reboot. To renable, run: # sysctl -w kernel.printk_ratelimit=5 test_apport_hooks (__main__.ApparmorApport.test_apport_hooks) Test required apport hooks ... ok test_perl (__main__.ApparmorBindings.test_perl) Test perl binding ... skipped 'libapparmor-perl does not exist in this release' test_python (__main__.ApparmorBindings.test_python) Test python binding ... skipped 'python-libapparmor does not exist in this release' test_python3 (__main__.ApparmorBindings.test_python3) Test python3 binding ... ok test_envfilter_compiled (__main__.ApparmorEnvFilter.test_envfilter_compiled) Test compiled libraries environment filtering (mmap) ... ok test_envfilter_perl (__main__.ApparmorEnvFilter.test_envfilter_perl) Test perl environment filtering (PERL5LIB) ... ok test_envfilter_python (__main__.ApparmorEnvFilter.test_envfilter_python) Test python environment filtering (PYTHONPATH) ... skipped "'/usr/bin/python2' not available" test_envfilter_python3 (__main__.ApparmorEnvFilter.test_envfilter_python3) Test python3 environment filtering (PYTHONPATH) ... ok test_domain (__main__.ApparmorNetwork.test_domain) Test network domain ... domain:inet domain:inet6 domain:ax25 (skipped: Kernel module ax25 is not available) domain:x25 (skipped: Kernel module x25 is not available) domain:ipx (skipped: Kernel module ipx is not available) domain:appletalk (skipped: Kernel module appletalk is not available) domain:netrom (skipped: Kernel module netrom is not available) domain:atmpvc (skipped: Kernel module atm is not available) domain:atmsvc (skipped: Kernel module atm is not available) domain:rose (skipped: Kernel module rose is not available) domain:packet (skipped: Kernel module af_packet is not available) domain:irda (skipped: Kernel module irda is not available) domain:pppox (skipped: Kernel module pppoe is not available) domain:bluetooth (skipped: Kernel module bluetooth is not available) ok test_protocol (__main__.ApparmorNetwork.test_protocol) Test network protocol ... proto:icmp proto:tcp proto:udp ok test_type (__main__.ApparmorNetwork.test_type) Test network type ... type:dgram type:stream type:raw type:packet type:seqpacket (skipped: Kernel module tipc is not available) type:rdm (skipped: Kernel module tipc is not available) ok test_pam_default_user_group (__main__.ApparmorPAM.test_pam_default_user_group) Test pam (order=default,user,group) ... adm_group can access default_user's file adm_group cannot access adm_group's file adm_group cannot access confined_user's file adm_group cannot access confined_group's file adm_group cannot access unconfined_user's file adm_group cannot access unconfined_group's file confined_group can access default_user's file confined_group cannot access adm_group's file confined_group cannot access confined_user's file confined_group cannot access confined_group's file confined_group cannot access unconfined_user's file confined_group cannot access unconfined_group's file confined_user can access default_user's file confined_user cannot access adm_group's file confined_user cannot access confined_user's file confined_user cannot access confined_group's file confined_user cannot access unconfined_user's file confined_user cannot access unconfined_group's file default_user can access default_user's file default_user cannot access adm_group's file default_user cannot access confined_user's file default_user cannot access confined_group's file default_user cannot access unconfined_user's file default_user cannot access unconfined_group's file unconfined_group can access default_user's file unconfined_group cannot access adm_group's file unconfined_group cannot access confined_user's file unconfined_group cannot access confined_group's file unconfined_group cannot access unconfined_user's file unconfined_group cannot access unconfined_group's file unconfined_user can access default_user's file unconfined_user cannot access adm_group's file unconfined_user cannot access conf
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
Hello Ryan, or anyone else affected, Accepted apparmor into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/4.0.1really4.0.1-0ubuntu0.24.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apparmor (Ubuntu Noble) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
** Merge proposal linked: https://code.launchpad.net/~rlee287/ubuntu/+source/apparmor/+git/apparmor/+merge/501716 ** Merge proposal linked: https://code.launchpad.net/~rlee287/ubuntu/+source/apparmor/+git/apparmor/+merge/501718 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
** Also affects: apparmor (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
This bug was fixed in the package apparmor - 4.1.0~beta5-0ubuntu14.1 --- apparmor (4.1.0~beta5-0ubuntu14.1) plucky; urgency=medium * This is an SRU from Questing to Plucky, tracked in LP: #2110236 * Add patch to allow unprivileged_userns access to root dir (LP: #2110616): - d/p/u/unprivileged_userns_rootdir.patch * Add patch to fix lsblk accesses on IBM System Z systems (LP: #2107402) and execution from a confined context (LP: #2107455): - d/p/u/lsblk-s390-fixes.patch * Add patch to fix execution of various commands from confined contexts (LP: #2110628): - d/p/u/profiles_ensure_access_to_attach_path.patch * Add patch to include new QtWebEngineProcess execution path in plasmashell profile (LP: #2107723): - d/p/u/plasmashell-QtWebEngineProcess-new-path.patch * Add patch to allow /cvmfs fusermounts (LP: #2110624): - d/p/u/fusermount3_cvmfs.patch * Add patch to grant OpenVPN DNS accesses (LP: #2107596, LP: #2109029): - d/p/u/openvpn_dnsfix.patch * Add patch to expand allowed fusermount3 flags for fuse_overlayfs and sshfs via fstab (LP: #2110626, LP: #2111807): - d/p/u/fusermount3_allow_more_flags.patch * Add patch to fix permission denials for iotop-c (LP: #2107727): - d/p/u/profiles-give-iotop-c-additional-accesses.patch * Add patch to fix parser handling of norelatime mount flag (LP: #2110688): - d/p/u/parser-fix-handling-of-norelatime-mount-rule-flag.patch * Add patch to fix incorrect mount rule documentation in the apparmor.d man page (LP: #2110630): - d/p/u/fix-incorrect-mount-flag-apparmor.d-docs.patch * Add patch to add regression tests for the above two patches: - d/p/u/regression-verify-documented-mount-flag-behavior.patch * d/p/u/remmina_mr_1348.patch, d/p/u/remmina-dbus-describeall.patch: move the remmina profile to profiles/apparmor/profiles/extras to disable it by default (LP: #2102033) * debian/apparmor.install: remove the remmina profile entry * debian/apparmor-profiles.install: add an entry for the remmina profile * debian/apparmor.maintscript: remove the remmina profile upon upgrade -- Ryan Lee Wed, 27 May 2025 11:29:02 -0700 ** Changed in: apparmor (Ubuntu Plucky) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
Hello Ryan, or anyone else affected, Accepted apparmor into plucky-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/4.1.0~beta5-0ubuntu14.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- plucky to verification-done-plucky. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-plucky. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apparmor (Ubuntu Plucky) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-plucky -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
QRT commit 97a96290cd862f2fcf6c4737ddfcfeefe3bfd0d0 was used for testing. After `sudo ./install-packages test-apparmor.py`, I manually installed the -proposed versions of the other apparmor packages. $ apt list --installed '*apparmor*' apparmor-profiles/plucky-proposed,now 4.1.0~beta5-0ubuntu14.1 all [installed] apparmor-utils/plucky-proposed,now 4.1.0~beta5-0ubuntu14.1 all [installed] apparmor/plucky-proposed,now 4.1.0~beta5-0ubuntu14.1 amd64 [installed,automatic] libapparmor-dev/plucky-proposed,now 4.1.0~beta5-0ubuntu14.1 amd64 [installed] libapparmor1/plucky-proposed,now 4.1.0~beta5-0ubuntu14.1 amd64 [installed,autom> libpam-apparmor/plucky-proposed,now 4.1.0~beta5-0ubuntu14.1 amd64 [installed] python3-apparmor/plucky-proposed,now 4.1.0~beta5-0ubuntu14.1 all [installed,aut> python3-libapparmor/plucky-proposed,now 4.1.0~beta5-0ubuntu14.1 amd64 [installe> $ apt policy apparmor-profiles apparmor-profiles: Installed: 4.1.0~beta5-0ubuntu14.1 Candidate: 4.1.0~beta5-0ubuntu14.1 Version table: *** 4.1.0~beta5-0ubuntu14.1 100 100 http://archive.ubuntu.com/ubuntu plucky-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.1.0~beta5-0ubuntu14 500 500 http://archive.ubuntu.com/ubuntu plucky/main amd64 Packages $ apt policy apparmor-utils apparmor-utils: Installed: 4.1.0~beta5-0ubuntu14.1 Candidate: 4.1.0~beta5-0ubuntu14.1 Version table: *** 4.1.0~beta5-0ubuntu14.1 100 100 http://archive.ubuntu.com/ubuntu plucky-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.1.0~beta5-0ubuntu14 500 500 http://archive.ubuntu.com/ubuntu plucky/main amd64 Packages $ apt policy apparmor apparmor: Installed: 4.1.0~beta5-0ubuntu14.1 Candidate: 4.1.0~beta5-0ubuntu14.1 Version table: *** 4.1.0~beta5-0ubuntu14.1 100 100 http://archive.ubuntu.com/ubuntu plucky-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.1.0~beta5-0ubuntu14 500 500 http://archive.ubuntu.com/ubuntu plucky/main amd64 Packages $ apt policy libapparmor-dev libapparmor-dev: Installed: 4.1.0~beta5-0ubuntu14.1 Candidate: 4.1.0~beta5-0ubuntu14.1 Version table: *** 4.1.0~beta5-0ubuntu14.1 100 100 http://archive.ubuntu.com/ubuntu plucky-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.1.0~beta5-0ubuntu14 500 500 http://archive.ubuntu.com/ubuntu plucky/main amd64 Packages $ apt policy libapparmor1 libapparmor1: Installed: 4.1.0~beta5-0ubuntu14.1 Candidate: 4.1.0~beta5-0ubuntu14.1 Version table: *** 4.1.0~beta5-0ubuntu14.1 100 100 http://archive.ubuntu.com/ubuntu plucky-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.1.0~beta5-0ubuntu14 500 500 http://archive.ubuntu.com/ubuntu plucky/main amd64 Packages $ apt policy libpam-apparmor libpam-apparmor: Installed: 4.1.0~beta5-0ubuntu14.1 Candidate: 4.1.0~beta5-0ubuntu14.1 Version table: *** 4.1.0~beta5-0ubuntu14.1 100 100 http://archive.ubuntu.com/ubuntu plucky-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.1.0~beta5-0ubuntu14 500 500 http://archive.ubuntu.com/ubuntu plucky/main amd64 Packages $ apt policy python3-apparmor python3-apparmor: Installed: 4.1.0~beta5-0ubuntu14.1 Candidate: 4.1.0~beta5-0ubuntu14.1 Version table: *** 4.1.0~beta5-0ubuntu14.1 100 100 http://archive.ubuntu.com/ubuntu plucky-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.1.0~beta5-0ubuntu14 500 500 http://archive.ubuntu.com/ubuntu plucky/main amd64 Packages $ apt policy python3-libapparmor python3-libapparmor: Installed: 4.1.0~beta5-0ubuntu14.1 Candidate: 4.1.0~beta5-0ubuntu14.1 Version table: *** 4.1.0~beta5-0ubuntu14.1 100 100 http://archive.ubuntu.com/ubuntu plucky-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.1.0~beta5-0ubuntu14 500 500 http://archive.ubuntu.com/ubuntu plucky/main amd64 Packages `man apparmor.d` shows the corrected example in the section describing mount rules Abbreviated QRT test results from `sudo test-apparmor.py -v` Ran 62 tests in 1583.322s Ok (skipped=3) Test plan verification successful ** Tags removed: verification-needed verification-needed-plucky ** Tags added: verification-done verification-done-plucky -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
** Description changed: [ Impact ] The apparmor.d man page contained incorrect information about the combination of mount options=(list) options in (list), so this documentation should be fixed, and a test included to ensure that the documented behavior matches the actual behavior. [ Test Plan ] Checking the contents of the man page: * Open the apparmor.d man page with `man apparmor.d` and scroll down to the example that starts with `mount options=(ro, atime) options in (nodev, user)` * Verify that the mount commands listed as matching the rule all include ro and atime * The regression test that checks that the behavior is as documented will run as part of the QRT test suite described below - Verification that the documentation matches the current behavior can be done via the QRT test suite, which includes execution of the AppArmor test suite. + Verification that the documentation matches the current behavior can be done via the QRT test suite, which includes execution of the AppArmor test suite via `ApparmorTestsuites`. * To prepare the QRT test suite (can be done on any machine): - `git clone https://git.launchpad.net/qa-regression-testing` - `./scripts/make-test-tarball ./scripts/test-apparmor.py` * To run the QRT test suite: - Copy the tarball onto the machine with the new AppArmor installed and extract it - `sudo ./install-packages test-apparmor.py` -- Reboot the machine + - Reboot the machine - `sudo ./test-apparmor.py -v` [ Where problems could occur ] The man page update is a documentation-only change. The risk exists that the new packaged man page could be malformed, but this is unlikely since the man page is generated by pod2man, and such issues can be caught during testing by attempting to open the man page after installation of the new version. The test suite update, which does not affect the final packaged build, will help ensure that the updated documentation matches the actual behavior. [ Other Info ] This bug was originally reported at https://gitlab.com/apparmor/apparmor/-/merge_requests/1674. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
** Description changed: [ Impact ] The apparmor.d man page contained incorrect information about the combination of mount options=(list) options in (list), so this documentation should be fixed, and a test included to ensure that the documented behavior matches the actual behavior. [ Test Plan ] Checking the contents of the man page: - * Open the apparmor.d man page with `man apparmor.d` and scroll down to the example that starts with `mount options=(ro, atime) options in (nodev, user)` - * Verify that the mount commands listed as matching the rule all include ro and atime - * The regression test that checks that the behavior is as documented will run as part of the QRT test suite described below + * Open the apparmor.d man page with `man apparmor.d` and scroll down to the example that starts with `mount options=(ro, atime) options in (nodev, user)` + * Verify that the mount commands listed as matching the rule all include ro and atime + * The regression test that checks that the behavior is as documented will run as part of the QRT test suite described below Verification that the documentation matches the current behavior can be done via the QRT test suite, which includes execution of the AppArmor test suite. - * To prepare the QRT test suite (can be done on any machine): -- `git clone https://git.launchpad.net/qa-regression-testing` -- `./scripts/make-test-tarball ./scripts/test-apparmor.py` - * To run the QRT test suite: -- Copy the tarball onto the machine with the new AppArmor installed and extract it -- `sudo ./install-packages test-apparmor.py` -- `sudo ./test-apparmor.py -v` + * To prepare the QRT test suite (can be done on any machine): + - `git clone https://git.launchpad.net/qa-regression-testing` + - `./scripts/make-test-tarball ./scripts/test-apparmor.py` + * To run the QRT test suite: + - Copy the tarball onto the machine with the new AppArmor installed and extract it + - `sudo ./install-packages test-apparmor.py` +- Reboot the machine + - `sudo ./test-apparmor.py -v` [ Where problems could occur ] The man page update is a documentation-only change. The risk exists that the new packaged man page could be malformed, but this is unlikely since the man page is generated by pod2man, and such issues can be caught during testing by attempting to open the man page after installation of the new version. The test suite update, which does not affect the final packaged build, will help ensure that the updated documentation matches the actual behavior. [ Other Info ] This bug was originally reported at https://gitlab.com/apparmor/apparmor/-/merge_requests/1674. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2110630] Re: apparmor.d man page contains incorrect information about mount flag combinations
** Also affects: apparmor (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Questing) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu Questing) Status: New => Fix Released ** Changed in: apparmor (Ubuntu Plucky) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
