SRU: bootable buildd images for all releases

livecd-rootfs (2.634) focal; urgency=medium

  * Only build bootable buildd images for amd64.
  * Properly setup the chroot before using the network.

 -- David Krauser <> Thu, 12 Dec 2019 13:50:58 -0400

Hello Cody, or anyone else affected,

Accepted livecd-rootfs into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.525.43 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, what testing has been performed on the package 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.

I did the following to validate v2.525.43:

 - Performed livefs build with project ubuntu-base and subproject buildd
 - Ensured the img artifact from that build boots using Multipass
 - Performed a livecd-rootfs build using the rootfs tarball from that build

Everything appears to be working as it should.

This bug was fixed in the package livecd-rootfs - 2.525.43

---------------
livecd-rootfs (2.525.43) bionic; urgency=medium

  [ David Krauser ]
  * Add bootable buildd image w/ fixes (LP: #1863024)

 -- Robert C Jennings <email address hidden> Mon, 30 Mar 2020 09:39:16 -0500

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being 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.

Hello Cody, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.408.61 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, what testing has been performed on the package 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've built the ubuntu-base/buildd project and verified that the resulting .img boots in multipass.

Using the lxd tarball to do a build is still pending.

The xenial changes for 2.408.61 are currently failing verification for me. Depending on the value of the --image-format argument passed to the livefs build, the build results in either a .img that boots (--image-format ext4) or lxd/rootfs tarballs that work (--image-format none), but not both in the same build.

The version of livecd-rootfs in the proposed pocket of Xenial that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days.

Hello Cody, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.408.64 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, what testing has been performed on the package 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.

All autopkgtests for the newly accepted livecd-rootfs (2.408.64) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

livecd-rootfs/2.408.64 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Hello Cody, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.408.65 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, what testing has been performed on the package 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.

All autopkgtests for the newly accepted livecd-rootfs (2.408.65) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/1.10+16.04ubuntu1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

I've built xenial buildd using livecd-rootfs version 2.408.65 and verified the lxd and rootfs tarballs are sized and structured as expected, and that the .img boots in multipass. This confirms verification done for xenial.

This bug was fixed in the package livecd-rootfs - 2.408.65

---------------
livecd-rootfs (2.408.65) xenial; urgency=medium

  [ Joshua Powers ]
  * amd64: revert install grub changes on Xenial (LP: #1901906)

livecd-rootfs (2.408.64) xenial; urgency=medium

  [ Joshua Powers ]
  * amd64: always install grub-efi-amd64-signed (LP: #1901906)

livecd-rootfs (2.408.63) xenial; urgency=medium

  [ John Chittum ]
  * Backport Ensure toolsVersion set in vmdk header (LP: #1893898)

livecd-rootfs (2.408.62) xenial; urgency=medium

  [ Dimitri John Ledkov & Joshua Powers ]
  * amd64: always install grub-pc with shim-signed (LP: #1901906), and
    ensure to autoremove packages

  [ Patrick Viafore ]
  * Increase Vagrant disk size from 10G to 40G (LP: #1580596)

  [ Cody Shepherd ]
  * buildd: ext4: change tar transform target to match changes in bionic+
  * buildd: Skip jasper for buildd subproject
  * buildd: Create manifests for buildd tarballs

livecd-rootfs (2.408.61) xenial; urgency=medium

  * SRU: Enable bootable-buildd hooks for Xenial (LP: #1863024)

 -- Robert C Jennings <email address hidden> Tue, 15 Dec 2020 11:11:14 -0600