On Saturday 29 October 2005 13:29, bt c wrote:
> Ok, what I just did was:
>
> svnadmin dump repo -r1:62 --incremental > repo_1to62.dmp
> svnadmin dump repo -r64:157 --incremental > repo_64to157.dmp
> // Rename repo to something else.
> svnadmin create repo
>
> svnadmin load repo < repo_1to62.dmp
>
> svnadmin load repo < repo_64to157.dmp
>
>
>
> My understanding is that I will not know what are the changes from 62 to 63
> now. Instead I am seeing only changes from 62 to 64 now.
Correct. Don't forget to get a whole new WC though. Since the version
numbers changed, you're old working copy is now out of kilter with what is
actually in the repository.
> John, I appreciate your offer to help. As I am focusing my efforts on some
> other developments and do not wish to be sidetracked, and also that I can
> afford to lose the changes, I decide to go ahead with the quick solution.
> Maybe you can list out the steps that you will take in addressing this
> problem here?
It can be a bit tedious. In order to let the checkout proceed, we would have
needed to identify the problem file (which should've been in the error
message for your checkout). The we could've opened revision 63 in a hex
editior (repos/db/revs), found the appropriate representation for the file,
and changed the md5sum to all 0's (all 0's is our wildcard value for the
checksum... it matches everything). After that, you should've been able to
checkout again. The only question would have been whether the data in r63
was valid.
Hope that helps.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Oct 30 00:23:30 2005