On Tue, Mar 11, 2008 at 5:45 AM, Simon Berry
<Simon.Berry_at_andromeda-telematics.com> wrote:
>
> > I had an issue earlier with my working copy where I could not cleanup
> a directory with an error message along the lines of :
> > "Could not copy .svn/tmp/text-base/<filename> to
> .svn/tmp/<filename>.tmp : no error" (sorry - I can't remember the exact
> message).
> > Eventually, I figured out that the .svn/log file had an entry pointing
> to the problematic <filename> in question. By deleting the 'log' file I
> was able to successfully complete the cleanup.
> > I think the .svn mismatch occurred after I terminated the
> 'TortoiseProc.exe' process in task manage during an update (the cancel
> button did not seem to work).
> > Is there any danger in deleting the log file ? Have I compromised the
> integrity of my working copy ?
>
> When attempting an update on the directory that had been 'hacked', I
> encountered a checksum error on the effected file. I had to delete the
> entire directory and do a fresh update of all files.
>
> I think I have therefore answered my own question : you should not
> fiddle with the .svn/ files .....
That's one of the reasons it's hidden, and numerous sources advise to
not mess with it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-03-11 15:05:22 CET