Comment 0 for bug 1549369
Revision history for this message
| Andrea Bernabei (faenil) wrote Apparmor profiles not updated after deploying an app without increasing its version | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
On Krilli, as of rc-proposed r264,
modifying the application apparmor manifest and then deploying the application to the device *without* increasing the app version will not trigger the apparmor profile update.
As a consequence, the developer is left confused because the app is still complaining about apparmor denials even after he modified the apparmo manifest and deployed the new .click package.
Deploying changes to an application without updating its version number is a quite common practice, especially while in development phase.
That is why I believe we should fix this bug as soon as possible, to make life of developers easier.