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

danger / bug in moving externals

From: Lübbe Onken <l.onken_at_rac.de>
Date: 2004-11-22 11:54:10 CET

Hi Folks,

consider the following situation:
your WC is in myProject, myproject contains a subfolder named "foo" Set
svn:externals on myProject to "bar http://some/location", commit your
changes and update your working copy.
You now got:
myProject/bar (External)

now do 'svn move bar foo' You get:
A foo/bar
D bar/...
...A lot of files and folders inside bar...
svn: 'bar' is not under version control,

but the move has taken place!

'svn st -v' shows you:
X bar
A + foo\folder
    + foo\...
Performing status on external item at 'bar'
D bar
D bar\folder
D bar\...

Now I didn't dare to commit this, because I'm afraid that the scheduled
deletion really is going to kill files from my separate repository for
the "bar" project. The files in bar are now scheduled for addition to
myproject\foo\bar, so the external property is lost.

Luckily enough there's a nice 'revert' function, but I think that 'svn
moving' externals should be disabled / discouraged / warned in the first
place. 'svn copy' externals is fine, but moving externals should be
forbidden or only allowed with --force because this results in a
deletion in one repository and an addition in another repository. Dangerous!


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 22 11:55:56 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.