----- John Felczak <jfelczak@siderean.com> wrote:
> JF>> Here's what it looks like in the area around
> JF>> where it's complaining about:
> JF>>
> JF>> K 8
> JF>> svn:date
> JF>> V 27
> JF>> 2006-10-14T06:55:40.217639Z
> JF>> PROPS-END
> JF>>
> JF>> * Dumped revision 0.
>
> JS> This part is wrong. You must have piped both stdout and stderr
> JS> into the dump file.
>
> JS> Subversion is absolutely capable of loading it's own dump
> files...
> JS> if you don't mix text that was meant for the screen into them.
> :-)
>
> OK, gotcha. Would have saved me some panic and an indigestion if the
> documentation and the error message had been little more informative.
In what way? I think it was pretty clear in the error that it was expecting a header and found the "Dumped revision" line instead. Can you make a suggestion of how to change the error message?
>
> JS> You need to remove these "* Dumped revision Xxx." lines.
> JS> Keep in mind that the dump files are binary, so you need
> JS> to exercise caution when editing your dump file.
>
> So sounds like good news, that these dumpfiles can actually be fixed
> so that svnadmin will load them. Just remove all the "Dumped revison
> *" lines and hopefully it should load?
Correct.
>
> Also good to know that one should expected to see binary data at
> various places in the dumpfiles, and that it doesn't necessarily mean
> they're corrupt.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 13:36:25 2006