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

Svndumpfilter produces incompatible dumpfile?

From: Scott Hughes <Scott.Hughes_at_dalsemi.com>
Date: 2004-11-16 01:16:49 CET

Hi all. New subversion user who is migrating a very large repository over.
Right now, I'm getting headaches from svn dump/filter/load. I have a dump
file with the following header:

  SVN-fs-dump-format-version: 2

Svndumpfilter will parse this dump file fine, and give me a new dumpfile
with the following header:

   SVN-fs-dump-format-version: 3

In case it matters, I was including a single path and I used the
--drop-empty-revs. Passing this new dumpfile to another instance of
Svndumpfilter causes it to bomb:

   svn: Unsupported dumpfile version: 3

I double-checked the documentation and can't see anywhere that would suggest
what the problem is or if it's design intent (i.e. can't filter twice).
I've tried with version 1.1.1 (r11581) on Fedora Core 2 and version 1.1.0
(r11180) on WinXP.

Incidentally, it would fix my problem if I could specify multiple include
and exclude statements on a single svndumpfilter command. I want to include
a path with a lot of subdirectores, but exclude just a few of them, i.e.:
   svndumpfilter include p/y exclude p/y/q p/y/w p/y/z

I'm guessing as it's written above, it's an "include" list of {"p/y",
"exclude", "p/y/q", etc}. I'm open to trying other ways of doing what I
want, but my dumpfile is way too big for experimenting.

Scott Hughes - Engineer
shughes aht dalsemi daut com 
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 16 01:17:52 2004

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.