On Aug 29, 2007, at 20:08, Glen Barber wrote:
> Quoting Ryan Schmidt:
>> But after running "svn update", your working copy should now be up-
> As stated in my initial post, `svn update` does not change my working
I know you stated that, but I've never heard of an instance of this
message that wasn't resolved by "svn update" so I wanted to make
>> Please try checking out a new working copy ("svn checkout <url>
>> <dir>") and
>> see if you can replicate the problem there. If not, you've solved
>> problem. Get rid of the old working copy, after manually moving
>> any changes
>> over to the new one.
> This problem occurs with Microsoft Office 2003 (specifically .doc
> -- I don't use many other office formats). Checking out a new
> copy is not a solution, because I am the only person committing to
> specific repository.
Working copies in Subversion are considered disposable. It occurs
from time to time that a working copy becomes corrupted in some way,
and the suggestion in those cases is to check out a new working copy.
It's a useful troubleshooting step.
On Aug 30, 2007, at 10:11, Glen Barber wrote:
> Here is the exact error, copied from TortoiseSVN.
> Modified: E:\backup\New Microsoft Word Document.doc
> Error: Commit failed (details follow):
> Error: Your file or directory 'New Microsoft Word Document.doc' is
> probably out-of-date
> Error: The version resource does not correspond to the resource within
> the transaction. Either the requested version resource is out of date
> (needs to be updated), or the requested version resource is newer than
> the transaction root (restart the commit).
Ok. And you're absolutely sure that running "svn update" now does not
allow you to commit?
If so, can you provide us with a reproduction recipe for this issue,
starting from creating the repository and creating the initial files?
Otherwise I'm not sure how to troubleshoot this further.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Aug 30 22:52:04 2007