[Monotone-devel] Problem detected by 'db check'

[Julio M. Merino Vidal]

Hi all,

I've just started the migration to 0.17.  After following the UPGRADE
document posted to the website, I still get this output from 'db check':

[sun tmp] $ monotone --db=monotone.db db check 2>&1 | tee db-check.log
monotone: [files: 362] 
monotone: [manifests: 75] 
monotone: [revisions: 75] 
monotone: [ancestry: 76]  
monotone: [revisions: 1] 
monotone: verifying new revisions (this may take a while)
monotone: [revisions: 75] 
monotone: [keys: 3]       
monotone: [certs: 302] 
monotone: revision 45cb6b87d27209c30b27685ae9064daa04c8b0dd mismatched
certs (2 authors 2 dates 1 changelogs)
monotone: warning: 1 mismatched certs
monotone: check complete: 362 files; 75 manifests; 75 revisions; 3 keys;
302 certs; 1 problems detected

I remember which revision is that, and how it was created.  It's a merge
that was issued by me and another developer.  In fact, here is its log:

Revision: 45cb6b87d27209c30b27685ae9064daa04c8b0dd
Ancestor: 0993ebf21897c22999199c4d33b3d7cd95d77892
Ancestor: 7c5b7534131b706500da0417e0bf69d27cb3599d
Author: address@hidden
Author: address@hidden
Date: 2004-12-25T19:40:40
Date: 2004-12-25T19:37:49
Branch: net.sourceforge.vigipac.src

Added files:
        .mt-attrs
Modified files:
        admin/clean-all.sh

ChangeLog: 

merge of 0993ebf21897c22999199c4d33b3d7cd95d77892
     and 7c5b7534131b706500da0417e0bf69d27cb3599d

Is db check really detecting a problem in the database?  Or is this just
a false positive?

As I see it, there are no problems with this "duplicate" merge.  And,
FWIW, everything seems to be working fine.

Thanks,

PS: Sorry if I overlooked something from UPGRADE, but I don't think so.

-- 
Julio M. Merino Vidal <address@hidden>
http://www.livejournal.com/users/jmmv/
The NetBSD Project - http://www.NetBSD.org/