I had some problems today with git+ssh protocol. First, when using cg-clone, it couldn't execute cg-rpush, although it's there in /usr/local. Maybe that has something to do with that being added to the path in /etc/profile.
Second, I don't know how to specify the port number, the typical notation of git+ssh://xyz:port/repo didn't work.
Anybody knows what to do with these? SSH would be very useful for me if it worked right.
AstralStorm
Daniel BarkalowRe: SSH pull problems
On Sat, 4 Jun 2005, Radoslaw Szkodzinski wrote:
> I had some problems today with git+ssh protocol. > First, when using cg-clone, it couldn't execute cg-rpush, although it's > there in /usr/local. > Maybe that has something to do with that being added to the path in > /etc/profile.
I haven't used recent Cogito, so I'm not sure, but it might actually want git-rpush rather than cg-rpush? Or it might be a permissions issue?
> Second, I don't know how to specify the port number, > the typical notation of git+ssh://xyz:port/repo didn't work.
I haven't made it understand port numbers yet; it should be pretty easy, though, if you want to do it. You'd probably have a better chance of getting it right than I would, if you've got an SSH server on a non-default port to test against. Just parse out the part of "host" after the : and make it a "-p" option in the execlp in rsh.c.
-Daniel *This .sig left intentionally blank*
Re: SSH pull problems
Daniel Barkalow wrote:
>On Sat, 4 Jun 2005, Radoslaw Szkodzinski wrote: > > > >>I had some problems today with git+ssh protocol. >>First, when using cg-clone, it couldn't execute cg-rpush, although it's >>there in /usr/local. >>Maybe that has something to do with that being added to the path in >>/etc/profile. >> >> > >I haven't used recent Cogito, so I'm not sure, but it might actually want >git-rpush rather than cg-rpush? Or it might be a permissions issue? > > >
Make that git-rpush, I was writing from my memory, and it couldn't find it, as in "Command not found". It's available for all to exec, in /usr/local.
>>Second, I don't know how to specify the port number, >>the typical notation of git+ssh://xyz:port/repo didn't work. >> >> > >I haven't made it understand port numbers yet; it should be pretty easy, >though, if you want to do it. You'd probably have a better chance of >getting it right than I would, if you've got an SSH server on a >non-default port to test against. Just parse out the part of "host" after >the : and make it a "-p" option in the execlp in rsh.c. > > >
That's not a problem, I'll get to it in some short time and post a patch.
AstralStorm
Petr BaudisRe: SSH pull problems
Dear diary, on Sat, Jun 04, 2005 at 03:05:26PM CEST, I got a letter where Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl> told me that...
> I had some problems today with git+ssh protocol. > First, when using cg-clone, it couldn't execute cg-rpush, although it's > there in /usr/local. > Maybe that has something to do with that being added to the path in > /etc/profile. > > Second, I don't know how to specify the port number, > the typical notation of git+ssh://xyz:port/repo didn't work. > > Anybody knows what to do with these? > SSH would be very useful for me if it worked right.
If you are staying at the Cogito's tip, there was an incompatible protocol change introduced recently, so make sure you have the same Cogito version on both sides.
-- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
Re: SSH pull problems
Petr Baudis wrote:
>If you are staying at the Cogito's tip, there was an incompatible >protocol change introduced recently, so make sure you have the same >Cogito version on both sides. > >
I've updated both at the same time, just before the access. So this is impossible.
AstralStorm