Apply correct tags upon signing rawhide updates #5857
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mattiaverga
force-pushed
the
tags-activation_point
branch
4 times, most recently
from
0c0077a to
e272a9b
Compare
Signed-off-by: Mattia Verga <[email protected]>
mattiaverga
force-pushed
the
tags-activation_point
branch
from
e272a9b to
eae84fa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I believe moving rawhide/branched builds from pending_testing to testing tag could solve stuck updates after bodhi activation point and fix #5830
This would introduce some more load on Koji, though, which is usefulness for 99%... but guarantees tags consistency.