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

Error with svn move --parents

From: Chris <chris_at_heathens.co.nz>
Date: Thu, 08 Jan 2009 12:08:04 -0500

Hi,

I have noticed that the new --parents option is not as useful or
consistent as it could be with WC moves. It only works when
intermediate directories don't exist. But it fails if intermediate
directories exist but aren't under version control. It seems
inconsistent to me, because svn add works fine with directories that
exist (of course).

Some test cases:

# Start with an empty working copy
svn checkout --depth=empty <myrepo> test
cd test

# Test 1, works OK
touch a; svn add a; svn move --parents a b/c
A a
A /home/chris/test/b
A b/c
D a

# Test 2, e exists but not under version control
touch d; mkdir e; svn add d; svn move --parents d e/f
A d
svn: 'e' is not a working copy
svn: Can't open file'e/.svn/entries': No such file or directory

Expected result:
A d
A e
A e/f
D d

# Test 3, h/i (a directory) exists but not under version control
touch g; mkdir -p h/i; svn add g; svn move --parents g h/i
A g
svn: 'e' is not a working copy
svn: Can't open file'e/.svn/entries': No such file or directory

Expected result:
A g
A h
A h/i
A h/i/g
D g

Is this a bug, or are my expectations wrong? In particular, the case in
Test 2 I run into all the time, so if not a bug, consider it a pleaful
RFE.

Chris

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1011977

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-08 18:43:38 CET

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.