oxide team mailing list archive

[David Barth <david.barth@xxxxxxxxxxxxx>]

Le 12/03/2014 17:59, Jamie Strandboge a écrit :
> Hi,
>
> Heads up, as the click frameworks discussions are coming to a close it was
> determined that click-apparmor needed to be quite strict about what apparmor
> policy version should be used with which framework. In the normal case, this
> shouldn't matter to anyone other than apparmor devs. However, right now
> click-apparmor 0.2 is likely to land before the ubuntu-sdk-14.04* frameworks are
> available on the image. This will affect webapps/oxide in particular because
> oxide policy only exists in apparmor policy 1.1, which is only valid for
> ubuntu-sdk-14.04* frameworks, but ubuntu-sdk-14.04* frameworks aren't available
> yet. I believe the webapps guys have been specifying the ubuntu-sdk-13.10
> framework with the 1.1 policy version, which is invalid.
>
> As such, until the ubuntu-sdk-14.04* frameworks are available, once
> click-apparmor 0.2 is on your systems, please adjust your click and security
> manifests as per the instructions in the wiki[1]. If
> /usr/share/click/frameworks/ubuntu-sdk-14.04-qml.framework does not exist yet,
> then do:
> $ sudo touch /usr/share/click/frameworks/ubuntu-sdk-14.04-qml.framework
>
> This should allow you to continue testing webapps with the new policy.
Thanks for the heads up Jamie.

This will handle the issue with new webapps, however do you know if old 
framework-13.10/policy 1.0 webapps will continue to work in the new images?

My understanding is that even on an image with framework-14.04, we 
should have framework-13.10 (and policy 1.0) still available for 6 
months or so.

David