Learn more about these different git repos.
Other Git URLs
In the last time there have been at least two builds, that broke the Rawhide buildroot entirely. The usual way to fix this is to untag the problematic NEVR of that package and to rebuild the package after fixing it.
NEVR
Before autosign was fully implemented, the package owner / maintainer and provenpackagers could untag builds themselves from the fXX tag. Today there is always intervention from someone having Koji-admin powers involved, which may result in a broken Rawhide buildroot for a longer period.
fXX
That should not be hard to implement, as builds can still be tagged and untagged from the fXX-pending tag by the package owner / maintainers and provenpackagers.
fXX-pending
CC: @tmraz and @cverna
well the tag/untag ACL is one and the same, people can tag in by tagging onto -pending which will go through the signing queue first. This is no different that people not being able to untag from the stable releases, the general rule is for a packager to fix/bump and rebuild.
To just provide untag capability will require koji enhancements which doesn't really come into the "not too hard to implement" category.
There's a simple workaround for this issue:
tag the previous/older/working version of the package into f30-pending. Autosign will check it and sign it, and then move it to f30. Since koji just uses the last tagged, it will then use this version.
No changes needed (well, perhaps documentation? but where?)
Metadata Update from @syeghiay: - Issue tagged with: docs
Metadata Update from @syeghiay: - Issue assigned to mohanboddu
Assigned to @mohanboddu to document the work around.
Hi @siddharthvipul1
We found a job for you :)
Seeing as how you are interested in release engineering and will be reading the the updates policy, , would you mind adding a new section to the updates policy on how to untag builds https://fedoraproject.org/wiki/Updates_Policy
Thank you kindly! Aoife
tag the previous/older/working version of the package into f30-pending...
with rawhide gating, I think this no longer works
Note that untagging packages after that went to a compose should be prohibited. So probably there should be tag out or something similar which will not allow package to be untagged in any ways (except of admin using --force option). Moreover, the bodhi will not allow you to push same version afterwards, so you will need to do some very hackish koji tag-build actions or make a new rebuild (which is not always trivial).
out
koji tag-build
So think twice before going right away to implementing this instead of trying to come up with set of rules you want to implement here in the ticket, discuss that and only after that going to implementation.
Just my $0.2.
We are not going to allow untagging, we will be testing how gating reacts when we tag old builds and update the documentation.
Metadata Update from @cverna: - Assignee reset
Since its not possible to self service this ticket right now and its not that common, please file a ticket with releng and we will untag it for them.
Sorry for the trouble.
Metadata Update from @mohanboddu: - Issue close_status updated to: Can't Fix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.