The reported issue is that multiple properties are changed on a single node, svnrdump does not produce
the correct output, and 'svnadmin load' subsequently chokes on this output.
However, in attempting to write a test for this issue, I ran across an assertion in svnrdump itself which
appears to be very easy to trigger on common scenarios. I've not yet gotten to to bottom of it, but will
shortly commit the test and dumpfile which trigger this assertion in svnrdump itself.
The original report and reproduction recipe are described in this mail:
http://svn.haxx.se/dev/archive-2011-03/0661.shtml
Major