2009/11/1 Jeremy Aston <jeremy.aston_at_realitylogic.com>:
>> Hi,
>>
>> I know this topic has been mentioned several times over the years on
>> the list but it does not appear that the problem has been fully
>> solved.
>>
>> I regularly have problems committing files (typically binary files
>> of 2 or more MB) to my repository as I keep getting errors such as
>> the following:
>>
>> Commit failed (details follow):
>> Checksum mishmatch, file: 'some file':
>> expected: e42d35e8e05762e7585aff281d2e8c1f
>> Actual: b57111e7f6c531daf0868f30d202f00e
>>
>> These errors sometimes occur on files that have been in the
>> repository for a while but I notice them alot with files that have
>> not even been committed yet.
>>
>> I have seen the various solutions such as hacking the svn local
>> files and copying the file to a temp file, rechecking out the
>> original and over writing the repo copy with the local temp file but
>> that cannot work with a file that has not even be committed as yet.
>>
>> These are workarounds, not solutions and I am seeing this all the
>> time and is rendering svn a massive pain to use. I've upgraded to
>> the latest version and am still seeing the problem.
>>
>> Does anyone have a proper solution or reason why this happening?
>>
>> Best regards
>>
>> jez
>>
>
> Just wondering if anyone has any comments on this? I am getting
> increasingly frustrated with this as I work with alot of binary files
> (CAD drawings etc.) and am hitting it all the time. Doing these work
> arounds is simply not a long term option for productivity.
>
> Would a move from FSFS to Berkeley make any difference?
>
> Would a move from FSFS to Berkeley make any difference?
I'm sure it won't.
>> Checksum mishmatch, file: 'some file':
>> expected: e42d35e8e05762e7585aff281d2e8c1f
>> Actual: b57111e7f6c531daf0868f30d202f00e
Just wondering:
If you know, what the file it was,
if you independently calculate md5sum for that 'some file', what will
be the value?
Do you have:
a) on the server: pre-commit hooks, that try modify the file before the commit?
b) proxies
c) on you local PC: something, that modifies the *.svn-base files?
Is the error reproducible?
Best regards,
Konstantin Kolinko
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2413483
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-01 19:48:11 CET