This bug was fixed in the package click-apparmor - 0.3.15
---------------
click-apparmor (0.3.15) yakkety; urgency=medium
* debian/tests/test_aa-exec-click: Upstream AppArmor >= 2.10.95 now installs
aa-exec into /usr/bin/. Adjust the test so that it doesn't hardcode the
aa-exec install path. (LP: #1581210)
-- Tyler Hicks <[email protected]> Sat, 04 Jun 2016 00:38:21 -0500
** Changed in: click-apparmor (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1581210
Title:
test_aa-exec-click autopkgtest should not hardcode aa-exec path
Status in click-apparmor package in Ubuntu:
Fix Released
Bug description:
The apparmor 2.11 beta 1 release (2.10.95) moved aa-exec from
/usr/sbin/ to /usr/bin/ but the test_aa-exec-click hard codes the path
as /usr/sbin/aa-exec.
The click-apparmor test needs to be updated so that the apparmor
package's install logic can follow upstream's lead regarding the aa-
exec path.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1581210/+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
