Found while testing both installers end-to-end in VMs:
- Wait for archiso's pacman-init.service instead of racing it. The installer
autostarts at login while the live keyring is still being populated
asynchronously, so every package failed with "signature is unknown trust" /
"invalid or corrupted package (PGP signature)". Do not run pacman-key --init
ourselves (corrupts the half-built keyring); wait, then refresh
archlinux-keyring so an ISO built weeks ago still trusts current keys.
- archbaseos-guided-install.sh: honor the answerfile's password/luks_password
fields; previously it always prompted interactively, so a documented
"zero-interaction" netboot/WDS install hung forever with no console.
- Install GRUB to the UEFI removable-media fallback (/EFI/BOOT/BOOTX64.EFI) in
addition to the NVRAM entry. Without it, an installed disk with empty/cleared
NVRAM (fresh board, CMOS reset, or a cloned/redeployed image — the whole point
of this installer) shows "No bootable device". Verified: the disk now boots to
the login manager with fresh NVRAM.
- build.sh: sudo rm -rf the work dir. mkarchiso runs as root and leaves
root-owned files if interrupted, so the next plain rm -rf aborted the script
under set -e before mkarchiso could run.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MUhrcFU8J1Hnf7vNqNxZNi
Amir Alexander Abdelbaki
405e37d243