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

Re: interrupt/cleanup mechanism

From: Karl Chen <quarl_at_hkn.eecs.berkeley.edu>
Date: 2003-11-09 06:39:18 CET

I meant:

Let's say I do 'svn ci' in ~/dir1/dir2/ to commit
~/dir1/dir2/file3, and interrupt it with C-z ; kill %.

When I do 'svn cleanup' in ~/dir1/dir2/, it seems to complete
successfully, but any other svn operation fails with the usual "do
svn cleanup" message.

After I do 'svn cleanup' in ~/dir1/, things work again.

It's not obvious that you need to do it in ~/dir1/, instead of

I'm running svn 0.32.1. This behavior has been around for at
least months.

>>>>> "Ben" == Ben Collins-Sussman <sussman@collab.net> writes:
    Ben> On Sat, 2003-11-08 at 22:13, Karl Chen wrote:
>> If I interrupt subversion, often I have to do 'svn cleanup'
>> in parent directories before it will work again.
>> Is this normal?
    Ben> Yes. Read this FAQ:
    Ben> http://subversion.tigris.org/project_faq.html#wedged-wc
>> And if so, having to 'cd .. && svn cleanup' should be
>> explained in the error message.
    Ben> If your working copy has locks left in it, the error
    Ben> message should say exactly that: "working copy locked:
    Ben> run 'svn cleanup'" Does it not? Are you running a very
    Ben> old version of svn?

Karl Chen 2003-11-08 21:35
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 9 06:40:12 2003

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

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