On 7/6/02 2:58 PM, "Ben Collins-Sussman" <sussman@collab.net> wrote:
> 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.
I'd just figured out something like this (rev 63 had an add under the copy)
when I got your email...
Having built the new old svn :) I just tried dumping and restoring the repos
(restoring to the old style). It works now.
Updated to new repos format. That seems to work now. And I can commit to
it straight from my old working copy :).
Quick question: There was much talk of a grad re-checkout for changing $svn
to !svn. Does this apply at all to ra-local working copies? I can't see
$svn or !svn in my entries files anywhere.
Thankyou for the help.
\x/ill :-}
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 7 23:11:37 2002