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

Re: error when upgrading working copy

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Tue, 01 May 2012 10:43:20 +0100

Ryan Schmitz <jschmitz_at_marketstar.com> writes:

> Is there another way for me to run 'svn status'?

We might be able to do without. It's unfortunate that the abort message
doesn't give us the filename, if you can run under a debugger the stack
trace would help. Or make your woking copy available to somebody else.

Failing that we have to resort to examining the .svn/entries files
manually--there is one in every directory in a 1.6 working copy. The
upgrade output can help identify which .svn/entries to examine. Given:

Upgrade 'F'
Upgrade 'F/X'
Upgrade 'F/A'
Upgrade 'F/A/P'
Upgrade 'F/A/Y'

then we know the problem occurred after 'F/A/Y' and is not in any of the
directories in the output. It should be the first of:

  - subdirectories of 'F/A/Y' such as 'F/A/Y/T'

  - subdirectories of 'F/A' such as 'F/A/T'

  - subdirectories of 'F' such as 'F/T'

  - subdirectories of '' such as 'T'

What we want to identify is the .svn/entries files that has a "deleted"
token. You can generally open these files with an editor on Linux but I
don't know which Windows tool to suggest. The token is a line of text
"deleted" (not "delete" which is a separate token that is not
interesting in this case).

Received on 2012-05-01 11:43:59 CEST

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