SvnDumpFilter 2,3: Error parsing header. How to fix?
Posted
by flashnik
on Stack Overflow
See other posts from Stack Overflow
or by flashnik
Published on 2010-05-04T07:35:38Z
Indexed on
2010/05/04
7:38 UTC
Read the original article
Hit count: 346
I use SVN from Collabnet, 1.6.9 version. I tried to separate my project on two parts with SvnDumpFilter and encountered an error because some folders (includeing the one I want to separate) had been moved. Then I googled that SvnDumpFilter 2 and 3 can solve this problem. I tried to use them but in both cases encountered an error: Error parsing header.
Here is the beginning of source dump:
SVN-fs-dump-format-version: 2
UUID: REP_GUID
Revision-number: 0
Prop-content-length: 56
Content-length: 56
K 8
svn:date
V 27
2008-10-28T07:01:45.445155Z
PROPS-END
Revision-number: 1
Prop-content-length: 151
Content-length: 151
K 7
svn:log
V 48
?±???·???µ??-?‡?°???‚??, ?????‚?????°?? ?±?‹?»?°
K 10
svn:author
V 8
flashnik
K 8
svn:date
V 27
2008-10-29T20:18:56.633888Z
PROPS-END
Node-path: Foo
Node-kind: dir
Node-action: add
Prop-content-length: 10
Content-length: 10
PROPS-END
Node-path: Foo/Bar
Node-kind: dir
Node-action: add
Prop-content-length: 10
Content-length: 10
PROPS-END
Node-path: Foo/Bar/example.doc
Node-kind: file
Node-action: add
Prop-content-length: 59
Text-content-length: 181248
Text-content-md5: f14c77a031ab2de001ac5239427ceded
Text-content-sha1: 95470e8d29bf76b00485c4fa33f4029f5c2386cb
Content-length: 181307
K 13
svn:mime-type
V 24
application/octet-stream
....Some binary code and so on
SvnDumpFilter3 produces following part before dying:
SVN-fs-dump-format-version: 2
UUID: REP_GUID
Revision-number: 0
Prop-content-length: 56
Content-length: 56
K 8
svn:date
V 27
2008-10-28T07:01:45.445155Z
PROPS-END
Revision-number: 1
Prop-content-length: 151
Content-length: 151
K 7
svn:log
V 48
?±???·???µ??-?‡?°???‚??, ?????‚?????°?? ?±?‹?»?°
K 10
svn:author
V 8
flashnik
K 8
svn:date
V 27
2008-10-29T20:18:56.633888Z
PROPS-END
What's wrong? How to fix it? Does it work with my subversion version?
© Stack Overflow or respective owner