Repository navigation
bootc: Reduce the Fedora packit karma window to 3 days (#2335) #310
Description
Repo: bootc-dev/bootc
Task: bootc-dev/bootc#2335. Updates keep obsoleting each other because the weekly release cadence conflicts with Bodhi's default 7-day karma wait. In .packit.yaml set the Fedora Bodhi update to the 3-day window the issue asks for, using whatever key packit documents for this (verify against https://packit.dev/docs/configuration/upstream/bodhi_update; do not guess a key name) and leave the COPR targets alone.
Acceptance: the file validates (packit validate-config if available, else a YAML parse plus a check against the documented key); explain the key you used in the commit message.
Constraints: code and tests only, no GitHub writes (the coordinator opens the PR); keep the change small and match the surrounding style; commit message in the project's style with a Generated-by: AI trailer, no Signed-off-by.
Generated-by: https://github.com/cgwalters/#llms
Activity
cgwalters-bot commentedon Oct 22, 2026
✅ dispatch ended well. Result: #310 (comment)
cgwalters-bot commentedon Oct 22, 2026
Triage: obsolete as written; recommend closing as not planned. The requested change would do nothing, and the part that can be changed already shipped in bootc-dev/bootc#2362.
bodhi_extra_paramsto Bodhi unchanged (packit/api.py,package_config.bodhi_extra_params | {"type": ...}). The Bodhi key would bestable_days, but Bodhi raises anystable_daysbelow the release'smandatory_days_in_testingback up to that minimum (bodhi models.py, "make sure that the value of stable_days will not be lower than the mandatory_days_in_testing"). Bodhi's API shows that minimum is 7 days for every current Fedora release (F43/F44: 7, or 14 for critpath). So settingstable_days: 3in.packit.yamlwould just be raised back to 7.bodhi_extra_params: {stable_karma: 1}on thebodhi_updatejob (.packit.yaml on main). With that, one +1 pushes an update to stable before the 7 days are up. Recent Bodhi updates confirm it applies: the F43/F44 bootc updates (for example FEDORA-2026-29abd0c1f9 and FEDORA-2026-d02b8572eb) showstable_karma 1, stable_days 7. They got 0 karma and went stable on the 7-day timer.Unclear: bootc-dev/bootc#2335 is still open even though #2362 fixed it in practice. cgwalters may want to close it with a pointer to #2362. Note that F45's update FEDORA-2026-6c8c8a543a has been in
testingsince 2026-10-08, probably held by the branched-release freeze rather than karma.I can't close items in this run, so the close is left to the operator.