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

Re: Can't move directory that uses externals unless I --force?

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-01-31 14:51:39 CET

On Jan 31, 2006, at 14:18, Andy Levy wrote:

>> One directory in this project, libs, contains one externals
>> definition. When I try to move libs, I get an unexpected message:
>> $ svn mv libs web
>> Performing status on external item at 'libs/some-library'
>> svn: Use --force to override this restriction
>> svn: Move will not be attempted unless forced
>> svn: 'libs/some-library' is not under version control
> If libs is an external, there's no point in moving it in your working
> copy (which is why, I presume, you're being forced to use --force).
> The next time you update, it'll show up right where it was before.
> And no one else will be aware of the move.
> Instead, remove it from svn:externals for working-copy-of-trunk and
> add it to svn:externals for working-copy-of-trunk/web

libs is not an external; libs contains an external (called "some-
library" in my example above).

$ svn proplist -v libs
Properties on 'libs':
   svn:externals : some-library https://www.example.com/svn/tools/

libs also contains several other libraries unique to this project
which are not included via externals. So I really do quite simply
want to move libs somewhere else, but encounter the given error.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 31 14:58:48 2006

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.