Re: [Monotone-devel] ANNOUNCE: monotone 0.20

[Nathaniel Smith]

On Thu, Jul 07, 2005 at 06:25:16PM +0200, Florian Weimer wrote:
> > Florian Weimer schrieb:
> >> With monotone at manifest d538000d4a53ebe2c9b275cb30639aeba22f9e80, I
> >> get the following error message when I try to run "monotone pull":
> >> 
> >> monotone: warning: caught bad_decode exception decoding input from
> >> peer venge.net: 'bad checksum 0xde836079 vs. 0x122b5343'
> >
> > Try to download 0.20, compile it, sync into your existing database and
> > update. I don't know what caused this either, but the bug does not occur
> > if you use 0.20+ against the server.
> 
> I think d538000d4a53ebe2c9b275cb30639aeba22f9e80 *is* 0.20.

0.20 seems to have manifest '5ce921ee9229c7e7f2f07d77c67de1feee633351'
(with debian fixes) or 'c67739c93ce43bb667ab86507556dd5ea79c8b5f'
(without debian fixes).  We never use manifests to refer to things,
though, so I don't really have any way to figure out, given your
manifest, what you're actually looking at...

Probably you are using some pre-0.20 version from mainline; it would
have an incompatible protocol, but not notice, because all the
in-development versions have the same protocol versioning stuff.  Then
when it starts misinterpreting packets, it would get a checksum error.

-- Nathaniel

-- 
Eternity is very long, especially towards the end.
  -- Woody Allen