Public bug reported: On Krillin, 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. Reference of a similar bug, which was however more Snappy specific: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1422744 ** Affects: canonical-developer-experience Importance: Undecided Status: New ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: click-apparmor (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Description changed: 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. + + Reference of a similar bug, which was however more Snappy specific: + https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1422744 ** Description changed: - On Krilli, as of rc-proposed r264, + On Krillin, 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. - Reference of a similar bug, which was however more Snappy specific: + Reference of a similar bug, which was however more Snappy specific: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1422744 ** Summary changed: - Apparmor profiles not updated after deploying an app without increasing its version + Updating the apparmor manifest and deploying the new code without increasing the version does not trigger apparmor profile update on the device. ** Summary changed: - Updating the apparmor manifest and deploying the new code without increasing the version does not trigger apparmor profile update on the device. + Updating the apparmor manifest and deploying the new code without increasing app version does not trigger apparmor profile update on the device. -- 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
