On Oct 2, 2006, at 14:37, Jason Ulrich wrote:
> I've tried to run svn cleanup on several levels of my working
> copies and I
> continually run into locks. I think somebody who hadn't used
> subversion
> before tried to delete the .svn directories on a couple directories
> and
> now we're not able to do anything.
>
> Svn status shows the files as "M" and not "L". Yet, the errors keep
> saying that they are locked.
I think you're mixing up two unrelated uses of the word "lock" when
relating to Subversion.
One sense, which I think applies to your situation, is that
Subversion had trouble dealing with your working copy, and left some
tokens around, which svn cleanup is meant to clean up, except if you
removed .svn directories then it won't be able to, so your working
copy will still be locked, in that sense.
The other sense, the one which has an L status, is when you want to
be the only person able to work on a given file, and you lock it in
the repository until you're done with your changes. I don't think
this applies to you.
But, if you post the exact error message you get, that might clarify
which of these cases applies.
> What's our best plan of attack here?
Best bet is to check out a new working copy, manually move over any
uncommitted changes you still had in the old working copy, and in the
future, don't remove .svn directories or anything in them. That's
Subversion's domain and it needs everything there to be under its
control so it knows what's up.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 3 21:29:48 2006