SRU 1.6 tracking bug

Hello Łukasz, or anyone else affected,

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Łukasz, or anyone else affected,

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

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

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.6+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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Verified ubuntu-image 1.6+18.10ubuntu1 on my cosmic machine:

$ ubuntu-image snap -d -O out/ test.model
(...)
$ ls out/
pc.img seed.manifest snaps.manifest

$ sudo ubuntu-image classic -d -O out/ -p ubuntu-cpc -a amd64 pc-amd64-gadget/prime/
(...)
$ ls out/
filesystem.manifest pc.img seed.manifest snaps.manifest

Sanity tested both images: both successfully booted.

Also, confirmed that the classic build (when ran without --with-proposed) did not pull in packages from -proposed as expected.

Verified ubuntu-image 1.6+18.04ubuntu1 on a bionic kvm:

$ ubuntu-image snap -d -O out/ test.model
(...)
$ ls out/
pc.img seed.manifest snaps.manifest

$ rm -rf out/
$ sudo ubuntu-image classic -d -p ubuntu-cpc -a amd64 -O out/ pc-amd64-gadget/prime/
(...)
$ ls out/
filesystem.manifest pc.img

Verified ubuntu-image 1.6+16.04ubuntu1 on a xenial kvm:

$ ubuntu-image snap -d -O out/ model
(...)
$ ls out/
pc.img seed.manifest snaps.manifest

$ sudo ubuntu-image classic -d -p ubuntu-cpc -O out/ -a amd64 pc-amd64-gadget/prime/
(...)
$ ls out/
filesystem.manifest pc.img seed.manifest snaps.manifest

This bug was fixed in the package ubuntu-image - 1.6+18.10ubuntu1

---------------
ubuntu-image (1.6+18.10ubuntu1) cosmic; urgency=medium

  * Do not copy-over /etc/cloud to the rootfs if it's empty. This can cause
    base snaps that define the writable-path as 'persistent' and 'transition'
    to not be able to provide default configuration. (LP:1808554)
  * Fix --with-proposed handling to properly pass PROPOSED to live-build.
  * SRU tracking number LP: #1808564

 -- Łukasz 'sil2100' Zemczak <email address hidden> Fri, 14 Dec 2018 17:08:09 +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.6+18.04ubuntu1

---------------
ubuntu-image (1.6+18.04ubuntu1) bionic; urgency=medium

  * Do not copy-over /etc/cloud to the rootfs if it's empty. This can cause
    base snaps that define the writable-path as 'persistent' and 'transition'
    to not be able to provide default configuration. (LP:1808554)
  * Fix --with-proposed handling to properly pass PROPOSED to live-build.
  * SRU tracking number LP: #1808564

 -- Łukasz 'sil2100' Zemczak <email address hidden> Fri, 14 Dec 2018 17:08:09 +0100

This bug was fixed in the package ubuntu-image - 1.6+16.04ubuntu1

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

  * Do not copy-over /etc/cloud to the rootfs if it's empty. This can cause
    base snaps that define the writable-path as 'persistent' and 'transition'
    to not be able to provide default configuration. (LP:1808554)
  * Fix --with-proposed handling to properly pass PROPOSED to live-build.
  * SRU tracking number LP: #1808564

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

  * debian/control: add sudo to the list of dependencies as we need it for
    the sudo cp workaround we have in place for xenial's outdated mkfs.ext4
    (LP: #1807750).

 -- Łukasz 'sil2100' Zemczak <email address hidden> Fri, 14 Dec 2018 17:08:09 +0100