fedpkg request-repo now creates request tickets with "branch: rawhide" and those are not understood by fedscm-admin yet (it thinks they are a modular branch lacking "scl" field).
Rather than revert the change in fedpkg again, wait for updates to get pushed out to users, and changing the default to "rawhide" again a few days later, can fedscm-admin mangle those requests on the "server side" by replacing "rawhide" with "master" until the switch is officially made?
It is related to fedpkg patch that was already released for rawhide and f33: https://pagure.io/fedpkg/pull-request/424 I am sorry, I released it earlier than I was sure it is safe.
@onosek I should have warned you about releasing it, we were thinking of creating a freeze to test the entire flow and then making the switch official. Right now, I think I should make the patch to make the fedscm-admin think when they request rawhide branch, ask it to create master branch and we will remove the patch when we make the official switch.
rawhide
master
@mohanboddu Thanks, this solution seems reasonable to me in the situation. Again, I am sorry for being too initiative this time.
Metadata Update from @humaton: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.