[SRU] New stable micro release 2.39.2

[Sergio Schvezov]

This is an SRU bug to release 2.39.2 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://github.com/snapcore/snapcraft/milestone/14?closed=1

Releases since 2.35 and this one are defined at:
https://github.com/snapcore/snapcraft/milestone/13?closed=1
https://github.com/snapcore/snapcraft/milestone/12?closed=1
https://github.com/snapcore/snapcraft/milestone/11?closed=1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sergio Schvezov (sergiusens)]

Successful runs on xenial (using dev autopkgtests):
- amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-snapcraft-daily/xenial/amd64/s/snapcraft/20180220_140404_01073@/log.gz
- arm64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-snapcraft-daily/xenial/arm64/s/snapcraft/20180220_211402_01073@/log.gz

...and somewhat successful run on armhf (dns timeouts): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-snapcraft-daily/xenial/armhf/s/snapcraft/20180220_195013_01073@/log.gz (a previous run passed on the ones these dns timedout)

[Łukasz Zemczak (sil2100)]

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.39.2 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 on 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

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

[Launchpad Janitor (janitor)]

This bug was fixed in the package snapcraft - 2.39.2+18.04.2

---------------
snapcraft (2.39.2+18.04.2) bionic; urgency=medium

  [ Sergio Schvezov ]
  * tests: improvements to demos (#1938)
  * tests: remove the webcam-webui demo (#1940)
  * elf: contemplate more patching scenarios (#1935)
  * New upstream release (LP: #1745488)

  [ Kyle Fazzari ]
  * tests: remove duplicate tests (#1928)
  * schema: remove underscore from version pattern (#1933)
  * store: support pushing snap with no architectures (#1937)
  * storeapi: handle errors even for >400 responses (#1936)

  [ Christian Dywan ]
  * sources: proper errors for invalid handlers (#1929)

  [ Sylvain Pineau ]
  * tests: update the plainbox-provider tests (#1931)

 -- Sergio Schvezov <email address hidden> Tue, 20 Feb 2018 00:40:00 +0000

[Leo Arias (elopio)]

The latest snapcraft released to the stable distros was 2.35. So, in order to accept this update, the following tests need to be executed:

For 2.36:

snapcraft.yaml:

    Build a snap with $SNAPCRAFT_ARCH_TRIPLET in the snapcraft.yaml.

Store:

    Run snapcraft push-metadata.

Exploratory:

    Build and run python snaps.
    Build snaps with $SNAPCRAFT_CONTAINER_BUILDS=local snapcraft, and run different clean commands.

For 2.37:

Store:

    Run the export-login command.
    Try to register a reserved name.
    Run snapcraft list-keys with no keys.
    Run the push metadata manual tests.

Exploratory:

    Run snapcraft help with multiple options.
    Build and run classic snaps.
    Run snapcraft commands that will return errors.

For 2.38:

Metadata:

    Build snaps with adopt-info and parse-info in the snapcraft.yaml, and an appstream metadata file.

Exploratory:

    Build snaps in docker.
    Build snaps with build-snaps in the snapcraft.yaml, with valid and invalid values.
    Build snaps with $SNAPCRAFT_CONTAINER_BUILDS=local snapcraft.
    Build snaps with advanced grammar in sources.

For 2.39:

Commands:

    Run snapcraft help.

Metadata:

    Build snaps with adopt-info and parse-info in the snapcraft.yaml, and an appstream metadata file that provides icon and desktop files.

Store:

    Run snapcraft export-login with expiration.
    Run snapcraft push.
    Push a snap without architectures.

Containers:

    Build snaps in docker using the beta and edge images.

Exploratory:

    Build classic snaps.
    Build snaps without UTF-8 locale.
    Build snaps with $SNAPCRAFT_CONTAINER_BUILDS=local snapcraft.
    Build snaps with socket activation.
    Try to build snaps with invalid sources.

[Leo Arias (elopio)]

I have been running the tests to verify this SRU. I found no blockers, so I'm marking this as verified. Please, continue with the release process.

[Sergio Schvezov (sergiusens)]

We cannot successfully work on an artful release as:
1- snapcraft is mostly designed to build on a host that matches a current "base" (today, the only base is "core" which is 16.04 based).
2- artful will most likely not have a base.
3- artful experienced the glibc bump which caused built snaps on artful to be non functional when snapped (given the base mismatch).
4- bionic has experimental fixes to patch binaries and libc6 inclusion logic which has not reached the release pocket yet and is a prerequisite if we ever want this to work on artful

Last but not least, I would like to propose not supporting non LTS as debs and have those users resort to the snapcraft snap.

[Launchpad Janitor (janitor)]

This bug was fixed in the package snapcraft - 2.39.2

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

  [ Sergio Schvezov ]
  * tests: improvements to demos (#1938)
  * tests: remove the webcam-webui demo (#1940)
  * elf: contemplate more patching scenarios (#1935)
  * New upstream release (LP: #1745488)

  [ Kyle Fazzari ]
  * tests: remove duplicate tests (#1928)
  * schema: remove underscore from version pattern (#1933)
  * store: support pushing snap with no architectures (#1937)
  * storeapi: handle errors even for >400 responses (#1936)

  [ Christian Dywan ]
  * sources: proper errors for invalid handlers (#1929)

  [ Sylvain Pineau ]
  * tests: update the plainbox-provider tests (#1931)

 -- Sergio Schvezov <email address hidden> Tue, 20 Feb 2018 00:40:00 +0000

[Łukasz Zemczak (sil2100)]

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.

[Stéphane Graber (stgraber)]

This new version of snapcraft appears to break all builds on s390x...

[Stéphane Graber (stgraber)]

A fix was uploaded to Xenial and will be rushed to -updates once built and published.

[Stéphane Graber (stgraber)]

And fix released to updates.