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

Re: svnadmin and svndumpfilter version inconsistency

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-11-26 00:41:26 CET

Richard Musil wrote:
> Hello all,
> I have found funny bug in svndumpfilter (or svnadmin). svnadmin dump
> produces dump with version 2 (SVN-fs-dump-format-version) written in the
> file header, svndumpfilter produces filtered dump with version 3. When
> using already filtered dump as an input to another svndumpfilter pass,
> svndumpfilter emits error about dump version and quits. So basically,
> filtered dumps cannot be used with svndumpfilter again.

That's a bug. I'm writing up a description for our issue tracker right now.
Thanks for the report.

> Another problem I am facing with svndumpfilter is when I try exclude
> some projects. Even I have 'Node-path: work' with 'add' in svn-dump, I
> cannot filter it out with exclude. Instead I am getting error:
> svn: Invalid copy source path '/work'
> I presume it might be related to the fact, that there is also /Work
> folder in the repository (which, btw, I do not want to filter out) and
> the case may conflict some processing. Other paths which do not have
> case insensitive twin filter out fine.

Would you be able to provide a simple example dumpfile and svndumpfilter
command line to illustrate this? I'm not entirely clear on exactly what is


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 26 00:42:45 2004

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

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