Following the example on page 88, I am trying to split a repo by creating
separate repos for individual projects in the existing repo. The first steps:
(1) dump the existing repo
(2) svndumpfilter the project you want
work as expected and I can then populate a newly create repo from the
processed dump file of step (2) above.
As the book mentions, one will typically have to modify the node entries
to 're-root' them in the new repository. In my case, I'm using sed to
convert the entries of the original dump:
and also remove the dump data that would create the "documentation"
directory. The resulting modified dump file appears ok and appears to
load properly (it handles revision 1, for example) until it hits the
first binary file at which point the svnadmin load command aborts with
a checksum error on that binary file.
Looking at the dump file I was surprised to see that it is not
"human readable" as the documentation claims. The binary file (in this
case a PDF) is not uuencoded (or some similar method) but included as
8-bit 'raw' data. That, of course, makes it impossible/difficult to
inspect/edit a dump file using an editor.
Still leaves me at a loss why a simple sed script like:
sed 's|^Node-path: documentation/|Node-path: |' < dump1 > dump2
which removes the leading 'documentation/' part from all node paths
would create this error on running 'svnadmin load newrepo < dump2':
started new transaction, based on original revision 1
* adding path : documentation ... done.
* adding path : branches ... done.
* adding path : tags ... done.
* adding path : trunk ... done.
* adding path : trunk/business ... done.
* adding path : trunk/design ... done.
* adding path : trunk/meetings ... done.
* adding path : trunk/presentations ... done.
* adding path : trunk/reference ... done.
* adding path : trunk/reference/DAVIC ... done.
* adding path : trunk/design/DesignBook/DesignBook.pdf ...svn: Checksum mis
match, rep 'a':
Has anyone seen this problem before?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Dec 30 14:33:42 2004