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

[Justin Patrin]

I haven't been following recent developments too close but just got a
message to migrate my monotone DB using mainline. After backing up my
DB I migrated and attempted to pull again. Now I'm getting a message
about the server key changing:

address@hidden ~/src/net.venge.monotone $ ./mtn pull && ./mtn up
&& make check
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to monotone.ca
mtn: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
mtn: @ WARNING: SERVER IDENTIFICATION HAS CHANGED              @
mtn: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
mtn: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY
mtn: it is also possible that the server key has just been changed
mtn: remote host sent key 3e6f5225bc2fffacbc20c9de37ff2dae1e20892e
mtn: I expected
33653666353232356263326666666163626332306339646533376666326461653165323038393265
mtn: 'mtn unset known-servers monotone.ca' overrides this check
mtn: error: server key changed
address@hidden ~/src/net.venge.monotone $ ./mtn --version
monotone 0.39 (base revision: c4007197c145794b99ddaa2e6f7e2bc4c014714f)

I tried pulling on my other machine with an older mainline mtn and I
didn't get any server key change messages and a quick search of
monotone-devel doesn't show me any messages about the server key
changing so I'm thinking the migration code did something incorrect to
the server key.

-- 
Justin Patrin