group.of.nepali.translators team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxx>]

Verified that 'confinement: strict' properly errors with 'plugs: [ network-control ]':
Errors
------
 - security-snap-v2:plug_safe:network-control:network-control
	reserved interface 'network-control' for vetted applications only

and that 'confinement: devmode' shows no error with 'plugs: [ network-
control ]'

** Also affects: click-reviewers-tools (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: click-reviewers-tools (Ubuntu Yakkety)
       Status: New => Fix Released

** Changed in: click-reviewers-tools (Ubuntu Xenial)
       Status: New => Fix Committed

** Changed in: click-reviewers-tools (Ubuntu Xenial)
     Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: click-reviewers-tools (Ubuntu Yakkety)
     Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1580819

Title:
  Add support for confinement property

Status in Canonical Click Reviewers tools:
  Fix Released
Status in Snapcraft:
  Fix Committed
Status in click-reviewers-tools package in Ubuntu:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in click-reviewers-tools source package in Xenial:
  Fix Committed
Status in snapcraft source package in Xenial:
  Fix Committed
Status in click-reviewers-tools source package in Yakkety:
  Fix Released
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * Snaps need to be able to specify if they require devmode or if they
  can be run confined. This will allow for snapd to provide reasonable
  errors if one tries to install a snap that cannot run successfully
  under confinement.

   * The YAML property should be called "confinement," and it should
  have two options: "devmode" and "strict." It should be optional, and
  `snapcraft init` should set it to "devmode."

   * The "confinement" YAML property should be copied into the resulting
  `snap.yaml`.

  * Example YAML:

          name: foo
          version: 1
          summary: foo
          description: foo
          confinement: devmode
          
          parts:
            foo:
              plugin: nil

  [Test Case]

   * Run `snapcraft init`. Make sure "confinement" is "devmode."

   * Create a valid snapcraft.yaml and run `snapcraft` on it. Make sure
  the "confinement" value gets copied to the `snap.yaml`.

   * Create a valid snapcraft.yaml and remove the "confinement"
  property. Run `snapcraft`. It should print a hint about defaulting to
  "strict", and "confinement: strict" should be in the resulting
  `snap.yaml`.

  [Regression Potential]

   * snapcraft.yaml validation could be incorrect (required properties
  may not be required correctly, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1580819/+subscriptions