>
> Here's the problem. If a developer tries to update one of the
> subdirectories, they occasionally get the following error:
>
> REPORT request failed on '/svn/<repo-name>/!svn/vcc/default'
> File not found: transaction '17s', path '/trunk/Development/Toolchain'
>
> Substitute '/trunk/Development/Toolchain' with pretty much any
> subdirectory you want. :-) There isn't any consistency as to when the
> errors occur. It appears to be random although I'm sure it's not.
> Cleaning up the directory doesn't seem to help.
>
We have had this error too
svn (1.0.6) running behind apache on Win2003
using TortoiseSVN client (1.0.8) on WinXP.
It has happened several times, but most often it
seems to happen whenever a directory is moved by one person, the change is committed,
then when someone else updates, they get an error...
will not delete locally modified file,
then whenever they try to update again they get an error as you have described...
REPORT request failed on 'svn/!svn/vcc/default'
File not found: transaction 'p7', path '/trunk/Subfolder/RandomLocation'
where Subfolder is updated.
> The workaround is to try the update from a parent directory. Often you
> have to go to the "root" of your working copy. It doesn't have to be
> the actual root of the full repository, just the root of the working
> copy.
>
We've also found that clean up doesn't work, and if you try to delete the path given,
you just get the error elsewhere...
It usually leads to the working copy being wiped and re checked out.
> Has anyone else seen this behaviour?
>
this has been reported in bug 1862
http://subversion.tigris.org/issues/show_bug.cgi?id=1862
I don't have time to try and replicate this issue (at present - would love to get it
solved though) and because of this we may end up moving away from subversion to
another tool because of the time lost re checking out repositories.
Things I'm hoping to follow up on are...
When stuff has been moved, an update has been run by people whilst the moved project
is currently open on there PC in Visual Studio. I'm wondering if there is some nasty
interaction going on with Visual Studio locking files that the update then
can't complete and the working copy's db is getting broken.
Tom McMillen
Senior Systems Developer
MPP Global
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 4 00:25:09 2004