← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1580819] Re: Add support for confinement property

 

This bug was fixed in the package snapcraft - 2.9+16.10

---------------
snapcraft (2.9+16.10) yakkety; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
    (LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
    (LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
    (LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov <sergio.schvezov@xxxxxxxxxx>  Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
       Status: New => Fix Released

-- 
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 snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
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