Re: How to backup a running script? and how to recover out-of-sync file?

"Cedric Williams" <CedWilli@tceq.state.tx.us> writes:

>>But you've still got the more fundamental problem: it's not working
>>to "self-commit" a script if it has keywords to expand. I don't
>>think that's going to go away. Checking to see whether the file's
>>writable might be done, but it would only allow SVN to refuse the
>>checkin, which ain't necessarily what you had in mind!

There is not much we can do if the OS prevents the client from
modifying a file in the working copy, that's always going to produce
an error. However if you can a) reproduce the problem, and b) build a
HEAD (later than revision 6584) client, then you should find that the
behaviour has improved.

Now when you get the error from "svn commit" the working copy will
remain locked. You will be unable to update or commit that working
copy until you successfully run "svn cleanup". For that to happen you
will need to remove the underlying problem (the inability to overwrite
the file), if you try to run cleanup before that it will fail and the
working copy will remain locked.

Once cleanup is successful the working copy will be useable again. It
may be out of date in places, that depends on where the original error
occurred during the post-commit processing, but an "svn update" will
fix that.

I don't have a Windows machine to test your exact scenario, but I can
reproduce something similar on Unix by using a debugger to simulate
errors.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org