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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2110630 Title: apparmor.d man page contains incorrect information about mount flag combinations Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Plucky: Fix Committed Status in apparmor source package in Questing: Fix Released Bug description: [ 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 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 - `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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
