Harlan Harris <harlan.harris_at_gmail.com> writes:
> 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,
Splitting up repositories is not trivial and it is not clear, to me at
least, exactly what you are doing.
>
> On Thu, Aug 29, 2013 at 8:21 AM, Harlan Harris <harlan_at_harris.name> wrote:
>
>> Hi. This is crossposted from ServerFault<http://serverfault.com/questions/534553/subversion-load-fails-with-no-such-revision>.
>> I'm not subscribed to this list, so a cc would be appreciated. (Or feel
>> free to just respond on ServerFault. So far it's got a couple of upvotes,
>> but no responses.)
>>
>>
>> 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.
That error refers to r19098 in the repository, does that revision exist?
Which revision was created by loading r19098?
>> 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!
Perhaps there is a bug in the load renumbering, but it's hard to say
because it's not clear what you are doing.
You mention "several hundred" but you are dealing with revisons much
higher. How did you produce the dump file? How did you filter it? How
many revisions in the dumpfile? Are they sequential? How many
revisions in the destination repository?
Aside from the renumbering problem, you say that r19098 exists in the
dumpfile but r19100 does not. I don't think there is any way you can
load r19190 if it refers to r19100. A dump may refer to revisions
before the start of the dump but that is not the case here. You have a
reference to a missing revision withing the dump range. What do you
expect load to do?
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2013-08-30 17:10:32 CEST