I think the current list dates from when chunkah was just released and
only living in Rawhide and the latest stable. Nowadays it's in all
active releases.
This also catches unreleased branched Fedora releases (e.g. Fedora 45
right now), which we really should be testing.
Ref: https://packit.dev/docs/configuration#aliases
Packit defaults to `git describe` for the project version. So when
cutting a release, on PRs where we're bumping the chunkah version in
`Cargo.toml`, we get a mismatch: `create-archives.sh` reads the version
from `Cargo.toml` (e.g. 0.3.0), but `PACKIT_PROJECT_VERSION` resolved to
0.2.0 from the last tag, so `fix-spec-file` referenced a vendor tarball
that didn't exist.
Add a `get-current-version` action that reads the version from
`Cargo.toml` via `cargo metadata`, keeping `PACKIT_PROJECT_VERSION`
consistent with the archives that `create-archives.sh` produces.
Assisted-by: OpenCode (Claude Opus 4.6)
Add a `copr_build` job to build RPMs in COPR on every PR for
early packaging feedback. The create-archive action calls
`tools/create-archives.sh`, a new shared script that generates source
and vendor tarballs from the current tree. `release.py` is updated to
use the same script, deduplicating the archive creation logic.
While we're here, tweak the vendor-filterer invocation to match bootc
(add `--tier 2` and use `*-unknown-linux-gnu` glob).
Closes: #59
Assisted-by: Claude Opus 4.6
Set up Packit here and downstream so that everything happens
automagically when we cut a release upstream.
Move canonical spec file from downstream to upstream. Switch to
`%autochangelog`.
