repository integrity(?) problem
Matt Mackall
mpm at selenic.com
Mon Sep 14 12:15:11 CDT 2009
On Mon, 2009-09-14 at 17:16 +0200, Berkes Adam wrote:
> I moved a repository from one linux server (Ubuntu 8.04) to another
> (tar.gz) and on the destination (SuSE 9.1) side an integrity exception
> thrown when walking through the repository. On both machine Mercurial
> 1.3.1 were used (no exception on source machine). The specific
> circumstance is that I have to build both python and mercurial from
> source (standard make/make install way): python raised a warning about
> _ctypes, but apart from that there were no mentionable problem. What is
> really unclear is that if I run the same command (below) with exact -r
> parameter there is no any problem (I checked some revisions around the
> mentioned one). Here is my traceback:
>
> hg --traceback --time -R ~/repository/hg/dev-hg --encoding UTF-8 log --style ~/log.style >log.out
Please run hg verify on both machines and also confirm that
the .hg/store/00manifest.* files on each side are identical.
If they're not, you may be a victim of cosmic rays:
http://lwn.net/Articles/219983/
--
http://selenic.com : development and support for Mercurial and Linux
More information about the Mercurial-devel
mailing list