On Thu, 29 Mar 2018 10:34:52 +0100, Philip Martin
<philip_at_codematters.co.uk> wrote:
>Philip Martin <philip_at_codematters.co.uk> writes:
>
>> Bo Berglund <bo.berglund_at_gmail.com> writes:
>>
>>> 2) Use hotcopy to make a backup copy of everything including hooks.
>>> The caveat here is that the hotcopy needs to be using the exact same
>>> version on both master and mirror. But I have 1.9.7 master on Windows
>>> and 1.9.3 mirror on Ubuntu Linux
>>
>> No, hotcopy needs compatible versions. Any version of Subversion is
>> compatible with all older versions, and any 1.N.x is compatible with any
>> other 1.N.y. In your case 1.9.7 and 1.9.3 are compatible.
>
>It's a bit more complicated in practice. Any version of Subversion can
>read/write all the older repository formats and it is the repository
>format that needs to be compatible. So for the hotcopy to be useable on
>the mirror what matters is whether the version of Subversion on the
>mirror is compatible with the repository format on the master.
OK, but I have now created the dump files and transferred them to the
mirror server. On that I had prepared all of the repos for
synchronization and succeeded to do the initial sync on two of them
when I ran into the problem for the 3rd and 4th, which triggered this
last question round here.
Now I am in a situation that I could load the dump files for the repos
I have not tried to sync yet, thus I can use the --allow-non-empty
flag during initialization and get the sync started on a later
revision.
But I have two questions in this regard:
1) Do I have to disable the hooks I put in place for sync during the
load? Or will they not be triggered during a load operation?
2) What do I do about the two repos where I have already run an
initialization command without the flag and where a number of
revisions have already been transferred before the error?
If I erase these repos and recreate them empty can I repeat the
initialization command with the non-empty flag and it will work? Or is
the fact that the initialization has been already executed without the
flag on these two master repos place them in limbo?
Can an svnsync initialize command be undone?
I don't want to rename the mirror repo to something different...
--
Bo Berglund
Developer in Sweden
Received on 2018-03-29 14:08:25 CEST