SRU 1.2 and 1.3 tracking bug

Since I missed the fact that ubuntu-image is now in main since artful, this release introduces new component mismatches for bionic and artful (as needed per classic image support). I am working on getting this cleared out.

We have decided to re-release as 1.3 with the snapcraft dependency removed.

This should be now good to review and release. We removed the component-mismatching dependencies so now all deps are from main as before.

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.3+17.10ubuntu1 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-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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!

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.3+17.04ubuntu1 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-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. 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!

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.3+16.04ubuntu1 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!

Hello Łukasz, or anyone else affected,

Accepted ubuntu-image into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-image/1.3+16.04ubuntu2 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, 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!

Verification for zesty (1.3+17.04ubuntu1):

* Built a snap-based image with `ubuntu-image snap -d -O out/ pc-amd64.assertion` on a zesty cloud instance
* Confirmed on my host kvm that the image is booting
* Built a classic image with `sudo ubuntu-image classic -d -O tmp/ --project=ubuntu-cpc pc-amd64-gadget/prime/` on a zesty cloud instance
* Confirmed on my host kvm that the image is booting

Verification for artful (1.3+17.10ubuntu1):

* Built a snap-based image with `ubuntu-image snap -d -O out/ pc-amd64.assertion` on my artful host machine
* Confirmed that the image is booting
* Built a classic image with `sudo ubuntu-image classic -d -O tmp/ --project=ubuntu-cpc pc-amd64-gadget/prime/` on the same artful host
* Confirmed that the image is booting

All looks fine here as well.

Verification for artful (1.3+16.04ubuntu2):

* Built a snap-based image with `ubuntu-image snap -d -O out/ pc-amd64.assertion` on a xenial cloud instance
* Confirmed that the image is booting on my host kvm
* Built a classic image with `sudo ubuntu-image classic -d -O tmp/ --project=ubuntu-cpc pc-amd64-gadget/prime/` on the same xenial instance
* Confirmed that the image is booting on my host kvm

This bug was fixed in the package ubuntu-image - 1.3+17.10ubuntu1

---------------
ubuntu-image (1.3+17.10ubuntu1) artful; urgency=medium

  * Remove the snapcraft dependency by moving the gadget tree priming step away
    from ubuntu-image. (LP:1734655)
  * Add support for defining the livecd-rootfs configuration path through
    an environment variable. (LP:1734949)
  * SRU tracking number LP: #1729531

ubuntu-image (1.2+17.10ubuntu1) artful; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * SRU tracking number LP: #1729531
  * Add a generic hook mechanism and add our first supported snap-image hook:
    post-populate-rootfs. (LP:1672436)
  * Document the newly added hook API in the ubuntu-image manpage.
    (LP:1715849)
  * Make sure ubuntu-image has 100% code-coverage after getting the classic
    image support added.

  [ Gary Wang ]
  * Add classic image creation support. (LP:1726391)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Mon, 27 Nov 2017 11:12:08 +0100

The verification of the Stable Release Update for ubuntu-image 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.

This bug was fixed in the package ubuntu-image - 1.3+17.04ubuntu1

---------------
ubuntu-image (1.3+17.04ubuntu1) zesty; urgency=medium

  * Remove the snapcraft dependency by moving the gadget tree priming step away
    from ubuntu-image. (LP:1734655)
  * Add support for defining the livecd-rootfs configuration path through
    an environment variable. (LP:1734949)
  * SRU tracking number LP: #1729531

ubuntu-image (1.2+17.04ubuntu1) zesty; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * SRU tracking number LP: #1729531
  * Add a generic hook mechanism and add our first supported snap-image hook:
    post-populate-rootfs. (LP:1672436)
  * Document the newly added hook API in the ubuntu-image manpage.
    (LP:1715849)
  * Make sure ubuntu-image has 100% code-coverage after getting the classic
    image support added.

  [ Gary Wang ]
  * Add classic image creation support. (LP:1726391)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Mon, 27 Nov 2017 11:12:08 +0100

This bug was fixed in the package ubuntu-image - 1.3+16.04ubuntu2

---------------
ubuntu-image (1.3+16.04ubuntu2) xenial; urgency=medium

  * Work-around build-time test_hook_fired issues due to the unavailability of
    sudo on builders. This is xenial-specific as for all other series sudo is
    not used because of a newer mkfs.ext4 available. Use the
    UBUNTU_IMAGE_TESTS_NO_NETWORK flag to skip this test build-time (the test
    is run as part of autopkgtests anyway).

ubuntu-image (1.3+16.04ubuntu1) xenial; urgency=medium

  * Remove the snapcraft dependency by moving the gadget tree priming step away
    from ubuntu-image. (LP:1734655)
  * Add support for defining the livecd-rootfs configuration path through
    an environment variable. (LP:1734949)
  * SRU tracking number LP: #1729531

ubuntu-image (1.2+16.04ubuntu1) xenial; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * SRU tracking number LP: #1729531
  * Add a generic hook mechanism and add our first supported snap-image hook:
    post-populate-rootfs. (LP:1672436)
  * Document the newly added hook API in the ubuntu-image manpage.
    (LP:1715849)
  * Make sure ubuntu-image has 100% code-coverage after getting the classic
    image support added.

  [ Gary Wang ]
  * Add classic image creation support. (LP:1726391)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Mon, 11 Dec 2017 13:36:27 +0100