Everyone can disregard this issue. I discovered that the os400 port is not
quite dead, and there is a new binary to address changes IBM made to their
Apache server.
Yesterday I received approval to move SVN on to a platform that is still being
maintained. I tried to do a dump via svnadmin on the current install and it
gives the same error.
Then it should be reproducible via our own svn (or svnadmin, or svnlook)
too.
Justin Taylor wrote on Tue, Apr 09, 2013 at 14:23:44 -0500:
> Since the Subversion trouble started with the server updates, and different
> clients are receiving the same error, I made the (possibly erroneous)
> assump
