mal content wrote:
> No, it doesn't exist, and I really have no idea what could have removed
> it. I don't use any tmp cleaners or anything like that. My exact actions
> were to run make, run make clean, edit two files, run make and then
> attempt to commit. Nothing in any of those invocations of make would
> have touched that directory, so this is a little worrying.
Is the working copy over NFS? I ask because I have seen similar
problems with the .svn directory becoming corrupted but only when the
working copy exists on an NFS filesystem. It always works fine to a
local filesystem. I have been thinking this was a linux kernel nfs
bug and have investigating but so far no root cause of it.
> For now, I'm just going to create a new branch from the last commit
> and copy diffs over.
It is also possible to do a clean checkout elsewhere and then restore
the .svn directories from the clean area. That would replace your
corrupted .svn dirs with known good .svn dirs. I have done this when
I have had this NFS-related problem. That operation is a little
tricky and you must be careful especially if there is a lot of
hierarchy of directories involved. Don't get them mixed up. But if
you have a lot of changes outstanding may be easier than other
alternatives.
Bob
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 27 19:29:51 2006