confinement failure when uploading to store

[Gustavo Niemeyer]

I think it makes sense in general, actually.  The kernel is special because
the image itself is of course not confined, but if/when we introduce hooks
for example, we'll want these to be properly confined, declaring any
interfaces they require to run explicitly as usual for everything else.
Same idea for the gadget snap.

That being the case, having development mode for them also makes sense.



On Mon, Jun 13, 2016 at 9:57 AM, Jamie Strandboge <jamie at canonical.com>
wrote:

> On Mon, 2016-06-13 at 19:20 +0800, Woodrow Shen wrote:
> > Hi all,
> >
> > I have one simple problem about uploading kernel snap to store as I used
> > snapcraft to create my kernel snap. I got the following error after the
> > upload was done:
> >
> > 'confinement' should only be specified with 'type: app'
> > lint-snap-v2_confinement_valid
> >
> > But 'confinement' flag will be added by snapcraft automatically, if I
> don't
> > do that manually. So is it expected for this behavior ?
> >
>
> This sounds like a bug in snapcraft (I've CC'd Sergio to be sure). The
> confinement flag only makes sense in the context of app snaps AFAIK, so
> snapcraft shouldn't be adding it to kernel snaps.
>
> --
> Jamie Strandboge             | http://www.canonical.com
>
>
> --
> Snapcraft mailing list
> Snapcraft at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>
>


-- 
gustavo @ http://niemeyer.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20160613/89716d06/attachment.html>