Bookworm became oldstable in July 2026 (standard support ended
2026-07-11). A new distro should be built on the current stable, which
is now Trixie (13.6): newer kernel (6.12 LTS vs 6.1, whose LTS ends Dec
2026), newer systemd/containers/toolchains, KDE 6 for the workstation
edition, and a year of stability behind it (full support until
2028-08-09).
- versions.mk / common.sh: DEBIAN_SUITE bookworm -> trixie, kernel 6.1 -> 6.12
- package list header comments: bookworm -> trixie
- GitLab CI: debian:bookworm -> debian:trixie build images
- docs (architecture, building): base references updated
All packages used across the three editions exist in Trixie unchanged.
- 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.
Define the three flagship editions as plain-text manifests:
- server (bastion): production server - observability stack, containers.
- workstation (forge): curated KDE Plasma + dev toolchains.
- cloud (nimbus): cloud kernel, cloud-init, guest agents.
Each manifest carries metadata (services to enable/mask), a package
list, a hardened kernel cmdline, and a btrfs fstab template.
