William Uther <will+@cs.cmu.edu> writes:
> Hi,
> I just started playing with switching to the new repository format.
> "svnadmin dump" worked fine. I only had ~120 revisions so I didn't bother
> redeltifying. Anyway, "svnadmin load" dies...
>
> ------- Committed new rev 62 (loaded from original rev 62) >>>
>
> <<< Started new txn, based on original revision 63
> * adding path : trunk/Papers/Thesis/fig/introb ...COPIED... done.
>
> subversion/libsvn_fs/tree.c:200
> svn_error: #21073 : <Item already exists in filesystem>
> file already exists: filesystem `svnroot/db', transaction `1r', path
> `trunk/Papers/Thesis/fig/introb/rawMaze.graffle'
I'm 90% certain that I know what your problem is, because it looks
exactly like what I've experienced myself.
You see, 'svnadmin dump' used to dump all the files below a copied
subtree, and 'svnadmin load' used to deliberately ignore these files
if the copy went successfully.
We tossed that plan: now 'svnadmin dump' just writes a *single* record
into the dumpfile: "copy this directory", and 'svnadmin load' isn't
deliberately ignoring any records anymore.
The problem you're seeing (I'll bet) is that your dumpfile was
produced by an older version of svnadmin -- it dumped too much data.
And now you're trying to load the data with the latest svnadmin that
doesn't want to see the data ("whattyamean add this file? it's
already there, it was part of the copy!")
Build yourself a static r2092 binary of svnadmin, and use *that* to
make your dumpfile.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 7 21:00:16 2002