[Sugar-devel] Setting public key - gitorious

[James Simmons]

Art,

When git tells you it "failed to push some refs" that generally means
that the remote repository has some changes that are not in your local
repository.  Do a "git pull" to get these changes brought in, have a
look at the files it changed to make sure the changes didn't hurt
anything (and if they did, fix it) then do your "git push".

There is a chapter on using Git in my "Making Sugar Activities" book.
It may be helpful to you, and if it isn't your comments on what was
missing would be helpful to me:

http://objavi.flossmanuals.net/books/ActivitiesGuideSugar-en-2010.02.15-18.18.25.pdf

It covers a lot of what you've just been through.

James Simmons


> Date: Thu, 18 Feb 2010 18:59:31 -0500
> From: "Art Hunkins" <abhunkin at uncg.edu>
> Subject: Re: [Sugar-devel] Setting public key - gitorious
> To: "Aleksey Lim" <alsroot at member.fsf.org>
> Cc: Sugar-devel at lists.sugarlabs.org
> Message-ID: <8E06D06946EE4ECAB2A72FB0C37C0590 at Art>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>        reply-type=original
>
> I did the "initial commit" with these results (similar to what I got
> before):
>
> [olpc at xo-05-25-69 ~]$ cd Activities/OurMusic.activity
> [olpc at xo-05-25-69 OurMusic.activity]$ git remote add origin
> gitorious at git.sugarlabs.org:our-music/mainline.git
> [olpc at xo-05-25-69 OurMusic.activity]$ git push origin master
> error: src refspec master does not match any.
> fatal: The remote end hung up unexpectedly
> error: failed to push some refs to
> 'gitorious at git.sugarlabs.org:our-music/mainline.git'
>
> Is the problem perhaps that this is not an "initial commit"? I think I've
> studied all available sugarlabs materials about git; unfortunately, Linux
> terminology is still largely a foreign language to me, and I often don't
> understand what's being said. (Sorry to be so unenlightened.)
>
> Art Hunkins