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

[Subclipse-users] Working copy has been left locked

From: Mathias Kleiner <mkleiner_at_massidia.fr>
Date: Mon, 04 Aug 2008 17:58:59 +0200

Hello,

I encountered the following (bug?) when using subclipse. Maybe I did
something wrong (I'm not an SVN expert), but I can't use my eclipse
project anymore. Here is what I did :

I moved a bunch of folders from one folder to another inside my project
using drag and drop. Old folders were marked as "to be deleted", and new
folders as "to be created". Which I suppose is fine (at least, that's
what I wanted).

Then I made an update of my project, and finally I committed.

The commit went fine, but at the very end, subclipse said (in console) :

> commit successful but working copy has been left locked
> This is probably a bug, please report" (or something similar).

Now everytime I try to commit anything in my project it says (in console) :
> Attempted to lock an already-locked dir
> svn: Working copy 'path/to/my/project' locked

I looked for a way to unlock my project, but did not find anything (at
least in the team menu, and for the main folder since I have a lock
option for files)

I guess I could delete my eclipse project and checkout the repository
one again, but I would like to avoid that for various reasons.

Is that a bug ? Can you help me "unlock" my working copy ?

Thank you,
Mathias Kleiner

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-04 18:01:50 CEST

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