You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Glenn McAllister <gm...@sapient.com> on 2004/09/03 15:28:30 UTC
Transaction errors while updating
Hey all,
Sorry if this has been answered before, but I haven't been able to
locate a solution to my problem. I'm happy to RTFM if someone will point
me at the FM.
We have a large repository with a mix of code, requirement documents,
design documents, etc. Only a relatively small part of the repo is
actually code. To make life easier for the developers, they typically
check out only the code into a local working copy. The repo lives
behind Apache; we hit it with an https URL.
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.
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.
Has anyone else seen this behaviour?
Glenn McAllister
Sr. Associate, Technology, Canada| Sapient
277 Wellington Street West
Toronto, ON M5V 3E4 Canada
desk: +1.416.645.1543
mobile: +1.416.873.6666
fax: +1.416.645.1501
e-mail: gmcallister@sapient.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Transaction errors while updating
Posted by Dmitry Beransky <db...@dembel.org>.
Hmm... I guess I got a different problem, because I get <svn: File not
found: revision '396', path '/svnroot/reports/project.xml'> even from the
command line.
D.
At 05:30 PM 9/9/2004, Ben Collins-Sussman wrote:
>According to the latest #1862 research, this error happens whenever:
>
> 1. the working copy is 'incomplete' (update was interrupted)
> 2. TortoiseSVN tries to update using an absolute path
>
>To fix this, run 'svn up' with a commandline client instead of TSVN. That
>will use a relative path instead of an absolute path, and allow the update
>to complete.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Transaction errors while updating
Posted by Ben Collins-Sussman <su...@collab.net>.
Dmitry Beransky wrote:
> I just finished reading the discussion related to bug #1862
> (http://subversion.tigris.org/issues/show_bug.cgi?id=1862). Just like
> so many other TSVN users I'm constantly hitting this problem. My
> question is: Can anyone recommend a way to recover from this error that
> doesn't involve wiping the local copy?
>
According to the latest #1862 research, this error happens whenever:
1. the working copy is 'incomplete' (update was interrupted)
2. TortoiseSVN tries to update using an absolute path
To fix this, run 'svn up' with a commandline client instead of TSVN.
That will use a relative path instead of an absolute path, and allow the
update to complete.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Transaction errors while updating
Posted by Dmitry Beransky <db...@dembel.org>.
I just finished reading the discussion related to bug #1862
(http://subversion.tigris.org/issues/show_bug.cgi?id=1862). Just like so
many other TSVN users I'm constantly hitting this problem. My question
is: Can anyone recommend a way to recover from this error that doesn't
involve wiping the local copy?
thanks
dmitry
At 03:28 PM 9/3/2004, Tom McMillen wrote:
>this has been reported in bug 1862
>
>http://subversion.tigris.org/issues/show_bug.cgi?id=1862
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Transaction errors while updating
Posted by Tom McMillen <th...@mppglobal.com>.
>
> 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