= phenomenon = I cannot push to the Virtualization Guide git (ssh://git.fedorahosted.org/git/Virtualization_Guide.git). I have followed the recommendations in the FAQ (https://fedorahosted.org/web/faq) and asked several people in #fedora and #fedora-admin for help and advice.
= reason = I've marked this as a blocker because it is preventing contributions to this project and if I cannot resolve this issue this week I will miss F12 release.
Presently I cannot get past these errors: error: src refspec master does not match any. fatal: The remote end hung up unexpectedly error: failed to push some refs to 'ssh://tsagadai@git.fedorahosted.org/git/Virtualization_Guide.git'
I've tried everything I know with regards to this and I haven't come up with any solutions. I don't understand what crazy method is being used to host git on fedorahosted, but it's nothing I know. Usually you just created/copy a repo to the server and set the git-daemon-export-ok file. Can you do this for me so I can actually just commit.
= recommendation = Can the repo be reset and initialized fully? I really don't care if anyone else gets commit access to it in order to configure a blank repo as long as I can commit to it. All I want is the ability to clone it and start pushing (this should be a really simple git-init action).
Hi Chris,
It looks to me like you need to push a master branch to the repo, as mentioned in the Fedora Hosted FAQ¹:
'''I just got a new git repository, how can I push/pull?'''
Before anyone can clone/push the new repository a master push must be done with the command (from your local git repo): git push ssh://git.fedorahosted.org/git/yourproject.git/ master
(If you have defined a remote for fedorahosted in y our local git repo, you can use that name instead of the full ssh://... URL.)
Can you try that and let us know if it solves your problem?
¹ https://fedorahosted.org/web/faq
Chris, some other potentially useful information would be the output of "git branch -a" in your local repository, as well as the .git/config file.
I followed up with Chris, for some reason the bare repo wasn't init'ed properly and was busted. As it was empty, I've replaced it with a new clean init.
Weird, I remember setting up this repo (one of the first ones I did), although I followed the SOP... maybe I messed up somehow? was the directory empty or the git stuff was messed up?
Login to comment on this ticket.