releaseupdate: an installed install script can silently omit a service, so an update never manages it #995
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#995
Reference in new issue
Block a user
Carina's installed archie-update-install (from the 1.30.0 release) had GATEWAY_SERVICES without archie-messaging. The 1.35.0 update therefore neither backed up nor built/installed/restarted archie-messaging (no archie-messaging.prev was written, and the watchdog restarted only 4 of 5 units), leaving a hand-installed messaging binary in place while everything else moved to 1.35.0. The script refreshes itself from the release source during a run, so the NEXT update manages it — but an update driven by an old script can never repair a binary the old list omitted. Same omission class as the deploy.yml:253 comment. Fix: add a cheap guard that every service the install script manages is listed in GATEWAY_SERVICES (and that every GATEWAY_SERVICES entry has a systemd unit), or fail loudly when a unit exists that the list does not cover.
Close reason
Fixed in
323870a9: the release build and updater guard every host service the installers manage.Imported from beads
archie-core-1faq· GitHub #1102 · type bug · priority P2 · created 2026-09-22 · closed 2026-09-26