Re: Unable to clone an ssh repository (with ugly installation-specific workaround)

From: Jakub Narebski <jnareb@gmail.com>
Date: Feb 12, 2008, 08:16 UTC
Message-ID: <m31w7iegk6.fsf@localhost.localdomain>
In-Reply-To: <51419b2c0802111822k4600e06bp4167a09b30bf947a@mail.gmail.com>

"Elijah Newren" <newren@gmail.com> writes:

Show 8 quoted lines

> I'm pretty sure this worked before, but with git-1.5.4, when trying to
> clone a repository via ssh from a machine that does not have git
> installed in a standard system path, I get the following:
> 
> $ git clone -u /home/enewren/software/install/linux/git/bin/git-upload-pack
> ssh://enewren@remote/var/scratch/enewren/votd
> Initialized empty Git repository in /home/newren/devel/votd/.git/
> remote: fatal: exec pack-objects failed.

git-pull(1)
[...]
       --upload-pack <upload-pack>
              When  given,  and  the  repository  to  fetch from is handled by
              git-fetch-pack, --exec=<upload-pack> is passed to the command to
              specify non-default path for the command run on the other end.

-- 
Jakub Narebski
Poland
ShadeHawk on #git