{ "action": "new_branch", "branch": "el6", "namespace": "rpms", "repo": "python3-gssapi", "create_git_branch": true }
The branch in PDC already exists
Metadata Update from @limb: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
No it doesn't?
rharwood@seton:~/python3-gssapi.epel $ fedpkg pull Already up to date. rharwood@seton:~/python3-gssapi.epel $ git branch -va * epel7 935a899 Initial import remotes/origin/HEAD -> origin/master remotes/origin/epel7 935a899 Initial import remotes/origin/master fba82bf Added the README rharwood@seton:~/python3-gssapi.epel $
Metadata Update from @rharwood: - Issue status updated to: Open (was: Closed)
It is utterly unhelpful it is to close the bug again with the same message as before. Clearly I didn't understand whatever you were trying to say then, so why would repeating it be different? If I'm doing this wrong tell me what to do instead so I stop bothering you.
Here is the official Fedora documentation I'm working from (step 10): https://fedoraproject.org/wiki/New_package_process_for_existing_contributors
Here is my package's repo: https://src.fedoraproject.org/rpms/python3-gssapi
Please note the lack of el6 branch. This means I cannot build for el6. See:
rharwood@seton:~/python3-gssapi.epel $ fedpkg switch-branch el6 Could not execute switch_branch: Unknown remote branch origin/el6
Apologies, I didn't see the comment. It would appear that the branch was created in PDC but not in git.
@pingou ?
Closing to keep it out of the queue.
Metadata Update from @limb: - Issue status updated to: Closed (was: Open)
If the branch exists in PDC, you can safely create it in your git repository from whichever commit you want to branch and just push it. From there it's business as usual :)
Login to comment on this ticket.