Glarion/glarion
Watch
1
0
Fork
You've already forked glarion
 0
Code Issues 10 Pull requests Projects Releases Packages Wiki Activity

Automatic update staging is not configured; README claims it is #7

New issue
Open
opened 2026-07-14 19:56:12 +00:00 by james.oates · 0 comments
james.oates commented 2026-07-14 19:56:12 +00:00
Owner
Copy link

The README stated "Updates apply automatically on reboot", but the image configured no automatic update mechanism — updates were manual only (just update + reboot).

Decision (2026-07-15): hybrid update model — stage silently in the background, apply at next reboot, with a gentle "restart when convenient" notification. No Windows-style consent prompts; atomic rollback (just rollback) is the safety net.

Checklist:

  • AutomaticUpdatePolicy=stage via /etc/rpm-ostreed.conf (verified against the rpm-ostreed.conf man page: stage "downloads and unpacks the update, queuing it for the next boot")
  • rpm-ostreed-automatic.timer enabled in the Containerfile — the enable doubles as a build-time existence check for the unit; build passed (commit d8e5609, image published)
  • README corrected to describe actual behaviour
  • Runtime verification on the testbed: install Glarion in a VM, publish a trivial image change, observe it stage without user action and apply on reboot
  • Check whether KDE Discover surfaces staged updates / provides the "restart when convenient" notification out of the box; if not, decide on a minimal notifier
  • Flatpak update automation (Discover default behaviour?) — confirm or configure; out of scope for the OS image staging but part of "simple safe updates" as experienced

Remaining items blocked on the Hetzner testbed (account being set up).

The README stated "Updates apply automatically on reboot", but the image configured no automatic update mechanism — updates were manual only (`just update` + reboot). **Decision (2026-07-15):** hybrid update model — stage silently in the background, apply at next reboot, with a gentle "restart when convenient" notification. No Windows-style consent prompts; atomic rollback (`just rollback`) is the safety net. Checklist: - [x] `AutomaticUpdatePolicy=stage` via `/etc/rpm-ostreed.conf` (verified against the rpm-ostreed.conf man page: stage "downloads and unpacks the update, queuing it for the next boot") - [x] `rpm-ostreed-automatic.timer` enabled in the Containerfile — the enable doubles as a build-time existence check for the unit; build passed (commit d8e5609, image published) - [x] README corrected to describe actual behaviour - [ ] Runtime verification on the testbed: install Glarion in a VM, publish a trivial image change, observe it stage without user action and apply on reboot - [ ] Check whether KDE Discover surfaces staged updates / provides the "restart when convenient" notification out of the box; if not, decide on a minimal notifier - [ ] Flatpak update automation (Discover default behaviour?) — confirm or configure; out of scope for the OS image staging but part of "simple safe updates" as experienced Remaining items blocked on the Hetzner testbed (account being set up).
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Glarion/glarion#7
No description provided.