touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #84123
[Bug 1449769] Re: Update apparmor python utils to 2.9.2 version in trusty
I have gone through and verified each of the individual linked bug
reports are fixed in the version of apparmor-utils/python3-apparmor in
trusty-proposed. I've also gone through and ran the lp:qa-regression-
testing test-apparmor.py script against the version in trusty-proposed
on both i386 and amd64 and with 3.13, 3.16 and 3.19 kernels, and did not
see any test failures. Also, while going through and verifying the bug
reports, I did not see any regressions in behavior and note that the
behavior of the tools is significantly improved. Based on this, I'm
marking verification-done for this bug report.
** Tags added: verification-done
--
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/1449769
Title:
Update apparmor python utils to 2.9.2 version in trusty
Status in apparmor package in Ubuntu:
In Progress
Bug description:
[impact]
Leading up to the release of 14.04, we decided to pull in a pre-release
version of the python utils, because we did not want to continue
supporting the out of date perl tools for the 5 years of the 14.04
release support lifetime. There were a number of issues with the
python tools that prevent users from using them effectively that
have subsequently been addressed by upstream releases, as well as
the addition of a significant number of tests.
Specific bugs that should be addressed by this include:
bug 1294797: aa-genprof traceback with apparmor 2.8.95
bug 1319829: aa-genprof will crash when selecting scan
bug 1317176: aa-logprof attempts to read program binary instead of profile
bug 1324154: aa-logprof is trying to process a binary instead of the profile
bug 1310598: AppArmor python tools fail to parse mounts with UTF-8 non-ascii characters
bug 1378095: aa-complain traceback when marking multiple profiles
[steps to reproduce]
1) attempt to use the aa-genprof/aa-logprof to generate or update
policy
[regression potential]
It's possible that the simple management tools, aa-enforce,
aa-complain, and aa-disable could be broken by this
large update. However, the test-apparmor.py script from
lp:qa-regression-testing attempts to exercise those scripts
to ensure they still function. Regressions could be introduced
in aa-genprof and aa-logprof, but they would need to be pretty
substantial to outweigh the improvement in quality that the 2.9.2
tools represent. Furthermore, a number of testcases have been added
(and again are driven by lp:qa-regression-testing) to try to prevent
the introduction of regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1449769/+subscriptions
References