Question: "cannot replace a directory from within" -- what happened?

[Jochem Schulenklopper <j....@gmail.com>]

I stumbled into a vague problem, I searched the archives, found
similar postings of this symptom... but no clear answer/solution was
given. It's a non-blocking but confusing issue, hence this mail.

The problem: suddenly I decided that my project's name needed to be
changed. I have a local file system BDB-type repository, and the top
directory in my repository also needed to change since it carried the
project's name. I moved that folder... and relocated my working copy
since its URL to a place in the repository changed.

After this, svn commit-s and svn log-s seemed to be working fine...
but svn update-s fail consistently with the mysterious "Cannot replace
a directory from within" error message. I closely examined the change
log and the result of svn info on typos, but didn't find any.

Re: Question: "cannot replace a directory from within" -- what happened?

[Ingo Adler <de...@synacon.ch>]

Hi,

have you got a solution until now?
I have the same problem too. I relocated with svn and with tsvn (on a 
different machine) - it doesn't work.

The entry files in the top level .svn directory are the same from the 
relocated and a newly checked out copy, especially the url - only the 
dates differ.

Ingo.

Jochem Schulenklopper wrote:

>Hi,
>
>On 05 Jan 2005 11:26:09 -0600, kfogel@collab.net <kf...@collab.net> wrote:
>[lengthy problem description deleted... search the archives for the
>full text --JSc]
>  
>
>>In your old, not-functioning-quite-correctly working copy, does 'grep'
>>find any instances of the old repository name?
>>
>>'svn switch --relocate' *should* have done what you expected, I don't
>>know why it didn't.
>>    
>>
>
>No, grepping did not find instances of the old repository name. I also
>don't know what happened.
>For your convenience, I'll attach a log of my CLI actions and results,
>including the grep. It should be easy to reproduce my case. I'm
>curious what you may find (hopefully not an error on my side).
>
>While doing the reproduction, I also noted a difference between SVN
>and the same command executed via TSVN. If and when the "svn switch
>--relocate" gives an error in SVN (not in the log attached, I
>encountered this another time), TSVN does not seem to catch it
>properly and reports a successful execution. I'll report that
>seperately to dev@t.t.o.
>
>Kind regards,
>
>Jochem
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Question: "cannot replace a directory from within" -- what happened?

[Jochem Schulenklopper <j....@gmail.com>]

Hi,

On 05 Jan 2005 11:26:09 -0600, kfogel@collab.net <kf...@collab.net> wrote:
[lengthy problem description deleted... search the archives for the
full text --JSc]
> In your old, not-functioning-quite-correctly working copy, does 'grep'
> find any instances of the old repository name?
>
> 'svn switch --relocate' *should* have done what you expected, I don't
> know why it didn't.

No, grepping did not find instances of the old repository name. I also
don't know what happened.
For your convenience, I'll attach a log of my CLI actions and results,
including the grep. It should be easy to reproduce my case. I'm
curious what you may find (hopefully not an error on my side).

While doing the reproduction, I also noted a difference between SVN
and the same command executed via TSVN. If and when the "svn switch
--relocate" gives an error in SVN (not in the log attached, I
encountered this another time), TSVN does not seem to catch it
properly and reports a successful execution. I'll report that
seperately to dev@t.t.o.

Kind regards,

Jochem

Re: Question: "cannot replace a directory from within" -- what happened?

[kf...@collab.net]

Jochem Schulenklopper <j....@gmail.com> writes:
> I stumbled into a vague problem, I searched the archives, found
> similar postings of this symptom... but no clear answer/solution was
> given. It's a non-blocking but confusing issue, hence this mail.
> 
> The problem: suddenly I decided that my project's name needed to be
> changed. I have a local file system BDB-type repository, and the top
> directory in my repository also needed to change since it carried the
> project's name. I moved that folder... and relocated my working copy
> since its URL to a place in the repository changed.
> 
> After this, svn commit-s and svn log-s seemed to be working fine...
> but svn update-s fail consistently with the mysterious "Cannot replace
> a directory from within" error message. I closely examined the change
> log and the result of svn info on typos, but didn't find any.
> 
> >From the investigations I did, I found that the repository seems to be
> fine. A fresh checkout of a new working copy is functioning without
> problem. So, somehow, the working copy seems to be corrupted or
> out-of-sync, but the cause is not clear. Moving a repository folder
> without relocating the working copy will surely give an (the same)
> error, because the current registered URL (for the root of the working
> copy which happens to be at some deeper level in the repository)
> doesn't exist anymore. Apparently, the relocation of the working copy
> doesn't solve this inconsistency, in contrast to my expectation. (But
> I could be wrong.)
> 
> While communicating with Joel Alexandre (who also mentioned this
> problem in December 2004), he mailed:
> <quoting relevant parts>
> I've never used move or relocate. [...] I did a checkout and after
> that i only used update. [...]
> When [...the problem...] happend for the first time, i contacted the
> repository administrator asking if he had changed something. The
> answer was that he didn't. The repository didn't change, i didn't
> change my WC.
> </quoting relevant parts>
> 
> So, apparently the problem does not seem to be 100% correlated to my
> moving and relocating... but what is? Another poster replied something
> along the lines of "this seems to be a bug that they just haven't
> started working on". (Without offense:) Is that the current state, or
> is it still in the unknown?
> In case this behavior is exactly as designed ("it's not a bug, it's a
> feature!"), it would be a solution to clarify the error message, or
> improve the documentation on this point. I couldn't find a reference
> to this message in the documentation nor the FAQ.

In your old, not-functioning-quite-correctly working copy, does 'grep'
find any instances of the old repository name?

'svn switch --relocate' *should* have done what you expected, I don't
know why it didn't.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org