Re: [Monotone-devel] disturbing errors from 'mtn db check' on monotone repo

[Timothy Brownawell]

On Fri, 2006-07-14 at 21:31 -0700, Zack Weinberg wrote:
> Debian just picked up monotone 0.27, so I thought it would be good to
> run db check over my local repository.  It spewed errors at me, e.g.
> 
> mtn: revision 0b09ae42e28165400b8023880c3efca0863a7d87 missing branch cert

This *could* be considered a problem, but it isn't a big deal. You
apparently pulled "net.venge.monotone*", but some branches in that have
ancestors in other branches that aren't included. The way we do things
currently, this means that you didn't get those branch certs. So, not a
big deal. But this does mean that those revisions are pretty much
"invisible", which could be a problem if you actually cared about them.

> mtn: revision 0b4ab5e89dac3e62efa3174c2b2294222eae91e6 mismatched
> certs (1 authors 2 dates 1 changelogs)

There are various (legitimate) ways this can happen. Mostly this
involves different people doing the same merge and getting the same
result.

> How much should I worry?  Should I try to fix it, and if so, how?
> There's nothing in UPGRADE or NEWS about this.

Don't worry. If anything, this means that "db check" reports too many
things as errors.

Tim