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

Re: [Subclipse-users] Working copy has been left locked

From: Mathias Kleiner <mkleiner_at_massidia.fr>
Date: Mon, 04 Aug 2008 18:54:54 +0200

Thank you for your answer.

Unfortunately, cleanup did not work :

>cleanup D:/fichiers/dev/eclipse-workspace/massegate/trunk
> Problem running log
> svn: In directory 'path/to/my/projet/subfolder1/subfolder2'
> svn: Error processing command 'committed' in
'path/to/my/projet/subfolder1/subfolder2'
> File can't be found
> svn: Can't move
'path/to/my/projet/subfolder1/subfolder2\.svn\dir-props' to
'path/to/my/projet/subfolder1/subfolder2\.svn\dir-prop-base': File can't
be found

I guess I'll have to save everything I could not commit, delete project,
and checkout project from repository again.

Mathias Kleiner

Mark Phippard a écrit :
> On Mon, Aug 4, 2008 at 11:58 AM, Mathias Kleiner <mkleiner_at_massidia.fr> wrote:
>
>
>> 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).
>>>
>
> That message comes out of the Subversion library we call. If you can
> come up with a set of steps to reproduce we can report the bug to
> them.
>
>
>
>> 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 ?
>>
>
> You can try Team > Cleanup on your project. That runs the SVN API
> that "fixes" these problems. It does not fix them all though. You
> might need to checkout again to fix your working copy.
>
>
Received on 2008-08-04 18:55:00 CEST

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