test_aa-exec-click autopkgtest should not hardcode aa-exec path
Bug #1581210 reported by
Tyler Hicks
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| click-apparmor (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
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.
Related branches
| description: | updated |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in click-apparmor (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This bug was fixed in the package click-apparmor - 0.3.15
---------------
click-apparmor (0.3.15) yakkety; urgency=medium
* debian/
aa-exec into /usr/bin/. Adjust the test so that it doesn't hardcode the
aa-exec install path. (LP: #1581210)
-- Tyler Hicks <email address hidden> Sat, 04 Jun 2016 00:38:21 -0500