Re: svndumpfilter and svnsync?

On Oct 10, 2018, at 02:04, Chris wrote:

> I've trawled through bad commits of data files in our repo and added such paths to a filter file that I'm using for svndumpfilter to get a reasonably-looking dump. In most cases, the files in question existed in a single path(branch( and were no problem. But in some cases, the same files had been copied to a 2nd branch and then svndumpfilter gave me errors about missing source paths, so I added the same path on the 2nd branch to the filter expressions and tried again. After a few iterations of this process, I have a dump that should do what I want.
> So I start "svnadmin load" and based on initial progress, that might take a couple of days to complete so I leave it overnight. I get back today and the load has crashed with a missing path. The error was:
>
> svnadmin: E160013: File not found: transaction '16289-ckh', path 'branches/second/dir/datafile'
>
> And looking up the history for that file, I see that "datafile" was added on branch "first" but the path "branches/first/dir" is already in my filter list. So why didn't svndumpfilter throw me an error on this like it did for a lot of other cases?
> Since the load process it so much slower, the turnaround time for each error in that step is beyond painful, so if there's anything that I can do to assure that this gets caught by the filter would make my life a lot easier.

I don't know the answer to that, but:

> The syntax I used:
> svnadmin dump -q MYREPO | svndumpfilter exclude --targets filterfile > filterdump
> svnadmin load -q --no-flush-to-disk --force-uuid -M 2048 --bypass-prop-validation ./NEWREPO < filterdump
>
> (I had to use the bypass-prop-validation due to some newline issues in old log message, similar to this one https://groups.google.com/forum/#!topic/subversion_users/P3ohZ-hKhCA, don't know why they have wrong newlines, but the repo works as it is now...)

Instead of ignoring wrong newlines, you could fix them using svndumptool (using its eolfix-revprop command), originally at:

http://svn.borg.ch/svndumptool/

Newer fork at:

https://github.com/jwiegley/svndumptool

> An additional question about what Johan wrote below:
>> - You can perfectly well use a 1.10 version of svnadmin or svnsync (or svnrdump, to create
>> a dumpfile from a remote server) to interact with a 1.8 server / repository.
>
> Can I even do this with "svnadmin load"; I thought that would use an FSFS version 8 while 1.8 should have 6? I got that impression from my "research", but I'm probably off base.

If you use a newer version of svnadmin (than the one that will be used to serve the repo) to create the new repo and load the dump file, then make sure you pass the right --compatible-version argument to svnadmin create.
Received on 2018-10-10 09:16:46 CEST