Hi Alex!
Am Sonntag, 22. August 2004 16:01 schrieb Alex Martelli:
> Not sure what I've done to cause it, and can't easily reproduce the
> behavior in a toy case, but it does happen systematically each time I
> run a script to build a directory tree for one more chapter of the book
I can get a working copy in a state as you described by the following
transcript:
---------------8<------------------
dirk@deepthought:/tmp> svnadmin create foo-rep
dirk_at_deepthought:/tmp> svn mkdir file:///tmp/foo-rep/trunk
Committed revision 1.
dirk_at_deepthought:/tmp> svn co file:///tmp/foo-rep/trunk trunk
Checked out revision 1.
dirk@deepthought:/tmp> cd trunk/
dirk@deepthought:/tmp/trunk> svn mkdir a
A a
dirk@deepthought:/tmp/trunk> svn mkdir b
A b
dirk@deepthought:/tmp/trunk> svn ci -m "a b"
Adding a
Adding b
Committed revision 2.
dirk@deepthought:/tmp/trunk> mv a b
dirk@deepthought:/tmp/trunk> svn st
! a
? b/a
dirk@deepthought:/tmp/trunk> svn add b/a
svn: warning: 'b/a' is already under version control
dirk@deepthought:/tmp/trunk> svn rm b
svn: Use --force to override this restriction
svn: 'b/a' is not under version control
---------------8<------------------
The problem is using "mv" instead of "svn mv", so that "b/a" looks like an
directory under version control (because it contains a .svn subdir), but has
no entry in the .svn directory of "b". Is this similar to your build script?
You might get similar problems when composing your directory tree, that is to
be added, by cp'ing directories already under version control instead of "svn
cp"ing them.
HTH,
Dirk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 22 21:00:03 2004