[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnrdump produce a strange dump file

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Fri, 2 Oct 2015 09:00:19 -0400

On Fri, Oct 2, 2015 at 3:26 AM, Yves Martin <ymartin1040_at_gmail.com> wrote:
> Hello,
> The problem I face now when using "svnadmin dump" is "svndumpfilter:
> E200003: Invalid copy source path' when selecting the three /trunk modules I
> am interested in.
> Such a problem "svnrdump" does not produce.
> Thank you in advance for your help
> --
> Yves Martin

Oh, my. Stop right there. Remember how svnrdump didn't work? Now
you're adding another peoblem, picking and choosing individual
components with svndump. Do a test svnadmin dump, and reload of
everything to a new repo, *first*. This helps eliminate confusion and
verifies that the basic process is workable.

*Then* consider optimizing. Dump from the *new* repo, with the latest
tools, and see if picking and choosing works there. And in general,
avoid picking and choosing with svnadmin dump: it's never worked that
well if components were moved among various target directories, if
"trunk" directories got renamed or re-arranged, etc.

Frankly, also, if you're planning on re-arranging the material and
putting up a pruned repository, why are you bothering with dumps? Why
not save yourself some grief, lock the original content in a final
tag, do an export and import, and start with a completely clean new
Received on 2015-10-02 15:00:24 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.