pengyos-monitor.service and pengyos-backup.service are Type=oneshot units started by timers, and
both set RemainAfterExit=yes. After the first run the unit stays "active (exited)" until shutdown, and
systemd won't start a unit that's already active. systemctl list-timers showed the monitor timer with
no next run scheduled, and the monitor log had one line per boot: two entries in 21 hours. The backup
timer, off by default, had the same flaw, so a machine that turned it on got exactly one backup per
boot and nothing after that. Every Server-based edition had this since the overlay was first written.
Both units drop the option, as does the unit the backup tool generates.
The nightly loop prepared the rest of the release as one batch of six and built all five images with it in: libnotify 0.8.9, Pengy 1.12.4, starship 1.27.0, uutils-coreutils 0.12.0, and the two GStreamer packages, whose media fixes were already in the image from 26.10.14 and 26.10.21.
Behind that batch, three packages moved to forks, which is what happens when a bump can't close what's
open. ffmpeg 9.0.2 as ffmpeg-pengyos, because 22 of the 25 P0/P1 matches against ffmpeg aren't
something you can patch onto 6.1.5; a fork on the current series takes the upstream fixes whole. hplip
3.26.6 as a fork, which closes all 9 P1 matches where 3.26.4 closes 2. OpenSSH 10.6p1 as a fork,
because Buildroot 2026.08 pinned 10.5p1, which had two remote unauthenticated sshd CVEs. Each fork has
a ledger entry naming the upstream release that retires it, and a source the nightly watches; the fork
budget is enforced by the gate rather than remembered.
One correction from the same session, because it matters more than the arithmetic: the ffmpeg ledger record said the fork closed 22 of 25 matches. It closes 32 of 37. The range was counted wrong, and the number in the record was the one being trusted.