pengyos-backup.timer was enabled in the Server layer, which means it was enabled in every edition
built on it, both Desktops included. Its default tars all of /etc and /home every night into
/var/backups/pengyos, on the same disk, keeping 7 copies. A Desktop with a Steam library or big Flatpak
data in /home ran out of space. It's disabled by a preset now, and the way it had to be done is the
lesson: removing the timers.target.wants/ symlink wasn't enough, because the image build runs
systemctl preset-all, which re-enabled the timer from the unit's own [Install] section. The Server
smoke matrix caught that.
Installed machines lose the enabled timer on update, since /etc is an overlay over the image's copy,
unless someone on that machine enabled it deliberately. The units and backup.conf still ship: set
BACKUP_DEST to another disk and systemctl enable --now pengyos-backup.timer. Tarballs already sitting
in /var/backups/pengyos stay until you delete them.
Linux went from 7.2.5 to 7.2.11 across every edition. nvidia-open went 610.57.04 → 615.78.08, NVIDIA's
current feature branch, in both NVIDIA editions; the module now requests ucodes_ga10x.bin and
ucodes_tu10x.bin beside the GSP firmware, so those ship too. Both bumps were made by hand rather than
by the nightly loop, because the loop is deliberately not allowed to move those two.
The maintenance loop got a web page for decisions. The loop proposes package bumps and security carries; the page shows each one with what it closes, and an approval or refusal is recorded against it, with the refusal reason kept. It also stopped offering approvals the act lane could never actually execute, which is a small thing that wastes an afternoon if you don't fix it.