Error while pushing to Gitorious

[Rohith]

Hey,

I am getting the following error when I try to git push origin master

error: src refspec master does not match any.
fatal: The remote end hung up unexpectedly
error: failed to push to 'g...@gitorious.org:chutney-jabber-bot/
mainline.git'

My .git/config looks like this:

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = g...@gitorious.org:chutney-jabber-bot/mainline.git
fetch = +refs/heads/*:refs/remotes/origin/*



Any idea what that error means?

Thanks,
Rohith

[Rohith]

Whoops. This was caused by forgetting to do a initial

git commit

Once I did the initial commit, the git push worked fine.

On Feb 3, 3:02 am, Rohith <EntombedVi...@gmail.com> wrote:
> Hey,
>
> I am getting the following error when I try to git push origin master
>
> error: src refspec master does not match any.
> fatal: The remote end hung up unexpectedly

> error: failed to push to '...@gitorious.org:chutney-jabber-bot/

[Johan Sørensen]

Hi,

hmm, it sounds like you may not have a local master branch?

What does "git branch -a" say?

>
> Thanks,
> Rohith

Cheers,
JS

[Sebastian]

I get the exact same error:

> git push origin master

fatal: The remote end hung up unexpectedly

error: failed to push to 'git://gitorious.org/couchobject/sebastians-
mainline-clone.git'

While a git commit seemed to work for Rohith it doesn't do anything
for me as there isn't anything new to commit...

And to answer Johans questions:

> git branch -a

* master
origin/HEAD
origin/master

Any ideas?

Best regards
S

On Feb 3, 8:11 am, "Johan Sørensen" <jo...@johansorensen.com> wrote:
> Hi,
>

> On Feb 3, 2008 12:02 PM, Rohith <EntombedVi...@gmail.com> wrote:
>
>
>
>
>
> > Hey,
>
> > I am getting the following error when I try to git push origin master
>
> > error: src refspec master does not match any.
> > fatal: The remote end hung up unexpectedly

> > error: failed to push to '...@gitorious.org:chutney-jabber-bot/

[Sebastian]

I read somewhere on the web that one gets this error when trying to
commit using a SSH key when the repo address doesn't start with ssh!?
I changed it to ssh://gitorious.org/couchobject/sebastians-mainline-clone.git
and tried again, but was asked for a password... something seems to be
wrong. I have uploaded my SSH key, in case you wonder.

Any ideas? Suggestions?

S

[Johan Sørensen]

Hi,

On Feb 3, 2008 10:42 PM, Sebastian <sebastian....@gmail.com> wrote:
>
> I read somewhere on the web that one gets this error when trying to
> commit using a SSH key when the repo address doesn't start with ssh!?
> I changed it to ssh://gitorious.org/couchobject/sebastians-mainline-clone.git
> and tried again, but was asked for a password... something seems to be
> wrong. I have uploaded my SSH key, in case you wonder.

[snip]

> > fatal: The remote end hung up unexpectedly
> > error: failed to push to 'git://gitorious.org/couchobject/sebastians-
> > mainline-clone.git'

The git:// protocol (=git-daemon) is, in this case, for read-only
operations (pulling/cloning) only, you can change your
$PROJECT/.git/config file to read:
url = g...@gitorious.org:couchobject/sebastians-mainline-clone.git

The way Gitorious auths you is via the public ssh key(s) you provided,
hence the need to use the "git" user.

Hope that clears things up a bit?

JS

[Sebastian]

Thanks for the answer Johan.
It still doesn't work though for some reason.
It asks for a password now after I changed the origins url.

Best regards
Sebastian

[Sebastian]

Well... there seemed to be something wrong with my public SSH key. I
regenerated it, uploaded a new public key and then it worked.

S

On Feb 4, 8:18 am, Sebastian <sebastian.probst.e...@gmail.com> wrote:
> Thanks for the answer Johan.
> It still doesn't work though for some reason.
> It asks for a password now after I changed the origins url.
>
> Best regards
> Sebastian
>
> On Feb 3, 7:39 pm, "Johan Sørensen" <jo...@johansorensen.com> wrote:
>
> > Hi,
>

[Vinnl]

This thread is a bit old, but I just found it when looking for a
solution to this problem. Since it helped me solve it, I figured I'd
send this thankyou-email out. So here goes: thanks!
>
> JS