SRU 1.5 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.5+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.5+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.5+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.

I have verified 1.5+18.10ubuntu1 as working on my cosmic system. I was using it all the time to build classic images and everything worked as expected.

I also performed one test build of a model-assertion-based image:

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

The pc.img image boots correctly.

I have verified 1.5+18.04ubuntu1 as working on my bionic lxc/kvm environments.

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

The pc.image boots correctly on my host's kvm.

Also tested classic image builds using the primed pc-amd64 gadget tree on a local kvm:

$ sudo ubuntu-image classic -d -p ubuntu-cpc -a amd64 -s bionic pc-amd64-gadget/prime/
(...)
$ cd out
$ ls
filesystem.manifest pc.img

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

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

  [ Alfonso Sanchez-Beato (email Canonical) ]
  * Fix bug with setting file owners in classic. (LP:1783577)
  * Add --filesystem option for classic. This gives us the option to use an
    existing unpacked root file system instead of calling live-build to create
    it. (LP:1782795)
  * Remove content of /boot/grub instead of the full folder, so update-grub
    can still run. (LP:1791049)

  [ Dimitri John Ledkov ]
  * Add python3.7 to tox commands everywhere.

  [ Łukasz 'sil2100' Zemczak ]
  * Fix handling of --extra-ppas for classic builds. (LP:1790708)
  * Check for image/boot/<bootloader> for bootfs additional contents also for
    classic builds. Ignore if it does not exist. (LP:1792561)
  * SRU tracking number LP: #1801332

 -- Łukasz 'sil2100' Zemczak <email address hidden> Tue, 02 Oct 2018 17:07:58 +0200

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.5+18.04ubuntu1

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

  [ Alfonso Sanchez-Beato (email Canonical) ]
  * Fix bug with setting file owners in classic. (LP:1783577)
  * Add --filesystem option for classic. This gives us the option to use an
    existing unpacked root file system instead of calling live-build to create
    it. (LP:1782795)
  * Remove content of /boot/grub instead of the full folder, so update-grub
    can still run. (LP:1791049)

  [ Dimitri John Ledkov ]
  * Add python3.7 to tox commands everywhere.

  [ Łukasz 'sil2100' Zemczak ]
  * Fix handling of --extra-ppas for classic builds. (LP:1790708)
  * Check for image/boot/<bootloader> for bootfs additional contents also for
    classic builds. Ignore if it does not exist. (LP:1792561)
  * SRU tracking number LP: #1801332

 -- Łukasz 'sil2100' Zemczak <email address hidden> Tue, 02 Oct 2018 17:07:58 +0200

I have verified 1.5+16.04ubuntu1 as working on my xenial kvm machine.

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

As for classic build, I have also performed a test image build but only did one with the --filesystem option - but that seemed to have worked as expected.

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

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

  [ Alfonso Sanchez-Beato (email Canonical) ]
  * Fix bug with setting file owners in classic. (LP:1783577)
  * Add --filesystem option for classic. This gives us the option to use an
    existing unpacked root file system instead of calling live-build to create
    it. (LP:1782795)
  * Remove content of /boot/grub instead of the full folder, so update-grub
    can still run. (LP:1791049)

  [ Dimitri John Ledkov ]
  * Add python3.7 to tox commands everywhere.

  [ Łukasz 'sil2100' Zemczak ]
  * Fix handling of --extra-ppas for classic builds. (LP:1790708)
  * Check for image/boot/<bootloader> for bootfs additional contents also for
    classic builds. Ignore if it does not exist. (LP:1792561)
  * SRU tracking number LP: #1801332

 -- Łukasz 'sil2100' Zemczak <email address hidden> Tue, 02 Oct 2018 17:07:58 +0200