[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 23:07:06 CET

>>>>> "Philip" == Philip Martin <philip@codematters.co.uk> writes:
    Philip> "svn status" shows locks.

But only in the current directory and its children, not in parent
or sibling directories.

{1} /tmp/r20031109-9395/r20031109/dir2$ svn st
M file2
{2} /tmp/r20031109-9395/r20031109/dir2$ svn ci -m ''
[1]+ Stopped cim
{3} /tmp/r20031109-9395/r20031109/dir2$ kill %1
[1]+ Terminated svn ci -m ''
{4} /tmp/r20031109-9395/r20031109/dir2$ svn st
  L .
M file2
{5} /tmp/r20031109-9395/r20031109/dir2$ svn cleanup
{6} /tmp/r20031109-9395/r20031109/dir2$ svn st
M file2
{7} /tmp/r20031109-9395/r20031109/dir2$ svn up
At revision 134.
{8} /tmp/r20031109-9395/r20031109/dir2$ svn ci -m ''
svn: Attempted to lock an already-locked dir
svn: working copy locked: /tmp/r20031109-9395/r20031109
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

Notice at line {6} that it looks like a commit should work in
dir2/. It's not apparent that the aborted commit at line {2}
actually locked dir2/../ and that the commit at {8} also wants to
lock dir2/../

(I think some of you already understand what I reported) 'cvs co
server:/foo && cd foo/bar' is equivalent to 'cvs co
server:/foo/bar && cd bar'. 'svn co http://server/foo && cd
foo/bar' LOOKS equivalent to 'svn co http://server/foo/bar && cd
bar' but is NOT: if you abort svn in foo/bar because your network
connection is down, then nothing indicates that you have to 'svn
cleanup' in foo instead of foo/bar.

>> If so the error message for locked directories should
>> specify which directory is locked,
    Philip> It does
    Philip> $ svn up wc 2>&1 | grep locked: svn: working copy
    Philip> locked: wc/foo

Wow, I overlooked that. Though even with the message it's
counterintuitive UI that you need to cleanup outside of the
directory that you were working in.

(I empathize with you for not debugging network-outage-manifested
problems as much. I work on an open-source project and because we
have perfect internet connections at work, network related bugs
sometimes get fixed last. But I use subversion on a wireless
laptop and network outages are common.)

Karl Chen 2003-11-09 13:34
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 9 23:07:46 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.