On 1/18/16, Ben Ventura <[email protected]> wrote:
>
> Hello,
>
> We’ve been running fossil on Ubuntu 14.04 for about a year; all of a sudden
> a problem has cropped up where it gives this message when attempting ‘fossil
> update':
>
> "content does not match sha1 hash"
>
> We get it on everyone’s workspace when they try to run “fossil update”, and
> the update fails.
>
> This is my fossil version:
>
> "This is fossil version 1.30 [1df1b41c86] 2015-01-19 11:29:00 UTC"
>
> Any ideas? I tried rebuilding “fossil rebuild” on client and server but no
> effect.
>
The fossil server itself is running 1.35. I not aware of any problems
like yours that have been fixed, but you never know and upgrading
won't hurt.
Please try running (on the server):
fossil test-integrity
fossil rebuild
The error you are seeing
(https://www.fossil-scm.org/fossil/artifact/360b9fb86?ln=196) comes
about because the server sent a message to the client that says "here
is the data for artifact S" (where S is a SHA1 hash). Then after the
data is received it has some other hash X. The client rightly rejects
this artifact.
The question at hand is why it is getting the wrong hash. Let's see
if the "test-integrity" on the server provides a clue before we get
into too much speculation.
--
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
