Add design spec for pungi autopatching #20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "autopatch-design"
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?
Summary
This PR adds a design spec for automating how AlmaLinux maintains its pungi fork. It is a design document only; no code changes.
Today the fork mixes the upstream code, the Fedora spec, and AlmaLinux changes in one tree, and updates are cherry-picked by hand. The spec proposes:
alma/<Version>(the upstream tag plus one commit per patch) and are exported withgit format-patch.config.yamlfor autopatch-tool, kept in a newautopatch/pungirepository.rpms/pungimain. It rebases the patches, applies the spec changes, runsrpmbuild -baon EL8/9/10, and opens a single PR against a newrpms/pungidist-git repository.pungi-4.10.1. Acceptance is an empty code diff against the currentmaster.Also noted: upstream moved from pagure.io to
forge.fedoraproject.org/pungi/pungiin 4.14.0.Out of scope for this stage: building in ALBS, runner provisioning, and reviewing the AlmaLinux modifications.
Spec:
docs/superpowers/specs/2026-09-29-pungi-autopatch-design.md🤖 Generated with Claude Code