svn checksum error
I tried "svn up" to bring my sandbox up-to-date and got this output: % svn up U Include/unicodeobject.h subversion/libsvn_wc/update_editor.c:1609: (apr_err=155017) svn: Checksum mismatch for 'Objects/.svn/text-base/unicodeobject.c.svn-base'; expected: '8611dc5f592e7cbc6070524a1437db9b', actual: '2d28838f2fec366fc58386728a48568e' What's that telling me? Thx, Skip
skip@pobox.com wrote:
I tried "svn up" to bring my sandbox up-to-date and got this output:
% svn up U Include/unicodeobject.h subversion/libsvn_wc/update_editor.c:1609: (apr_err=155017) svn: Checksum mismatch for 'Objects/.svn/text-base/unicodeobject.c.svn-base'; expected: '8611dc5f592e7cbc6070524a1437db9b', actual: '2d28838f2fec366fc58386728a48568e'
What's that telling me?
"welcome to the wonderful world of subversion error messages" (from what I can tell, the message means that SVN thinks that there might have been some checksum error somewhere, or some other error at a point where subversion thinks it's likely that a checksum was involved; to figure out what's really causing this problem, you probably need a debug build of subversion). deleting the offending directory and doing "svn up" is the easiest way to fix this. </F>
skip@pobox.com wrote:
I tried "svn up" to bring my sandbox up-to-date and got this output:
% svn up U Include/unicodeobject.h subversion/libsvn_wc/update_editor.c:1609: (apr_err=155017) svn: Checksum mismatch for 'Objects/.svn/text-base/unicodeobject.c.svn-base'; expected: '8611dc5f592e7cbc6070524a1437db9b', actual: '2d28838f2fec366fc58386728a48568e'
What's that telling me?
At the shallow level, the message should be clear: there is an actual checksum for a file and an expected checksum, and they differ. They shouldn't differ. Somewhat deeper, this indicates a bug in Subversion. It's not clear to me whether this is a client or a server bug. In the version on svn.python.org, the error message is on line 2846, so I would suspect it is a client bug. The natural question then is: what operating system, what subversion version are you using? Regards, Martin
Martin> The natural question then is: what operating system, what Martin> subversion version are you using? Sorry, wasn't thinking in terms of svn bugs. I was anticipating some sort of obvious pilot error. I am on Mac OSX 10.3.9, running svn 1.1.3 I built from source back in the May timeframe. Should I upgrade to 1.2.3 as a matter of course? Fredrik> "welcome to the wonderful world of subversion error messages" ... Fredrik> deleting the offending directory and doing "svn up" is the Fredrik> easiest way to fix this. Thanks. I zapped Objects. The next svn up complained about Misc. The next about Lib. After that, the next svn up ran to completion. Skip
Le dimanche 30 octobre 2005 à 19:08 -0600, skip@pobox.com a écrit :
Sorry, wasn't thinking in terms of svn bugs. I was anticipating some sort of obvious pilot error. I am on Mac OSX 10.3.9, running svn 1.1.3 I built from source back in the May timeframe. Should I upgrade to 1.2.3 as a matter of course?
IIRC, the version provided by Fink works fine. No need to compile manually.
skip@pobox.com wrote:
Martin> The natural question then is: what operating system, what Martin> subversion version are you using?
Sorry, wasn't thinking in terms of svn bugs. I was anticipating some sort of obvious pilot error. I am on Mac OSX 10.3.9, running svn 1.1.3 I built from source back in the May timeframe. Should I upgrade to 1.2.3 as a matter of course?
Not sure. The only mentioning of this specific message was about Linux and multi-threading, in svnserve. Apparently, due to some race condition/pthread locking semantics problems, something could get corrupted. It could be a compiler bug as well, of course. I would try to get some "official" binaries; 1.2.x works just fine with svn.python.org as well. Regards, Martin
On Sun, 2005-10-30 at 19:08 -0600, skip@pobox.com wrote:
Martin> The natural question then is: what operating system, what Martin> subversion version are you using?
Sorry, wasn't thinking in terms of svn bugs. I was anticipating some sort of obvious pilot error. I am on Mac OSX 10.3.9, running svn 1.1.3 I built from source back in the May timeframe. Should I upgrade to 1.2.3 as a matter of course?
Fredrik> "welcome to the wonderful world of subversion error messages" ... Fredrik> deleting the offending directory and doing "svn up" is the Fredrik> easiest way to fix this.
Thanks. I zapped Objects. The next svn up complained about Misc. The next about Lib. After that, the next svn up ran to completion.
Skip
You didn't happen to try to update a checked out copy from a repo that had an older cvs2svn conversion to the one produced by the final conversion, did you? Cause that will cause these errors too. --Dan
participants (5)
-
"Martin v. Löwis" -
Antoine Pitrou -
Daniel Berlin -
Fredrik Lundh -
skip＠pobox.com