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

Re: possible bug: checkout parent dir fails on subdir if it's wc

From: Denis Pokataev <dpokataev_at_team.vega.ru>
Date: Thu, 28 Aug 2008 11:14:59 +0400

Daniel Shahaf пишет:
Denis Pokataev wrote on Tue, 26 Aug 2008 at 13:02 +0400:
checkout parent dir fails on subdir if it's working copy already

Steps to reproduce:
Assuming repo has

mkdir -p dir/subdir
cd dir/subdir
svn co http://svn.domain/svn/dir/subdir ./
A    file2
 U   .
Checked out revision 1.
cd ../
svn co http://svn.domain/svn/dir ./
A    file
svn: Failed to add directory 'subdir': a versioned directory of the same 
name already exists

Shouldn't it just update 'subdir' as it is working copy already?..


'svn checkout --force'?  It will "slide" a working copy under the existing 
files.  (You might have to remove all .svn dirs first for this to work.)

It is possible to do so manually, but I've ran into this problem during automatical checkout... And more important - don't you think that it's incorrect behavior? it's not just a "versioned directory", it's the same working copy - so it needs regular update, imho.

It is possible to checkout new directory, and later checkout it's subdirectories - using --depth key. So, why it's not possible to checkout parent directory later?

And one more comment:
comments from Karl Fogel
"Yes. IMHO, a checkout into an existing directory should behave like an update, assuming that the checkout is of the same URL that the existing wc represents."

So?.. checkout into existing subdirectory should behave like an update, even if parent directory was not checked out earlier, am I right?
Denis Pokataev
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.org Received on 2008-08-28 15:56:43 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.