On Tue, May 20, 2008 at 3:40 PM, J Snod <subclipse_at_thesnodgrass.com> wrote:
> I am having all sorts of trouble with my repo, have researched fixes, tried
> them all, and they all failed. Here is the process. A commit failed,
> giving the following error:
>
> svn: Commit succeeded, but other errors follow:
> The directory is not empty.
> svn: Error bumping revisions post-commit (details follow):
> svn: Can't remove 'W:\projects\site.com-trunk\public_html\dir1\.svn': The
> directory is not empty.
>
> And now when attempting to re-try the commit, I get the following:
>
> Attempted to lock an already-locked dir
> svn: Working copy 'W:\projects\domain.com-trunk' locked
>
> Ok, so it's locked, so I try an SVN cleanup:
>
> Working copy not locked; this is probably a bug, please report
> svn: Unable to lock 'W:\projects\site.com-trunk\public_html\dir2'
>
> I figured I'd try an update, and it gives me the same error as my commit
> attempt:
>
> Attempted to lock an already-locked dir
> svn: Working copy 'W:\projects\domain.com-trunk' locked
>
> I'm pulling my hair out here. Does anyone have any suggestions for getting
> this fixed?
>
> This is on Eclipse 3.2.2 with Subclipse 1.2.4
These errors are all coming out of the Subversion libraries, which we
are just driving from Subclipse. I'd suggest you recreate the problem
using the command line and report on the Subversion users@ list so
that you have a wider net of help you can receive.
I have seen errors like this reported on that list before, I do not
recall what the resolution was. It should be easy to recreate the
problem using the command line client if it is happening consistently
from Subclipse.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-05-20 22:10:10 CEST