[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Corrupt .svn directories

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-06-02 11:29:10 CEST

On 01.06.2005, at 12:49, Robin Pellatt wrote:

> I have what I think might be a reasonably common problem, but so far
> haven't found a good solution. So...
> My situation is this:
> ----------------------------------------------
> D:\Projects\XXX>svn up
> svn: Working copy '.' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> details)
> D:\Projects\XXX>svn cleanup
> svn: Can't open directory '.svn/tmp': The system cannot find the path
> specified.
> ----------------------------------------------
> Now I know this is because some of my .svn directories have been
> corrupted (my own fault).
> However there doesn't seem to be a clean way to recover from this, and
> I know I'm not the only one who has done this.
> I've looked through the book, the FAQ, the mailing lists, and Googled,
> and the recommended solution seems to be just to move the whole
> working copy somewhere, check out a clean copy, and copy across any
> changes. OK, fine, I could do this, I've got maybe 20 files changed
> across a few directories, it wouldn't take *that* long.
> But it seems to me that Subversion actually has all the information it
> needs to recover from this situation. All I actually want to do is
> force it to recreate all my .svn directories, without messing with my
> changed files.
> [snip]

I would say if you and your developers are routinely corrupting your
.svn directories, then that is the problem that needs to be addressed.
It is perfectly reasonable for Subversion to assume that its
directories will remain intact. If they are not remaining intact, then
that is a problem outside of Subversion. And it is a good thing that
Subversion makes it moderately difficult to recover from this -- make a
new working copy and manually redo your modifications -- because it
encourages the developer not to get into this situation.

Or perhaps it would help us to understand if you listed the steps you
routinely perform which result in the corrupted .svn directories.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 2 11:33:21 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.