svndumpfilter vs svnadmin

Hi, I have a repository that ends up as 2479097336 bytes when dumped. I need to
filter some stuff using the svnadmin dump command so I tried making a long
pipeline and got some messages saying

svn: Unsupported dumpfile version: 3

Did this by hand.

svnadmin --version
svnadmin, version 1.1.1 (r11581)
    compiled Jan 10 2005, 13:12:10

Copyright (C) 2000-2004 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).

svndumpfilter --version
svndumpfilter, version 1.1.1 (r11581)
    compiled Jan 10 2005, 13:12:10

Copyright (C) 2000-2004 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).

  head filtered.dmp orig.dmp
==> filtered.dmp <==
SVN-fs-dump-format-version: 3

UUID: a7bc1bb3-9edd-0310-bf06-f611768c3a79

Revision-number: 0
Prop-content-length: 56
Content-length: 56

K 8
svn:date

==> orig.dmp <==
SVN-fs-dump-format-version: 2

UUID: a7bc1bb3-9edd-0310-bf06-f611768c3a79

Revision-number: 0
Prop-content-length: 56
Content-length: 56

K 8
svn:date

so it seems that I have svnadmin v1.1.1 and svndumpfilter v1.1.1 and the latter
will not read the result of it's own output. Is that a stupid bug or a stupid me?

How can I filter my database to remove multiple items? Can I do
cat orig.dmp | svndumpfilter exclude path1 exclude path2

What will be the effect of using a version 3 dump as input to svnadmin load?
Will I forever lose the chance to do filtering?

I do not want to upgrade right now. I'm on a freebsd 4.10 system and we're using
the repository pretty intensively right now so down time will have to be delayed.

-- 
Robin Becker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org