[SRU] New stable micro release 2.14

Bug #1611009 reported by Sergio Schvezov on 2016-08-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapcraft (Ubuntu)
Wishlist
Unassigned
Xenial
Wishlist
Unassigned
Yakkety
Wishlist
Unassigned

Bug Description

This is an SRU bug to release 2.14 of snapcraft which follows the guidelines defined in the wiki over at https://wiki.ubuntu.com/SnapcraftUpdates

The list of bugs and features in this release are defined at https://launchpad.net/snapcraft/+milestone/2.14

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package snapcraft - 2.14+16.10.1

---------------
snapcraft (2.14+16.10.1) yakkety; urgency=medium

  * debian/tests/snapstests: disable the ros test as there are network
    errors.

 -- Sergio Schvezov <email address hidden> Tue, 09 Aug 2016 13:31:07 +0000

Changed in snapcraft (Ubuntu Yakkety):
status: New → Fix Released

Hello Sergio, or anyone else affected,

Accepted snapcraft into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapcraft/2.14 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in snapcraft (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed
Leo Arias (elopio) wrote :

This are the tests that must be executed in order to verify the package:

Packaging:
* Install snapcraft in a virtualenv using the requirements files.
* Run the tests in a virtualenv using the requirements-test file.

Init:
* Run snapcraft init with an existing .snapcraft.yaml file.

Parser:
* Run the parser using a part defined in .snapcraft.yaml

Plugins and snaps:
* Build a rust snap.
* Build a python2 snap and check that the pyc files are removed.
* Build a python2 snap and check that the shebangs use env.
* Build a python3 snap and check that the shebangs use env.
* Build a snap with a oneshot daemon.
* Build a snap using the godeps plugin.
* Run the ROS example snap in xenial.
* Build mhall's Arduino IDE snap.
* Build the OS snap, check the file ownership.
* Build kernel snaps with debarch targets.

Autocomplete:
* Autocomplete with register, tour, push, release, prime, update, define, search.

Store:
* Run the integration tests using the staging store.
* Run the integration tests using the production store.

Exploratory:
* Build snaps using the go plugin.
* Build snaps using the dump plugin.

Leo Arias (elopio) wrote :

Init:
✔ Run snapcraft init with an existing .snapcraft.yaml file.

Parser:
✔ Run the parser using a part defined in .snapcraft.yaml

Plugins and snaps:
✔ Build a rust snap.
✔ Build a python2 snap and check that the pyc files are removed.
✔ Build a python2 snap and check that the shebangs use env.
✔ Build a python3 snap and check that the shebangs use env.
✔ Build a snap with a oneshot daemon.
✔ Build a snap using the godeps plugin.
✔ Run the ROS example snap in xenial.
✔ Build mhall's Arduino IDE snap.
✔ Build the OS snap, check the file ownership.
✔ Build kernel snaps with debarch targets.

Autocomplete:
✔ Autocomplete with register, tour, push, release, prime, update, define, search.

Store:
✔ Run the integration tests using the staging store.
✔ Run the integration tests using the production store.

Exploratory:
✔ Build snaps using the go plugin.
✔ Build snaps using the dump plugin.

✗ Packaging:
* Install snapcraft in a virtualenv using the requirements files.
* Run the tests in a virtualenv using the requirements-test file.
There is still work to do here, but not a blocker for this release: bug #1611498
This is not related to the package in xenial, just affects the developer experience from master. The work done in this milestone gets us closer to work nicely in a virtualenv, which wasn't working before, so not are regression either.

I'm going to mark this bug as verified. Thanks Steve!

tags: added: verification-done
removed: verification-needed
Changed in snapcraft (Ubuntu Xenial):
milestone: none → xenial-updates
Changed in snapcraft (Ubuntu Yakkety):
milestone: xenial-updates → none
Changed in snapcraft (Ubuntu Xenial):
importance: Undecided → Wishlist
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package snapcraft - 2.14

---------------
snapcraft (2.14) xenial; urgency=medium

  [ Joe Talbott ]
  * Add python package dependencies to setup.py (#550)
  * parser - Support .snapcraft.yaml files. (#618)
  * Preserve file ownership for 'os' snaps. (#690)

  [ Marius Gripsgard ]
  * Add new plugin: rust (#579)

  [ Sam Yaple ]
  * Fix python2 compile cache removal (#660)
  * Improve python2 test coverage (#663)

  [ Stéphane Graber ]
  * Implement "oneshot" daemon type (#693)

  [ Bogdana Vereha ]
  * Replace 'strip' with 'prime' on intro page and step options. (#696)

  [ Kyle Fazzari ]
  * Rewrite shebangs generated by the python plugins. (#680)
  * Add godeps plugin. (#691)
  * Catkin plugin: Enforce C.UTF-8 locale. (#497)

  [ Blake Rouse ]
  * Pass --root to the python3 plugin on build (#694)
  * Add make-install-var field to the make plugin. (#711)

  [ Sebastian Bacher ]
  * Use the new snapcraft.io mailing list as contact information (#702)
  * Update the completion list of commands (#703)
  * Slightly tweak the "no jar files" errors (#704)

  [ Liu XiaoGuo ]
  * Added "camera" plug into the example (#706)

  [ Simon Quigley ]
  * Update the debian/control file (#662)
  * Add detection for an existing `.snapcraft.yaml` file before running
    `snapcraft init` (#669)

  [ Michael Hall ]
  * Strip common path prefixes from linkname as well as name when extracting
    a tarfile. (#688)

  [ Leo Arias ]
  * Use requirements files in travis tests (#656)
  * Enable integration tests to run in the production store (#687)

  [ Daniel Watkins ]
  * Make formatting of daemon options consistent (#710)

  [ Sergio Schvezov ]
  * Run tests from /tmp (#684)
  * Use the proper requirements.txt path (#707)
  * Improve the go plugins usability (#709)
  * kernel plugin: kernel targets depending on debarch (#689)
  * New plugin: dump (#712)
  * rust plugin: mock downloads in unit tests (#713)
  * New upstream release 2.14 (LP: #1611009)

 -- Sergio Schvezov <email address hidden> Mon, 08 Aug 2016 14:58:39 +0000

Changed in snapcraft (Ubuntu Xenial):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for snapcraft has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers