group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1581166@xxxxxxxxxxxxxxxxxx>]

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/1581166

Title:
  unused and potentially confusing support for plugs/slots at a part
  level in the snapcraft.yaml schema

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]

   * snapcraft has a schema that describes allowed snapcraft.yaml files.
  Part of this schema describes plugs and slots that are defined as the
  level of a part (so not globally and not at the level of an app).

   * keeping this code in the schema can create potential confusion for
  users who expect snapcraft to validate the input to be correct.

   * the change is minimal, altering the schema only

  [Test Case]

   * create a snapcrat.yaml with a part defining a plug and a slot
   * run snapcraft
   * snapcraft should complain about the plug/slot definition at a part level 

  ...
  parts:
    foo:
      plugin: nil
      plugs: [iface1]
      slots: [iface2]
  ...     

  
  [Regression Potential] 

   * snaps that used parts defining plugs or slots will no longer build
   * snaps that will be built after removing the offending declarations will behave exactly as before so the regression potential is minimal

  [Other Info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1581166/+subscriptions