[SRU] New stable micro release 2.15

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

Bug Description

This is an SRU bug to release 2.15 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.15 and https://launchpad.net/snapcraft/+milestone/2.15.1

Changed in snapcraft (Ubuntu Xenial):
milestone: none → xenial-updates
Launchpad Janitor (janitor) wrote :

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

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

  [ Harald Sitter ]
  * add multiple generator script options to autotools (#679)

  [ Sam Yaple ]
  * python2 plugin: Add support for constraints (#657)

  [ Blake Rouse ]
  * Add option disable-parallel for all plugins. (#698)
  * python3 plugin: allow setup.py to work on some projects. (#718)

  [ Christian Ehrhardt ]
  * fix checker errors to let runtests.sh pass again (#717)

  [ Dan Watkins ]
  * python plugins: add process-dependency-links option (#734)

  [ Leo Arias ]
  * Start the fake parts server only in the tests that need it. (#720)
    (LP: #1611828)
  * In travis, install the static checkers with pip. (#724)
  * go plugin: add a go-buildtags property to the plugin (#733)

  [ Joe Talbott ]
  * Set owner/group for directories in stage and prime (#723)
  * parser - Return non-zero code for wiki errors. (#658)
  * Factor parts config into snapcraft/internal/parts.py (#731)

  [ Kyle Fazzari ]
  * Use link_or_copy instead of just hard-links for deb cache. (#728)
  * Support having the snapcraft.yaml in a subdir. (#725)
  * Dump plugin: Don't remove install directory. (#729)

  [ Jason Hobbs ]
  * Add artifacts option to make plugin. (#715)

  [ Michael McCracken ]
  * Clarification of make plugin help text (#730)

  [ Sergio Schvezov ]
  * Globally cache stage-packages (#677)
  * Remove store dispute logic (#732)
  * New upstream release 2.15 (LP: #1614322)

 -- Sergio Schvezov <email address hidden> Wed, 17 Aug 2016 17:47:44 -0300

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.15 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 :

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

plugins:

autotools:
- build the VLC snap.

python2:
- build a snap using constraints.
- build a snap using process-dependency-links.

python3:
- build a snap using process-dependency-links.

go:
- build the vault snap.

dump:
- build a snap with dump and stage packages.

make:
- build a snap with artifacts instead of an install target.

general:
- run snap commands with parallel build disabled.
- run the owner/group manual test: https://github.com/snapcore/snapcraft/blob/master/manual-tests.md#test-file-ownership-is-retained
- build a snap from with snapcraft.yaml in a subdir.
- run the cache manual test: https://github.com/snapcore/snapcraft/blob/master/manual-tests.md#test-stage-package-caching

parser:
- run the parser with an error and check the exit code.

store:
- try to register an already reserved snap name.

Leo Arias (elopio) wrote :

Tested in an up-to-date xenial virtual machine with kvm.

I installed snapcraft, snapcraft-examples and snapcraft-parser, version 2.14. Then enabled proposed and updated those packages to 2.15.

✓ build the VLC snap.
✓ build a snap using constraints.
 build a snap using process-dependency-links.
✓ build the vault snap.
✓ build a snap with dump and stage packages.
✓ run snap commands with parallel build disabled.
✓ run the owner/group manual test.
✓ run the cache manual test.
✓ run the parser with an error and check the exit code.
✓ try to register an already reserved snap name.

✗ build a snap with artifacts instead of an install target. https://bugs.launchpad.net/snapcraft/+bug/1614754
✗ run the parser with an error and check the exit code. https://bugs.launchpad.net/snapcraft/+bug/1602394/comments/2

description: updated
Steve Langasek (vorlon) wrote :

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.15.1 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!

Leo Arias (elopio) wrote :

The verification for 2.15 failed on xenial, so 2.15.1 was released with a few small fixes.

I tested it in an up-to-date xenial virtual machine with kvm.

I installed snapcraft, snapcraft-examples and snapcraft-parser, version 2.14. Then enabled proposed and updated those packages to 2.15.1.

Then I ran the following tests:

✓ build a snap with artifacts instead of an install target.
✓ run the parser with an error and check the exit code.
✓ build a snap with chown warnings, check that they are printed only with --debug.
✓ build a part that depends on a library part

I'm marking this bug as verified so it can land in xenial. Thanks Steve and Chris!

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package snapcraft - 2.15.1

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

  [ Robert Ancell ]
  * Remove .la files generated by autotools (#670)

  [ Joe Talbott ]
  * Only show chown warnings with --debug. (#739)
  * Actually return a non-zero error code on errors. (#745)

  [ Sergio Schvezov ]
  * make plugin: fix artifact collecting (#743)
  * testing: only run the ros demo on xenial (#744)
  * New upstream release 2.15.1 (LP: #1614322)

 -- Sergio Schvezov <email address hidden> Fri, 19 Aug 2016 13:43:42 -0300

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