[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: David Grant <davidgrant_at_gmail.com>
Date: Sun, 24 Aug 2008 23:20:19 -0700

On Sun, Aug 10, 2008 at 11:23 PM, Ryan Schmidt <
subversion-2008c_at_ryandesign.com> wrote:

> 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.
I agree, but is it possible that the error message could be better?

I think what is happening is that it is going through all the working copy's
directories and locking them, but first it checks if the directory is
already locked (that's my guess). It locks B first, for example, and then
tries to lock A (the symlink to B) but it's already locked, so it fails.
Received on 2008-08-25 17:05:16 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.