Comment fixup

ubuntu/yakkety
Ben Howard 9 years ago
parent e931fbeaa5
commit 9a87b066cf

12
debian/changelog vendored

@ -1,3 +1,15 @@
livecd-rootfs (2.354.0~utlemming31) xenial; urgency=medium
* Test build
-- Ben Howard <ben.howard@ubuntu.com> Thu, 12 Nov 2015 17:22:18 -0700
livecd-rootfs (2.354.0~utlemming30) xenial; urgency=medium
* Test build
-- Ben Howard <ben.howard@ubuntu.com> Thu, 12 Nov 2015 17:21:42 -0700
livecd-rootfs (2.354) xenial; urgency=medium
* ubuntu-cpc: extended hooks to build additional cloud image targets

@ -63,7 +63,8 @@ umount_partition() {
modify_vmdk_header() {
# Modify the VMDK headers so that both VirtualBox _and_ VMware can
# read the vmdk and import them. The vodoo here is _not_ documented
# anywhere....so this will have to do.
# anywhere....so this will have to do. This is undocumented vodoo
# that has been learned by the Cloud Image team.
vmdk_name="${1}"
descriptor=$(mktemp)
@ -104,6 +105,11 @@ modify_vmdk_header() {
}
create_vmdk() {
# There is no real good way to create a _compressed_ VMDK using open source
# tooling that works across multiple VMDK-capable platforms. Thie functions
# uses vmdk-stream-converter and then call modify_vmdk_header to produce a
# compatiable VMDK.
src="$1"
destination="$2"
size="${3:-102400}"

@ -2,11 +2,6 @@
# vi: ts=4 noexpandtab
#
# Generate VMDK files
#
# There is no real good way to create a _compressed_ VMDK using open source
# tooling that works across multiple VMDK-capable platforms. This hook uses
# vmdk-stream-converter and then modifies the header manually to produce a
# compatiable VMDK.
architecture=$(chroot chroot dpkg --print-architecture)

Loading…
Cancel
Save