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

Re: Error message about locked directory after replacing dir with symlink to another dir

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Mon, 11 Aug 2008 01:23:58 -0500

On Aug 10, 2008, at 21:05, David Grant wrote:

> I'm using svn v1.4.6 (r28521). I am curious if 1.5 has the same
> behaviour or if others think the expected behaviour is different
> than what I think it should be.
> #set up test repository
> svnadmin create /home/david/svntest
> cd ~/svn
> svn co file:///home/david/svntest ./svntest
> cd svntest
> #create base directories
> mkdir A B
> svn add *
> svn ci -m ""
> #remove A, create symlink to B, called "A"
> rm -rf A

Don't do this. "A" is a versioned directory at this point. You must
not remove it behind Subversion's back.

> ln -s B A

And you definitely should not be changing it from a directory to a
symlink behind Subversion's back.

> #run svn update (with intention to update B which is still in
> working copy)
> svn up
> svn: Working copy 'B' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> details)
> Expected behaviour: svn should give some error message when it
> tries to update A but it should still update B. At the very least
> it shouldn't tell me that some directory is locked. After I run svn
> cleanup on '.' and B, svn up still gives the "working copy 'B'
> locked" message
> Please reply by e-mail because I am not subscribed to the list.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-11 08:24:31 CEST

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.