The edition package lists installed BOTH grub-pc and grub-efi-amd64
(+ shim-signed). Those provide the same bootloader role and conflict in
apt, so every rootfs build failed with "unable to correct problems, you
have held broken packages".
A rootfs now carries exactly ONE bootloader, chosen by the BOOT variable
(mirroring the existing --boot bios|efi deploy option):
- versions.mk / common.sh: BOOT := bios (bios -> grub-pc,
efi -> grub-efi-amd64 + shim-signed + mokutil), exported via the
Makefile.
- build-rootfs.sh validates BOOT early and injects the matching boot
packages into the apt install; the static package lists no longer
contain any grub package.
- deploy-disk.sh / build-image.sh / install.sh default --boot from the
same BOOT variable, so a rootfs and the artifact deployed from it can
never disagree (BOOT=efi make image-cloud produces a UEFI image).
- mokutil is now installed explicitly in the efi flavour (it was not
pulled in because we install with --no-install-recommends).
- docs updated (building.md knob + rationale, secureboot.md note).
- deploy-disk.sh: the shared "write a finished system to a disk" step —
partition (GPT bios/efi) -> btrfs layout via btrfs/init.sh -> rsync
rootfs -> chroot (real fstab, GRUB, hostname). Carries the optional
ARCLINE_SIGN hook; the signing tooling itself lands in a later commit.
- apply-fstab.sh: renders the edition fstab template with real root/efi
UUIDs and drops the swap line.
- build-image.sh: rootfs -> bootable qcow2/raw disk image (sparse file +
loop device + deploy), the cloud edition's primary output.
- install.sh: scripted installer for a real disk, confirmation-gated.
- Makefile: image-<edition> targets (+ minimal variants); build-edition.sh
learns the "image" stage; cloud metadata now ships a disk image.
- check-host-deps.sh / GitLab CI: add gdisk, parted, rsync, dosfstools,
qemu-utils, dpkg, sbsigntool to the build image.
