Last commit made on 2020-12-11
Get this branch:
git clone -b sil2100/appliance-qcow2
Members of Ubuntu Core Development Team can upload to this branch. Log in for directions.

Branch merges

Branch information


Recent commits

69195a0... by Łukasz Zemczak

Build appliance qcow2 images only for amd64 appliances.

0e35dfd... by Łukasz Zemczak

We need to do it in a different order.

a976382... by Łukasz Zemczak

Try building qcow2 images for appliances.

83b582c... by Robert C Jennings

actually releasing package livecd-rootfs version 2.525.48

My prior commit had the wrong suite

cc37151... by Robert C Jennings

releasing package livecd-rootfs version 2.525.48

e6dc732... by Robert C Jennings

Merge bionic-open-vm-tools-backport into ubuntu/bionic [a=jchittum] [r=rcj]

Backport vmtools version in vmdk (LP: #1893898)

LP: #1893898 describes missing vmtools version from the vmdk headers.
The version should be added as ddb.toolsVersion = "2147483647" however
the sed was no longer replacing a ddb.comment field with the tools
version. Rather than subbing ddb.comment with toolsVersion, this commit
deletes ddb.comment (which the comment mentions could cause errors),
and adds the correct value. There was no visibility into the descriptor
during hook creation, so debug statements were added. This allows us to
quickly verify in the logs that bad statements are removed (the possibly
offending comments), as well as ensuring that the toolsVersion is added


b5e2192... by Robert C Jennings

Merge bionic-sru-grub into ubuntu/bionic [a=powersj] [r=patviafore,rcj]

SRU always install grub-pc with shim-signed (LP: #1901906), and ensure to autoremove packages


8842b05... by Robert C Jennings

Merge vagrant_40_gb_bionic into ubuntu/bionic [a=patviafore] [r=rcj]

Make Ubuntu Vagrant box 40G. (LP: #1580596)

Vagrant images were previously put at 10G, but this was a regression
from Trusty, in which they were 40G. This made it a tough sell for
users to upgrade if they were using a Ubuntu desktop experience.

This change does not impact disk usage as Vagrant with the virtualbox
provider dynamically allocates space with the VMDK. On a test system,
the VMDK took up 1.1G of disk space according to df, and after
creating a 2G file in Vagrant, the VMDK grew to 3.1G.

Therefore, users who are running on a system with little free space will
not see adverse effects if they upgrade to a new vagrant image


1834666... by John Chittum

Open and update changelog

Open new version, add changelog description

45abf7c... by John Chittum

re-add sed command

Older version of vmdk-stream-converter has an incorrect header. The
original sed command replaced the incorrect "Description File" comment
with the correct "Disk DescriptorFile".