I have seen this in the past too, could not determine what lead to it. Ludo tells me that Mercurial is even worse, requiring manual merging each time he gets an update on an untouched workspace, I hope it's specific to his settings.
On Jun 18, 2011, at 12:07 AM, Bill Shannon wrote:
> I did not.
>
> My script runs every night and does "svn up". Last night it failed
> with that message. I didn't do anything with distributions/nucleus.
> In my workspace it looks like a derived directory, containing only
> a "target" directory. Has it become a managed directory in the latest
> update?
>
> Sure wish svn would handle these cases...
>
>
> Jane Young wrote on 06/17/2011 05:47 PM:
>> You may have removed distributions/nucleus and restored to an older version of
>> distributions/nucleus.
>> Try removing distribution/nucleus and execute "svn update".
>>
>> On 6/17/11 5:25 PM, Bill Shannon wrote:
>>> I'm seeing this on two machines when I try to svn up:
>>>
>>> D distributions/nucleus
>>> svn: Failed to add directory 'distributions/nucleus': an unversioned directory
>>> of the same name already exists
>>>
>>> Am I supposed to remove the directory and try again?
>>
>