README.md: add koji untag
to releasever bump SOP
#432
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We encountered this this morning: FCOS f30 signed packages were garbage
collected (even though the Koji builds themselves were not since they're
tagged in the pool), and this caused the
distRepo
task to fail becauseit expects the signed packages to be there.
Ideally, we'd have proper GC for pool packages in place, but for now
let's add a step there to untag packages from the
N-2
release. Thisinterestingly does put a natural upper bound on how long to keep
packages; until the release in which it shipped goes EOL, which I think
is completely reasonable.