Subversion repository version
Problem: need to upgrade the Subversion repository's version
At times during the development of subversion it has and will be necessary to change the underlying database schema for subversion repositories (libsvn_fs). Thus, if a 'new' libsvn_fs library tries to access an 'old' repository, you'll see an error like:
Expected version '2' of repository; found version '1'
svn: No repository found in '...URL...'
Or if you use an 'old' libsvn_fs library to access a 'new' repository, you might see an error like:
Expected version '1' of repository; found version '2'
svn: Malformed skeleton data svn: Malformed node-revision skeleton
So if you're seeing an error like these you will need to upgrade or downgrade your repository version.
For full details, see: HOW-TO: svn repository upgrade procedure
Solution: need to upgrade the schema
If available, use an svnadmin binary from a release with the same schema version as your repository to create a dumpfile of your repository:
$ mv myrepos old-repos $ svnadmin dump old-repos > dumpfile
Use an svnadmin binary from a release with the same schema version as you want your repository to have to load the dumpfile into a new repository:
$ svnadmin create myrepos $ svnadmin load myrepos < dumpfile