RE: subversion load fails with “no such revision”
From: Tony Sweeney <tsweeney_at_omnifone.com>
Date: Fri, 30 Aug 2013 15:26:16 +0000
There are at least four different versions of dumpfilter floating about the aether. It would help to know which one you used, and how you used it.
I still haven't been able to make any progress on this. If ServerFault and this mailing list aren't going to be adequate to solve the problem, could someone suggest an alternative? Thanks,
On Thu, Aug 29, 2013 at 8:21 AM, Harlan Harris <harlan_at_harris.name<mailto:harlan_at_harris.name>> wrote:
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
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:
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?
No virus found in this message.
This is an archived mail posted to the Subversion Users mailing list.