Pair bakery update snapshots and configure direct transactions #77
No reviewers
Labels
No labels
P0
P1
P2
P3
audio
bakery
boot
breadbug
bug
build
ci
dependencies
design
disk
docs
encryption
final
firewall
graphics
hardware
idle
installer
keybinds
nvidia
packages
phase-1
polish
recovery
reliability
reproducibility
secure-boot
security
shell
signing
snapshots
supply-chain
swap
tech-debt
theming
ux
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos!77
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/bos-28-paired-bakery-snapshots"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
bos-update now brackets only its bakery step with numbered pre/post Snapper pairs on older bakery builds, including failed updates. It checks configured transaction capability under the same privilege context as the update and delegates snapshot creation to newer bakery to avoid duplicate pairs. The image opts system-prefix bakery into root and home transaction snapshots.
Verified Bash syntax, diff checks, and isolated mock-command tests for success, failed updates, missing home configuration, update ordering, and duplicate prevention. No installed binaries, personal configuration, desktop sessions, or live Snapper state were changed.
Dependency: ECO-47 adds direct/Packages transaction protection to bakery. The BOS config enables that support after a bakery build containing ECO-47 ships; keep this deployment dependency visible during review. Real snapper list acceptance on an installed BOS system remains a separate headless acceptance check.
Closes #28