Migration from make-install systems: runbook, guard, no-move continuity #50

New Issue

2026-09-02T20:21:40Z

xavierk commented

2026-09-02 20:21:40 +00:00

Parent

Ship Fenris as native deb + rpm packages (execute the release plan)

What to build

The path from a make-installed system to packages, runbook-first: a short remove-then-install runbook published in the install docs, an install guard that refuses to coexist with make-install remnants, and verified no-move continuity — store, group, directory permissions, and hand-written configuration all survive in place.

Acceptance criteria

The migration runbook is published in the install docs: mandatory remove-then-install steps, why over-install is forbidden (stale admin-directory units silently shadow vendor units; the local wrapper shadows the package wrapper), no-move continuity, and the reset-to-dormant expectation (the user opts back in with the sanctioned resume)
The guard is verified across the matrix: either make-install marker (the legacy placement manifest, or a unit file under the admin unit directory) causes an abort with a runbook pointer — never auto-clean
No-move continuity is verified in a container seeded with a make-install-shaped system: existing group makes sysusers a no-op, existing store directory makes tmpfiles a no-op, the hand-written configuration survives as a non-database file (package default lands beside it), and the store schema is caught up by the upgrade-path migration
The migration costs at most one short sample gap, honestly recorded in the endurance timeline

Blocked by

Rpm from the same packaging config, dormant install in a Fedora container

## Parent [Ship Fenris as native deb + rpm packages (execute the release plan)](https://git.bongbetic.com/xavierk/Fenris/issues/44) ## What to build The path from a make-installed system to packages, runbook-first: a short remove-then-install runbook published in the install docs, an install guard that refuses to coexist with make-install remnants, and verified no-move continuity — store, group, directory permissions, and hand-written configuration all survive in place. ## Acceptance criteria - [ ] The migration runbook is published in the install docs: mandatory remove-then-install steps, why over-install is forbidden (stale admin-directory units silently shadow vendor units; the local wrapper shadows the package wrapper), no-move continuity, and the reset-to-dormant expectation (the user opts back in with the sanctioned resume) - [ ] The guard is verified across the matrix: either make-install marker (the legacy placement manifest, or a unit file under the admin unit directory) causes an abort with a runbook pointer — never auto-clean - [ ] No-move continuity is verified in a container seeded with a make-install-shaped system: existing group makes sysusers a no-op, existing store directory makes tmpfiles a no-op, the hand-written configuration survives as a non-database file (package default lands beside it), and the store schema is caught up by the upgrade-path migration - [ ] The migration costs at most one short sample gap, honestly recorded in the endurance timeline ## Blocked by - [Rpm from the same packaging config, dormant install in a Fedora container](https://git.bongbetic.com/xavierk/Fenris/issues/46)

xavierk added the ready-for-agent label 2026-09-02 20:21:42 +00:00

xavierk added a new dependency 2026-09-02 20:22:14 +00:00

#46 Rpm from the same packaging config, dormant install in a Fedora container

xavierk referenced this issue from a commit

2026-09-03 08:24:27 +00:00

docs(migration): add make-install-to-package runbook and no-move continuity tests for #50

xavierk closed this issue

2026-09-03 08:24:31 +00:00

Sign in to join this conversation.