0039 (ADR-016): Upgrades come from the Keel repository #44

New issue

Open

opened 2026-09-30 10:11:03 -03:00 by marcos-mendez · 0 comments

marcos-mendez commented

2026-09-30 10:11:03 -03:00

(Migrated from github.com)

Decision (maintainer, 2026-09-30). Everything Keel installs is a .deb in the Keel repository, overlays included; apt upgrade is the only update mechanism. Application packages carry a post-install migration hook (Odoo module update, Mastodon db:migrate). Mesh-aware ordering: a database primary never upgrades while primary; it hands over, upgrades, returns after catch-up. Two tracks, stable and testing, declared in the YAML; simple defaults to stable with security-only unattended upgrades. The YAML is re-emitted after every upgrade.

Handbook: docs/decisions/0039-upgrades-from-the-keel-repository.md (handbook#26)

Amends: 0016 (tracks share the channels' two names; a third is a decision), 0012 (unchanged, the pool builds the repository), 0020 (upgrade order becomes handover and return after catch-up), 0022 (superseded on how Odoo is updated).

Review notes (resolved by the maintainer, 2026-09-30)

0022 upgrades Odoo by moving a git checkout. Resolved: apt is the only update path; Odoo from git becomes a Keel-maintained package (built from the git mirror at a fixed revision, carrying the Odoo-only wheels, post-install hook runs the module update).
First packages this requires: Coraza (no package, no ITP), Anubis (ITP #1102132; upstream .deb v1.27.0), Garage (ITP #1118368), possibly a current CrowdSec (trixie 1.4.6-10, upstream 1.8.1), and Odoo. Anubis and Garage are candidates to contribute to Debian via tracker#15.

First tasks

Track field in the spec (stable/testing) converged into the apt sources.
One overlay shipped as a .deb end to end (see 0036).

**Decision (maintainer, 2026-09-30).** Everything Keel installs is a .deb in the Keel repository, overlays included; `apt upgrade` is the only update mechanism. Application packages carry a post-install migration hook (Odoo module update, Mastodon `db:migrate`). Mesh-aware ordering: a database primary never upgrades while primary; it hands over, upgrades, returns after catch-up. Two tracks, stable and testing, declared in the YAML; simple defaults to stable with security-only unattended upgrades. The YAML is re-emitted after every upgrade. **Handbook:** `docs/decisions/0039-upgrades-from-the-keel-repository.md` (handbook#26) **Amends:** 0016 (tracks share the channels' two names; a third is a decision), 0012 (unchanged, the pool builds the repository), 0020 (upgrade order becomes handover and return after catch-up), 0022 (superseded on how Odoo is updated). **Review notes** (resolved by the maintainer, 2026-09-30) - [x] 0022 upgrades Odoo by moving a git checkout. Resolved: apt is the only update path; Odoo from git becomes a Keel-maintained package (built from the git mirror at a fixed revision, carrying the Odoo-only wheels, post-install hook runs the module update). - [x] First packages this requires: Coraza (no package, no ITP), Anubis (ITP #1102132; upstream .deb v1.27.0), Garage (ITP #1118368), possibly a current CrowdSec (trixie 1.4.6-10, upstream 1.8.1), and Odoo. Anubis and Garage are candidates to contribute to Debian via tracker#15. **First tasks** - [ ] Track field in the spec (`stable`/`testing`) converged into the apt sources. - [ ] One overlay shipped as a .deb end to end (see 0036).