From: Jakub Narebski <jnareb@gmail.com>
To: "Elijah Newren" <newren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Unable to clone an ssh repository (with ugly installation-specific workaround)
Date: Tue, 12 Feb 2008 00:16:11 -0800 (PST) [thread overview]
Message-ID: <m31w7iegk6.fsf@localhost.localdomain> (raw)
In-Reply-To: <51419b2c0802111822k4600e06bp4167a09b30bf947a@mail.gmail.com>
"Elijah Newren" <newren@gmail.com> writes:
> 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
next prev parent reply other threads:[~2008-02-12 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 2:22 Unable to clone an ssh repository (with ugly installation-specific workaround) Elijah Newren
2008-02-12 7:04 ` David Symonds
2008-02-12 8:16 ` Jakub Narebski [this message]
2008-02-12 8:37 ` Johannes Sixt
2008-02-12 10:30 ` Johannes Schindelin
2008-02-12 11:28 ` [PATCH] upload-pack: Initialize the exec-path Johannes Sixt
2008-02-12 11:49 ` Johannes Schindelin
2008-02-12 12:45 ` Johannes Schindelin
2008-02-13 13:00 ` Elijah Newren
2008-02-13 12:57 ` Unable to clone an ssh repository (with ugly installation-specific workaround) Elijah Newren
2008-02-13 14:17 ` Stephen Sinclair
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31w7iegk6.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).