[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.7.1, Build 22161 line 672: assertion failed (checksum != NULL)

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Wed, 16 Nov 2011 10:03:41 +0000

Philip Martin <philip.martin_at_wandisco.com> writes:

>> I hate to confess to such absent mindedness, but I may have "svn delete"ed
>> this file. I see that I don't have a local copy of it, which supports that
>> theory. If I did that, I didn't commit the change -- the repository still
>> has the file.
> I'll have to think about that.

This does explain some things. The client is not adding or modifying
the file due to any change sent from server, it is merely restoring the
missing file from its own metadata. That's a small step forward in
understanding the problem.

It's still not clear how the upgrade went wrong. It's not as simple as
"svn rm file", "svn upgrade", "svn update" as that works (and would have
created an op_depth>0 nodes row that we didn't see in the very first
query you ran).

Perhaps it's something to do with the moved file? Perhaps you did
something like:

   svn rm file-before-mv # or perhaps a mv?
   # some other wc moves and commits the file
   svn update # getting a delete/delete tree conflict
   svn resolved # or revert?
   rm file-after-mv # a non-svn rm
   svn upgrade

Perhaps you had two files with the same checksum (that's legitimate) and
that caused the upgrade to fail? I'll experiment and see if I can
reproduce it.

Received on 2011-11-16 11:04:20 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.