[SRU] New stable micro release 2.13.1

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

Bug Description

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

Changed in snapcraft (Ubuntu Xenial):
milestone: none → xenial-updates
Leo Arias (elopio) wrote :

The following verification is required before landing into Xenial:

- Build a snap with 2 stage packages that install the same pc file.
- Build, install and run a snap with a daemon and restart condition never.
- Parse duplicated wiki entry, verify that only the first one is retained and that a warning is logged.
- Build a snap that redefines properties of a remote part with / in the name.
- Build, install and run a plainbox snap.
- Build a maven snap using http proxy.
- Build, install and run a snap using the ant plugin.
- Build a snap with maven targets.
- Build, install and run a snap using the gradle plugin and gradle options.

Exploratory:
- Parse malformed wiki entries, verify the logged errors.
- Push snaps.
- Release snaps.

Launchpad Janitor (janitor) wrote :

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

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

  * New upstream release 2.13 (LP: #1605107)

 -- Sergio Schvezov <email address hidden> Thu, 21 Jul 2016 08:12:25 +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.13 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
Changed in snapcraft (Ubuntu Xenial):
importance: Undecided → High
Changed in snapcraft (Ubuntu Yakkety):
importance: Undecided → High

Tested in an up-to-date xenial:

Installed snapcraft, snapcraft-examples, snapcraft-parser
Enabled -proposed
Updated the three packages to 2.13.

✗ Parse duplicated wiki entry, verify that only the first one is retained and that a warning is logged. https://bugs.launchpad.net/snapcraft/+bug/1605541

tags: added: verification-failed
removed: verification-needed
summary: - [SRU] New stable micro release 2.13
+ [SRU] New stable micro release 2.13.1
description: updated
Steve Langasek (vorlon) on 2016-07-25
description: updated
description: updated

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

tags: removed: verification-failed
tags: added: verification-needed
Leo Arias (elopio) wrote :

Tested in an up-to-date xenial:

Installed snapcraft, snapcraft-examples, snapcraft-parser
Enabled -proposed
Updated the three packages to 2.13.1.

✔ Build a snap with 2 stage packages that install the same pc file.
✔ Build, install and run a snap with a daemon and restart condition never.
✔ Parse duplicated wiki entry, verify that only the first one is retained and that a warning is logged.
✔ Build a snap that redefines properties of a remote part with / in the name.
✔ Build, install and run a plainbox snap.
✔ Build a maven snap using http proxy.
✔ Build, install and run a snap using the ant plugin.
✔ Build a snap with maven targets.
✔ Build, install and run a snap using the gradle plugin and gradle options.

Exploratory:
✔ Parse malformed wiki entries, verify the logged errors.
✔ Push snaps.
✔ Release snaps.

I'm marking this verification as done.

Thanks Adam, Steve and all the contributors to this release!

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

This bug was fixed in the package snapcraft - 2.13.1

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

  [ Joe Talbott ]
  * parser - Add handling for carriage returns in wiki (#681)

  [ Sergio Schvezov ]
  * New upstream release 2.13.1 (LP: #1605107)

 -- Sergio Schvezov <email address hidden> Mon, 25 Jul 2016 13:27:29 +0200

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