Roland Besserer wrote:
...
> 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.
Well, I guess our interpretations of "human-readable" differ.
Personally, I think that uuencoding (or similar) doesn't increase
human-readability, it just wastes processing time.
> That, of course, makes it impossible/difficult to
> inspect/edit a dump file using an editor.
Get a better editor, then.
> 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':
> expected: 225d1ed316bf0830dbdd6c50ff1e79e7
> actual: f41751bce1f5fe359351df3a9b37be30
>
>
> Has anyone seen this problem before?
Looks fairly obvious that the implementation of sed you are using is munging
the data in some way.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 30 11:48:35 2004