Re: [Monotone-devel] Mainline DB migration breaks server keys?

[Justin Patrin]

On Sun, Apr 6, 2008 at 1:11 AM, Richard Levitte <address@hidden> wrote:
> In message <address@hidden> on Sat, 5 Apr 2008 12:06:17 -0700, "Justin 
> Patrin" <address@hidden> said:
>
>  papercrane> I haven't been following recent developments too close but just 
> got a
>  papercrane> message to migrate my monotone DB using mainline. After backing 
> up my
>  papercrane> DB I migrated and attempted to pull again. Now I'm getting a 
> message
>  papercrane> about the server key changing:
>  papercrane>
>  papercrane> address@hidden ~/src/net.venge.monotone $ ./mtn pull && ./mtn up
>  papercrane> && make check
>  papercrane> mtn: doing anonymous pull; use -kKEYNAME if you need 
> authentication
>  papercrane> mtn: connecting to monotone.ca
>  papercrane> mtn: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>  papercrane> mtn: @ WARNING: SERVER IDENTIFICATION HAS CHANGED              @
>  papercrane> mtn: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>  papercrane> mtn: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY
>  papercrane> mtn: it is also possible that the server key has just been 
> changed
>  papercrane> mtn: remote host sent key 
> 3e6f5225bc2fffacbc20c9de37ff2dae1e20892e
>  papercrane> mtn: I expected
>  papercrane> 
> 33653666353232356263326666666163626332306339646533376666326461653165323038393265
>  papercrane> mtn: 'mtn unset known-servers monotone.ca' overrides this check
>  papercrane> mtn: error: server key changed
>  papercrane> address@hidden ~/src/net.venge.monotone $ ./mtn --version
>  papercrane> monotone 0.39 (base revision: 
> c4007197c145794b99ddaa2e6f7e2bc4c014714f)
>  papercrane>
>  papercrane> I tried pulling on my other machine with an older mainline mtn 
> and I
>  papercrane> didn't get any server key change messages and a quick search of
>  papercrane> monotone-devel doesn't show me any messages about the server key
>  papercrane> changing so I'm thinking the migration code did something 
> incorrect to
>  papercrane> the server key.
>
>  The migration code did nothing wrong, the bug is elsewhere, as has
>  already been shown.
>
>  You can fix this two ways, the first being this:
>
>  $ mtn unset known-servers monotone.ca
>
> $ ./mtn pull && ./mtn up && make check
>  $ mtn unset known-servers monotone.ca
>  $ ./mtn pull
>
>  At this point, everything should be fine.  When doing the pulls,
>  monotone should tell you that it got a new server key with the hash
>  3e6f5225bc2fffacbc20c9de37ff2dae1e20892e.
>

Yep, that's what I did. Thanks for the responses.

-- 
Justin Patrin