False integrity errors?

[Guy Brand]

Hello,


On a few repositories, various sizes and histories, I see strange
errors when verifying them. These errors do not exist with version
1.0.1 of mercurial. A typical example is:

    bug ~/rbt# hg version
    Mercurial Distributed SCM (version 1.0.1)

    Copyright (C) 2005-2008 Matt Mackall <mpm at selenic.com> and others
    This is free software; see the source for copying conditions. There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    bug ~/rbt# hg verify             
    checking changesets
    checking manifests
    crosschecking files in changesets and manifests
    checking files
    23 files, 19 changesets, 46 total revisions

All ok, but with the current -devel revision:

    bug ~/rbt# hg version
    Mercurial Distributed SCM (version cbdfd08eabc9+20080726)

    Copyright (C) 2005-2008 Matt Mackall <mpm at selenic.com> and others
    This is free software; see the source for copying conditions. There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    bug ~/rbt# hg verify 
    checking changesets
    checking manifests
    crosschecking files in changesets and manifests
    checking files
     Makefile at 2: unpacked size is 863, 814 expected
     Makefile at 3: unpacked size is 741, 692 expected
     Makefile at 9: unpacked size is 754, 705 expected
     Makefile at 15: unpacked size is 741, 740 expected
     Makefile at 17: unpacked size is 724, 674 expected
     Makefile at 18: unpacked size is 577, 528 expected
     calendar.page at 3: unpacked size is 1839, 1763 expected
    ...
    23 files, 19 changesets, 46 total revisions
    39 integrity errors encountered!
    (first damaged changeset appears to be 0)

Bisecting the repository shows that the changeset which introduced
that behavior is:

    The first bad revision is:
    changeset:   6752:e79a8f36c2a5
    user:        Matt Mackall <mpm at selenic.com>
    date:        Thu Jun 26 14:35:50 2008 -0500
    summary:     verify: lots of refactoring

Anyone else observing that? Anything else to do to help debugging this
issue?

-- 
  bug