"Yes, keep this update" previously pushed a fresh WizardHomePage, which
always lands on its first step — so confirming felt like being sent
back to square one. Show a terminal "kept" message on the same page
instead, with an explicit button if the user wants to start a new
install.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Adds a package-source toggle so the wizard can take a path to a
downloaded .rpm (verified via `rpm -qp` and resolved to its NEVRA)
in addition to the existing repo-name search flow, since both are
valid targets for `rpm-ostree install`.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
dnf repoquery only matches exact package names, so virtual provides
like "vim" (satisfied by vim-enhanced etc.) falsely failed the Check
step even though rpm-ostree install would resolve them fine. It also
silently reported a broken dnf (e.g. a plugin enabled in config but
missing on disk) as "package not found" instead of flagging it as its
own distinct failure.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Gives HistoryDb an in-memory mode and reconcile() an injectable
deployments list so HistoryService can be exercised hermetically,
without touching the real history.db or shelling out to rpm-ostree.
Covers bootstrap, idempotent reconcile, install-then-reboot,
manual/detected changes, last_known_safe, and chain walking.
Also fixes the pre-existing widget boot-smoke test: startup now makes
a second real Process.run call (via HistoryService.reconcile), which
tipped flutter_test's fake-time zone into flagging a dangling Timer
from that real I/O. Wrapping the pump in tester.runAsync() is the
standard fix.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
rpm-ostree/ostree only retain a couple of deployments, so there's no
durable record of what's been layered since the stock image. Add a
local history DB (lib/history/) keyed on the ostree deployment
checksum, with a parent pointer forming a tree, plus named "current"
and "last_known_safe" pointers.
Reconciling against live `rpm-ostree status --json` on every launch
means the history stays correct even across manual rpm-ostree/bootc
changes made outside this app: any booted checksum we don't recognize
gets recorded as a "detected" node rather than silently ignored.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
A GUI installer wizard for permanent rpm-ostree package layers on
bootc/image-based systems. Walks through: welcome/current-version check,
package name entry with existence check, confirmation, then a streamed
rpm-ostree install via pkexec. On success, writes a pending-confirmation
marker and installs an autostart entry so the next login shows a
"did this update work?" screen with a one-click rollback (bootc rollback
--apply) if not.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
