Learn more about these different git repos.
Other Git URLs
Hello,
Some weeks ago I built bunch of Rust packages for epel9-next (as I was assuming it's the way to go). Recently plans have changed and we should use epel9 instead, but as bootstrap is quite painful… would anybody help me to get those packages tagged in the epel9 buildroot so that I can just mass-bump specs and do the rebuild without having to bootstrap them once more?
Relevant question, is there way to drop them from epel9-next?
Maybe you are able to tag them to a epel9 side tag?
They can be untagged, but I guess the branch stays.
Hi @ignatenkobrain
so tagging *el9.next build into the epel9 build root is not really a great idea. But you can create a side tag and we can tag all the required builds into it for the rebuild and merge it back into epel9. Is that doable for you?
Metadata Update from @humaton: - Issue tagged with: low-gain, low-trouble, ops
In the end this is what I have done. Thanks :)
Metadata Update from @ignatenkobrain: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.