Timothy B K. Kientzle wrote:
> The only operations I used were "checkout", "update", and "commit"
That can't be really true. You must have at least used the "remove" and
the "add" command too, according to the entries file.
> I did not use "switch" or "relocate", I never tinkered with the
> internals of the .svn dir, nor did I do anything else that an
> ordinary developer wouldn't do a dozen times a day.
Sometimes ordinary developers don't use the commands right ;) Seriously:
I just got some crashreport two days ago. And by discussing this with
the one who sent the report I found out that they use the "relocate"
command to switch their working copies to other branches. They did that
because "the relocate command only rewrites the URL, so it won't touch
any files which I may have modified in my working copy at all - and
that's what we want".
> Nevertheless, TortoiseSVN is somehow terminally confused
> about the state of the WC. It refuses to update or commit, cleanup
> has no effect, nor does a system reboot.
Rebooting does not help at all. Why did you think it would help?
I can't really say what's wrong here. The server pointed to by the
working copy you sent is not available from here, so I can't really tell
you if update doesn't work or not.
But the command line client shows for an 'svn st -v':
! 58 52 tkientzle .
D 55 55 tkientzle fooey.txt
A 0 ? ? foo.txt
The "!" on the folder shows that the folder is "incomplete", i.e. you
checked it out non-recursively (with TSVN, that means you activated the
"Only check out the top folder" checkbox when checking out).
You have to be careful with that option. Subversion doesn't handle such
folders very well. After all, from a Subversion point of view, an
incomplete working copy _is_ already broken. Sure, Subversion allows
that, but it also means that by allowing it there's a lot of
workaround-code in play which doesn't always work well - it's not as
well tested as the rest of the code.
> My suspicion is that some internal SVN operation is interrupted
> (possibly because of file locking?) and as a result, inconsistent
> data is written into the .svn directory. I copied this
> trashed WC to another dir and was able to partially recover by deleting
> some of the clearly erroneous data from the "entries" file.
Define "clearly erroneous data" please. What exactly did you do?
> Unfortunately, I can't seem to find any docs for the "entries"
> file, so I couldn't tell you definitively what might be wrong
> with it. I was hoping someone on this list would be able to tell me.
I'm sorry to tell you that, but TSVN uses the Subversion library which
does all the Subversion commands, including handling the working copies.
TSVN _never_, ever touches any files inside the .svn directory.
So you might have more luck asking sending your messed up working copy
to the Subversion mailing list (users@subversion.tigris.org).
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Aug 27 20:55:28 2004