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

>>> Jack Repenning <jrepenning@collab.net> 07/24/03 06:12PM >>>
>Any chance that, on the first time around, you got something like this?
<snip>
>svn: A problem occurred; see later errors for details
>svn: Your commit message was left in a temporary file:
>svn: 'C:/Documents and Settings/Jack Repenning/Desktop/home/svn-commit.tmp'

Yep - that looks very familiar. I also had a couple svn.commit-tmp[123] files hanging around. Unfortunately, those got tossed in an attempt to clean up and start again. :) I had a number of things (learning curve errors) that left those tmp files around, so I didn't treat them differently than others. I would be fine with recovering with the technique you used, if I knew about it beforehand. But now, here are the resources that I seem to have available to get back to a good status:

daily.sh - Working copy
.svn/prop-base/daily.sh.svn-base - list of properties valid for the file
.svn/props/daily.sh.svn-work - list of properties valid for the file
.svn/text-base/daily.sh.svn-base - prior rev of the file

I'm thinking that I can just revert to a version before the (prior) version that is stored in text-base/ and then make my changes to bring it up to date - but will that mess up the diff with the prior-to-current version? (I'm guessing yes)

The other option I'm thinking is changing the "entries" file in .svn to have the checksum for the base file that it actually has - but would that cause further badness in the repository?

Final option would be to just "svn rm" it, get the repository to a clean state, and then bring the script back in a later commit.
Should checking if the destination is locked (unwritable) be part of the commit process somewhere?

Thanks for all the help!
--Cedric

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 25 17:01:01 2003