Actually, in examining this more closely, adjusting click-apparmor in
this manner will trigger a full policy recompile on first boot after
upgrade. Pat, please let me know if this is acceptable. If not, click
could be adjusted as I suggested and this would not trigger a policy
recompile.
** Changed in: canonical-devices-system-image
Status: Confirmed => Incomplete
** Changed in: canonical-devices-system-image
Assignee: Jamie Strandboge (jdstrand) => (unassigned)
** Changed in: click-apparmor (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: click-apparmor (Ubuntu)
Assignee: (unassigned) => Pat McGowan (pat-mcgowan)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549369
Title:
Updating the apparmor manifest and deploying the new code without
increasing app version does not trigger apparmor profile update on the
device.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1549369/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
