Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm trying to learn how to migrate a Subversion repo, and am running into an issue that doesn't make sense to me. I've used svndumpfilter to split out a sub-project, and have removed some path prefixes. Several hundred commits now import correctly, but then I'm getting the following error:

<<< Started new transaction, based on original revision 19190
     * editing path : branches/features/DynamicSource ... done.
     * editing path : branches/features/DynamicSource/src/build.properties ... done.
     * editing path : branches/features/DynamicSource/src/client/default.htm ...done.
     * editing path : branches/features/DynamicSource/src/client/js/AdHocController.js ... done.
     * editing path : branches/features/DynamicSource/src/client/js/Report.js ... done.
svnadmin: E160006: No such revision 19098
     * adding path : branches/features/DynamicSource/src/client/js/Enums.js ...

OK, so I go into the dump file to look at revisions 19190 and 19098. First of all, revision 19098 does exist in the dump file and was imported without a problem. Revision 19190 is a merge. Within 19190, here's that last file's info, which seems to be causing the issue:

Node-copyfrom-rev: 19100
Node-copyfrom-path: trunk/src/client/js/Enums.js
Text-copy-source-md5: 2db7f8d9c0ba4750d88ce0722731aad6
Node-path: branches/features/DynamicSource/src/client/js/Enums.js
Node-action: add
Text-copy-source-sha1: 8f930509f8dbc17c5e82cd40aa5a76454d3d812c
Node-kind: file
Content-length: 0

Confusingly, revision 19100 does NOT exist in this filtered file. But the error's not referring to 19100, it's referring to 19098!

What do I do to get this file to load?


share|improve this question
If something complicated ("dump and filter" followed by "import") fails, try something simpler first ("dump", then "import"). I only ever migrated a whole repo, and that went easy-peasy. –  Dirk Eddelbuettel Aug 29 '13 at 13:39
Thanks, Dirk. We really do have to split this repo up, though. –  Harlan Aug 29 '13 at 13:40
Maybe do "Dump, Import. Hand-reduce, Dump again. Import 2nd Dump." ? –  Dirk Eddelbuettel Aug 29 '13 at 13:41
Unless I'm missing something, I don't think SVN works that way. You have to reduce using the dump file and svndumpfilter. And we do want to keep history, as much as possible. –  Harlan Aug 29 '13 at 14:08
Why not migrate to git or mercurial, and get rid of the legacy SVN in the same step? –  vonbrand Jan 24 '14 at 17:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.