[Bug 1815251] Please test proposed package
Adam Conrad
adconrad at 0c3.net
Tue Feb 19 13:58:16 UTC 2019
Hello Colin, 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.19 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.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1815251
Title:
Build buildd images
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Xenial:
Fix Committed
Status in livecd-rootfs source package in Bionic:
Fix Committed
Bug description:
I've been working for some time on having livecd-rootfs be able to
build buildd chroots. This has a few immediate advantages: it makes
the process of building those chroots more transparent and
reproducible, reduces the pressure on the single person currently
responsible for managing chroots across all architectures, and allows
for a less frustrating chroot update process since I added a facility
to Launchpad last year for updating chroots from a livefs build which
will be a fast API operation rather than something requiring uploading
several hundred megabytes to Launchpad and frequently timing out. I
expect that in the future it can also allow us to have separate
chroots for e.g. -updates at relatively low cost, which will make
builds for stable series substantially faster as they won't need to
apply a large and growing set of upgrades at the start of nearly every
build.
We also have a more recent requirement to build LXD images in order
that we can converge with the images used by snapcraft, and so that we
can use them directly in Launchpad livefs and snap builds rather than
having to convert chroots on the fly. Fortunately it's quite easy to
convert buildd chroots into images usable by LXD, and for now I've
simply translated the approach currently used in launchpad-buildd to
do the conversion on the fly.
Particularly in order to assist with snapcraft convergence but also so
that we can improve build performance for the heavily-used LTS series,
I'd like to backport this support to xenial and bionic. Most of it
has been in disco for a while now, with some recent tweaks.
[Test Case] We'll want to run livefs builds in Launchpad with
appropriate configuration, similar to https://launchpad.net/~ubuntu-
cdimage/+livefs/ubuntu/disco/buildd, and probably then test on dogfood
or similar before unleashing them on production.
[Regression Potential] The patch is substantially just adding another
subproject type so I'm not too concerned, but of course we should
check that a couple of other build types still work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1815251/+subscriptions
More information about the foundations-bugs
mailing list