----------------- repro.sh -------------------------
#!/bin/bash
#./cvs2svn.py --dump-only test-data/split-branch-cvsrepos
rm -rf sb1.svn sb2.svn
svnadmin create sb1.svn
svnadmin create sb2.svn
svnadmin load sb1.svn < pathological-dump
svnadmin dump sb1.svn > intermediate-dump
svnadmin load sb2.svn < intermediate-dump
svnlook tree sb1.svn > sb1.tree
svnlook tree sb2.svn > sb2.tree
diff -u sb1.tree sb2.tree
----------------- END -------------------------
----------------- output --------------------------
--- sb1.tree 2004-02-26 15:43:38.611712000 +0000
+++ sb2.tree 2004-02-26 15:43:39.833468800 +0000
@@ -6,6 +6,7 @@
branches/
demo-node-0/
module/
+ branched-from-branch
branched-from-trunk
first_working/
module/
----------------- END -------------------------
In other words, THE CONTENTS OF THE REPO WAS CHANGED BY DUMP-LOAD.
The sometimes overly complex dumpfiles produced by cvs2svn seem to confuse
the loader into producing a repository which behaves correctly to "svn
checkout", but incorrectly to "svn log -v" and "svnadmin dump".
I'm attaching a bz2-ed copy of pathological-dump, so that the bug can be
reproduced without cvs2svn.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 26 17:00:07 2004