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
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
