66 Commits (86917060b8e5686187c284f250b7a75f3b15e976)

Author	SHA1	Message	Date
Dimitri John Ledkov	6746d9fbd9	disk-image-uefi: fix riscv64 subarch user-data.	4 years ago
Dimitri John Ledkov	3e1e76b94a	riscv64: fixup subarch build, unbound variable	4 years ago
Dimitri John Ledkov	a808b28d47	riscv64: build preinstalled riscv64 image with uboot SPL and CIDATA.	4 years ago
Dimitri John Ledkov	3962f4ac23	disk-image-uefi: riscv64 add ubuntu:ubuntu login, without expiry.	4 years ago
Dimitri John Ledkov	da578b2c6b	disk-image-uefi: riscv64 add u-boot spl ... LP: #1905274	4 years ago
Dimitri John Ledkov	914997827d	disk-image-uefi.binary: build riscv64 image without a bootloader. ... We want GPT image with ESP, however there is no bootloader for it yet. Build without it.	4 years ago
Dimitri John Ledkov	122364df65	disk-image-uefi.binary: enable secureboot on the arm64 image.	4 years ago
Dimitri John Ledkov	e2fd168f50	amd64: always install grub-pc with shim-signed ... shim-signed depends on grub-efi-amd64-signed, which in turn has alternative depends on either `grub-efi-amd64 | grub-pc`. However to support booting with either via shim&signed-grub and BIOS, the choice must be made to install grub-pc, not grub-efi-amd64. This makes images consistent with Ubuntu Deskop, Live Server, buildd bootable images; all of which already do install grub-pc and shim-signed. LP: #1901906	4 years ago
Joshua Powers	b0c8b628b2	ubuntu-cpc: only install shim-signed, run autoremove ... The CPC build hooks for amd64 incorrectly attempt to install shim-signed in addition to grub-efi-amd64 and grub-pc. These latter two packages conflict with each other. Instead shim-signed should install whatever packages are required. Additionally, this will ensure that autoremove is run after installing anything in the CPC build hooks. This is done to avoid shipping images that include packages that are autoremovable. This will clean-up as packages are installed and detect any breakage at build time.	4 years ago
David Krauser	83499f1a95	Add mechanism to detect initrdless boot fallback ... In v2.672 the default boot behavior of cloud images changed: - Prior to v2.672, cloud images with the linux-generic kernel attempt to boot without an initramfs, would fail, and then retry with an initramfs. - After v2.672, cloud images with the linux-generic kernel boot with an initramfs on the first try. While the behavior is different between the two, they both result in an instance that has booted with an initramfs. To ensure the changes in v2.672 do not regress, we need an automated way to check if we are attempting to boot without an initramfs and failing. With this change, when we attempt to boot with an initramfs and fail, initrdless_boot_fallback_triggered is set to non-zero in the grubenv. This value can be checked after boot by looking in /boot/grub/grubenv or by using the grub-editenv list command.	4 years ago
David Krauser	4c504f6781	Fix broken minimal cloud image boot on amd64 ... I recently pulled initramfs logic out of the base build hook, and dropped that into the `replace_kernel` function. Any cloud image that does not leverage the generic virtual kernel was expected to call `replace_kernel` to pull in a custom kernel. That function will disable initramfs boot for images that use a custom kernel. Minimal cloud images on amd64 use the linux-kvm kernel, but the build hook does not utilize the `replace_kernel` function. Instead, the kernel flavor is set in `auto/config`. I pulled that logic out of `auto/config` and am now calling `replace_kernel` in the build hook. I also moved a call to generate the package list so that it will pick up the change to the linux-kvm kernel.	5 years ago
David Krauser	1ca1330eae	Boot with an initramfs by default in cloud images ... Generic cloud images with the linux-generic kernel are not able to boot without an initramfs. Previously, these images attempted to boot without an initramfs, would fail, and then retry with an initramfs. This slows the boot and is confusing behavior.	5 years ago
David Krauser	0e3b1e206b	Add support for HyperV Gallery images	6 years ago
Robert C Jennings	0bfc5c4290	ubuntu-cpc: Fixup comment references to file names post-parallelization	6 years ago
Robert C Jennings	a45342f269	ubuntu-cpc: avoid duplicate snaps listed in qcow manifest ... commit a993592 introduced an additional call to create_manifest (and snap-seed-parse) to write binary/boot/filesystem.packages. This caused duplicate snap lines in the qcow manifest. This is because the live-build/auto/binary code assumes that after 'lb binary' is run the filesystem.packages will only have debs and it calls snap-seed-parse to add them to the file. The commit changed filesystem.packages in the ubuntu-cpc uefi binary hook to include debs and snaps. This patch keeps the intent of the prior patch, updating the filesystem.packages file for the content of the uefi disk image, but only writes a listing of debian packages to match the expected content of filesystem.packages. The snaps will still be added in generic code in live-build/auto/build.	6 years ago
Tobias Koch	cbd4eb5717	Use series files with dependency handling to generate hook symlinks dynamically ... This patch currently only applies to the "ubuntu-cpc" project. More and more logic has been going into the hook scripts to decide under which conditions they should run or not. As we are moving to parallelized builds of image sets, this will get even more complicated. Base hooks will have to know which image sets they belong to and modification of the dependency chain between scripts will become more complicated and prone to errors, as the number of image sets grows. This patch introduces explicit ordering and dependency handling for scripts through the use of `series` files and an explicit syntax for dependency specification.	6 years ago