aboutsummaryrefslogtreecommitdiff
path: root/scripts/test-configs/zfs-encrypt.conf
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-08-20 08:05:38 -0500
committerCraig Jennings <c@cjennings.net>2026-08-20 08:05:38 -0500
commit6ed8697ae38e30bd7990553d26ea6bb4ef4d3e46 (patch)
treefb28cc7f5f2540ac49217dc3bf8f4707440ac1af /scripts/test-configs/zfs-encrypt.conf
parente9f82d19c75ac8602f5840794d6bd62e30576c30 (diff)
downloadarchangel-6ed8697ae38e30bd7990553d26ea6bb4ef4d3e46.tar.gz
archangel-6ed8697ae38e30bd7990553d26ea6bb4ef4d3e46.zip
fix(build): say so when the ISO ships without archsetupHEADmain
The 2026-08-02 build ran without ARCHSETUP_DIR set and produced a bare ISO with no complaint. A recovery image missing its setup tooling only reveals that on the machine you're recovering, which is the worst place to find out. The build now warns when ARCHSETUP_DIR is unset or points at a non-directory, and the closing summary reports baked or not baked either way. Both go to the build log, since mkarchiso's output buries anything printed mid-run. The remediation hint uses sudo's VAR=value form because build.sh needs root and env_reset drops an exported variable. It uses $HOME rather than a tilde, which zsh leaves unexpanded in an assignment.
Diffstat (limited to 'scripts/test-configs/zfs-encrypt.conf')
0 files changed, 0 insertions, 0 deletions