From: seventh guardian <seventhguardian@gmail.com>
Date: Sun, 06 Apr 2008 16:22:39 GMT
Subject: Re: [bug] git-clone over ssh fails when repository has local commits
Message-ID: <1caff7430804060922seba4978qa13b123103b8282b@mail.gmail.com>
In-Reply-To: <20080406161120.GB24358@coredump.intra.peff.net>

On Sun, Apr 6, 2008 at 5:11 PM, Jeff King <peff@peff.net> wrote:
> On Sun, Apr 06, 2008 at 02:45:22PM +0100, seventh guardian wrote:
>
>  >  $ git-clone ssh://<host>/<path>
>  > Initialized empty Git repository in <path>/.git/
>  > Password:
>  > remote: Counting objects: 132468, done.
>  > remote: Compressing objects: 100% (25543/25543), done.
>  > remote: Total 132468 (delta 107355), reused 130574 (delta 105466)
>  > Receiving objects: 100% (132468/132468), 42.12 MiB | 4161 KiB/s, done.
>  > Resolving deltas: 100% (107355/107355), done.
>  > error: Trying to write ref REMOTE_HEAD with nonexistant object
>  > f7a51afd56964cb0f10178353315d2680832ea54
>  > fatal: Cannot update the ref 'REMOTE_HEAD'.
>  > Warning: Remote HEAD refers to nonexistent ref, unable to checkout.
>
>  It sounds like your remote repository has a bogus HEAD that points to a
>  non-existent object. Can you ssh to <host> and confirm that you can do a
>  "git show HEAD" in the remote repo?

I can, but it is a local commit. It seems like local commits aren't
being "cloned over" to the slaves.. As I said, this only happens for
"local masters" where I have local commits. If my master is untouched,
then I can successfuly clone the repo.

Thanks,
  Renato