ansaurus

Question

Git push origin master returns Error cannot spawn ... why?

Answer 1

+1 A:

That reminds me of issue 313, where GIT_SSH environment variable contains spaces in its path.

Other than that, did you followed the GitHub Help page and checking if your ssh connection worked?

$ ssh [email protected]
The authenticity of host 'github.com (207.97.227.239)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.
ERROR: Hi tekkub! You've successfully authenticated, but GitHub does not provide shell access
Connection to github.com closed.

VonC 2010-06-22 23:21:49

Yeah ive definitely checked that my ssh works correctly. as per the GitHub help page, and gotten the mesage:"Hi christopherdebeer! You've successfully authenticated but GitHub does not provide shell access"I'll look into "issue 313"...

Christopher 2010-06-23 06:23:37

Nope its is definitly not issue 313, my $GIT_SSH is set to "c:/putty/plink.exe"

Christopher 2010-06-23 06:29:09

@Christopher: How about not using `GIT_SSH` and plink.exe at all? I don't (on my Windows7 msysgit installation) and push just fine. What version of msysgit are you using by the way?

VonC 2010-06-23 07:22:27

@VonC I'll give it a go, I'm using 1.7.0.2 mysysgit

Christopher 2010-06-23 08:15:35

still no luck...

Christopher 2010-06-25 09:23:56

@Christopher: Then could you try changing the remote address from a git protocol to an https protocol, taking advantage from the smart http implementation proposed by GitHub? See http://stackoverflow.com/questions/2949128/git-push-problem-argh/2949418#2949418

VonC 2010-06-25 09:44:36

Answer 2

+1 A:

I'm not sure if it was just stupid of myself, but I've solved the problem... Here's what I did (from advice, from work colleagues):

I was attempting to push changes in a local repo to an empty repo on github...

what i should have done was clone the empty repo, add the files locally to my cloned repo, added the files, commited the adds, and THEN push to the github repo...

$ git clone [email protected]:christopherdebeer/yUML-Diagram.git
 // added files
$ git add *
$ git commit -m "first commit locally"
$ git push origin master

My original problems might have been due to my totaly naivety as to gits usage...

Christopher 2010-06-26 19:16:14

Strange, since you shouldn't be able to clone an empty repo: http://stackoverflow.com/questions/1298190/gitosis-and-git-clone-problem/1298224#1298224 and http://stackoverflow.com/questions/895819/whats-the-most-straightforward-way-to-clone-an-empty-bare-git-repository/895828#895828. See also http://support.github.com/discussions/repos/150-cannot-clone-an-empty-repo

VonC 2010-06-26 19:31:14

The advice that i recieved from a work colleague, (he doesnt use git at all, but does svn) ... when i mentioned my issues he recommended cloning the empty repo... as though it were common practice (if not for svn) then for him at least.

Christopher 2010-06-26 19:39:50

which is weird that you say it isnt possible... because it Definitly worked for me.

Christopher 2010-06-26 19:41:45

@VonC: Git 1.6.2 and later can “clone” empty repositories (i.e. setup the remote and a local master branch that will, eventually, track the remote master branch).

Chris Johnsen 2010-06-26 20:21:00

@Chris: very true. I need to update those old answers ;)

VonC 2010-06-26 20:33:13

ansaurus

tags:

views:

answers:

Git push origin master returns Error cannot spawn ... why?

related questions