Re: [Monotone-devel] Re: trouble using ssh transport

[hendrik]

On Thu, Mar 12, 2009 at 06:10:29PM +0100, Lapo Luchini wrote:
> address@hidden wrote:
> >
> > sh-3.1$ mtn --version
> > monotone 0.31 (base revision: 1bd1fe1e811dce82bee09b9f0effca3225bd1cee)
> > address@hidden:~$ mtn --version
> > monotone 0.40 (base revision: 5ccc279f9dea0444b47f03dd5291ecc985fcb7f6)
> 
> It's quite possible that command line to launch a serve command changed
> somewhere in between those revisions, so the old client tries to spawn
> the new server with a command line the server doesn't understand.

Thanks for confirming that I'm not crazy.  ;-)

> 
> > Any advice?  I suppose I could manually start 'mtn serve' on the server, 
> > and then use netsync, but it would be less convenient.  And *I'd like to 
> > learn how the ssh transport is supposed to work.
> 
> It's supposed to work that way.
> 
> Netsync itself (the communication protocol) is quite stable and, other
> than being able to spawn the remote ssh server, those two revision can
> certainly talk to each other... so if you "mtn serve" manually they will
> most probably work.

I tried it.  It did.

> 
> > I'm reluctant to install an non-etch monotone on this machine unless 
> > it's really necessary, because it's not mine.
> 
> You could use a static binary in your home just for the time needed...

Manually doing the serve will do for now.  I'll work on a better way 
(with an up-to-date monotone) when I get my own laptop.

-- hendrik