On 08/09/2011 02:16 PM, Richard Hipp wrote:
> da39a3ee5e6b4b0d3255bfef95601890afd80709 is the hash for a zero-length
> object. Something is clearly messed up.
As a general rule of thumb, whenever mysteriously zero-length files crop
up, the first thing I check is whether anything's run out of dis
On Tue, Aug 9, 2011 at 9:05 AM, Marco Maggesi wrote:
> Thank you for your quick answer.
>
> I run test-integrity and I found that both repositories are corrupted.
> One says:
>
> fossil: checksum mismatch on blob rid=58:
> da39a3ee5e6b4b0d3255bfef95601890afd80709 vs
> 01f57728b3a5d55520becb489146d
Hi,
I found another copy of the same repository which is up to date and
doesn't have this inconsistency.
This solves my current problem.
BTW, these repositories are quite small (~120K).
If you think that they can be useful for debugging, I can send them to you.
Thank you for your support,
Marco
Thank you for your quick answer.
I run test-integrity and I found that both repositories are corrupted.
One says:
fossil: checksum mismatch on blob rid=58:
da39a3ee5e6b4b0d3255bfef95601890afd80709 vs
01f57728b3a5d55520becb489146d0a7f42f9638
The other says:
skip phantom 177 ccc986b41c2a37fb86a82
On Tue, Aug 9, 2011 at 8:25 AM, Marco Maggesi wrote:
> Hello,
>
> I have two fossil repositories (the "local" one and the "remote" one) and I
> get the following error when I try to pull:
> "content does not mach sha1 hash"
>
> So, first of all, I would like to establish if one or both repositori
Hello,
I have two fossil repositories (the "local" one and the "remote" one) and I get
the following error when I try to pull:
"content does not mach sha1 hash"
So, first of all, I would like to establish if one or both repositories are
corrupted.
Are there specific commands to check the integ
6 matches
Mail list logo
