In https://pagure.io/releng/fedora-scm-requests/issue/79101 @ksurma requested "initial_commit": false. But the releng-bot account happily committed https://src.fedoraproject.org/rpms/python3.15/c/734bbd88f74d7a474c0280f3ceeb38fca7f5a2ea?branch=rawhide -- which we now cannot get rid of. This should not have happened.
"initial_commit": false
Please:
If at all possible, remove that branch and commit so we can import the git history of python3.14 instead, as desired.
When do you need this? (YYYY/MM/DD)
Investigate on your own schedule. Removing the branch should ideally right now (if approved).
When we abandon the fedora-scm-requests approach.
Unexpected commits that are not removable.
Thanks.
Closing it because its duplicated here https://pagure.io/fedora-infra/toddlers/issue/362
Metadata Update from @phsmoura: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
The investigation part is duplicated but we need the repository fixed :(
Could you do that?
Metadata Update from @churchyard: - Issue status updated to: Open (was: Closed)
Context: We would really like to push the git history of python3.14 to the repository as is (not a merge commit, not rebased), and not resolving this is blocking us to actually ship Python 3.15.0a1 for Fedora. If we are told that this absolutely cannot be undone, we will use a merge commit that deletes the README we did not want, but we would like a resolution soon. Thanks
Could we please get that branch removed so we can recreate it with python3.14 git history?
Metadata Update from @james: - Issue tagged with: low-gain, low-trouble
We're not sure how bad pague will take it if there is no branch at all, so deleting the branch might make it unhappy (at least until you push the new one).
how bad it would be to just remove the entire project and re-request it?
If it'd be too bad, then maybe speak to kevin/nirik on matrix when he has some free time and then the project will be branch free for a minimal amount of time.
That will work fine, as it did with other projects where "initial_commit": false worked.
Works for us, but we cannot re-request it without the fix deployed first.
The repo has no branch now. You should be able to push the new branch, and the main admin will ned to set an alias to rawhide.
Thanks. Pushed, alias created.
Metadata Update from @churchyard: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.