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

Re: locked working copy help please

From: Lieven Govaerts <svnlgo_at_mobsol.be>
Date: 2006-09-17 12:08:18 CEST

o.nash@cs.ucc.ie wrote:
> On Sun, 17 Sep 2006, Lieven Govaerts wrote:
>
>
>> o.nash@cs.ucc.ie wrote:
>>
>>> Hi all this might be a little long sorry ..
>>> Using Subervion 1.3.1 with apache 2.0.58 on linux as main users access
>>> point.
>>>
>>> As an experiment I have the /etc directory as a live working copy that is
>>> committed weekly with cronjob. Running now for about 8 weeks.
>>> Last week though postfix was deleted and re-installed i.e. somebody did
>>> rm -rf /etc/postfix
>>> The weekly commit then failed with message:-
>>> ---------------
>>> un Sep 17 03:20:01 BST 2006
>>> svn: 'postfix' is not a working copy directory
>>> svn: Working copy '.' locked
>>> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
>>> details)
>>> svn: Working copy '/etc' locked
>>> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
>>> details)
>>> ---------------
>>>
>>> Problem is how to unlock the working copy so that the new postfix dir can
>>> be added or imported?
>>> ---------------
>>> # cd /etc
>>> # svn status | grep L
>>> L .
>>>
>>> # svn cleanup .
>>> svn: 'postfix' is not a working copy directory
>>>
>>> Using the URL method:-
>>> # svn unlock --force http://hostname:8080/repos/etc
>>> svn: Failed to fetch lock information: 404 Not Found
>>> (http://hostname:8080)
>>>
>>> There is no lock at the repos end svnadmin lslocks repos/path returns
>>> nothing.
>>>
>>> Do I have to temporarily remove the postfix dir then do the cleanup and
>>> re-import postfix or add it?
>>> { I should add this is not a production mail server so would be no
>>> problem doing above]
>>>
>>> thanks Oliver
>>>
>>>
>> Oliver,
>>
>> when svn cleanup talks about locks, it talks about 'lock' files put in the
>> .svn area to indicate svn is working on that folder. In this case cleanup
>> fails to delete the lock files because of that deleted postfix folder. The
>> first thing you should do is put back the postfix folder, and then run the
>> cleanup.
>>
>> I see three possible ways to recover the postfix folder:
>> Revert the postfix folder:
>> svn revert postfix
>>
>> An alternative is to update only that folder, it should normally be
>> ressurected:
>> svn update postfix
>>
>> If none of the above help, you can also checkout the postfix folder
>> svn checkout postfix
>>
>> I suppose one of these three actions has worked, so you can now run 'svn
>> cleanup' on the etc folder.
>>
>> hope this helps,
>>
>> Lieven.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>>
>>
> Lieven
> thanks for the swift reponse,
> the checkout and all other attempts seem to fail because the etc dir
> working copy is locked so no checkout or any other svn cmd can modify
> inside it.
> # svn checkout http://hostname:8080/repos/path/etc/postfix
> svn: Working copy '.' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> details)
>
You should specificy the target folder as well if your cwd = /etc:

svn checkout http://hostname:8080/repos/path/etc/postfix postfix

If that still doesn't work, can you try to checkout that folder
somewhere else on your disk (not in an svn working copy), then copy the
folder to /etc followed by 'svn cleanup'?

Alternatively, if that doesn't work, you can also try a hack by removing
all 'lock' files in the .svn folders, then do that checkout and run 'svn
cleanup'.

Lieven.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Sep 17 12:08:55 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.