threads / discuss / 12031

Git over SSH

Subject: Git over SSH

## tl;dr

3 messages between Feb 11, 2008 and Feb 11, 2008.

replies: 2people: 3as markdown or json

Henrik Vendelbo· Feb 11, 2008, 12:38 UTC · lore

I seem to have missed something quite crucial. After many weeks of using git locally on two machines, I still haven't managed to synchronise over ssh.

I use Mac OS X Leopard on both and have no problem ssh'ing between them manually.

Why I try any of the examples in the documentation I always get a general failure with some command not being found. The last one missing was git-upload-pack. Thing is though from a shell logged in as the same user, I can execute git-upload-pack on both machine, np.

So is it MacPort of git that is somehow broken?

Thanks,

Henrik

Matthieu Moy· Feb 11, 2008, 12:45 UTC · re: Henrik Vendelbo · lore

Re: Git over SSH

"Henrik Vendelbo" <hvendelbo.dev@googlemail.com> writes:

> I seem to have missed something quite crucial. After many weeks of
> using git locally on two machines, I still haven't managed to
> synchronise over ssh.

Can you post a cut-and-paste of a shell session reproducing the error?

-- 
Matthieu

Jonathan del Strother· Feb 11, 2008, 12:47 UTC · re: Henrik Vendelbo · lore

Re: Git over SSH

On Feb 11, 2008 12:38 PM, Henrik Vendelbo <hvendelbo.dev@googlemail.com> wrote:

Show 13 quoted lines

> I seem to have missed something quite crucial. After many weeks of
> using git locally on two machines, I still haven't managed to
> synchronise over ssh.
>
> I use Mac OS X Leopard on both and have no problem ssh'ing between
> them manually.
>
> Why I try any of the examples in the documentation I always get a
> general failure with some command not being found.
> The last one missing was git-upload-pack. Thing is though from a shell
> logged in as the same user, I can execute git-upload-pack on both
> machine, np.
>

Interactive and non-interactive shells run different scripts on ssh login. The real test for whether your path is set up correctly for git over ssh would be "ssh othermachine type git", which will run 'type git' as a non-interactive command. You could try adding your path to .MacOSX/environment.plist, which will set things up for both interactive and non-interactive sessions.