On Thu, 29 Mar 2018 10:23:34 -0700, Eric Johnson <e...@tibco.com> wrote: >On Wed, Mar 28, 2018 at 8:17 PM, Bo Berglund <bo.bergl...@gmail.com> wrote: > >If you're dumping into an empty repository, that typically resets the >repository UUID to match that of the dump file. Changing the UUID will >break the sync.
Gosh, that was unfortunate! I have just completed the local load operation for all repos. If the UUID will block the subsequent synchronize (which I have not come to yet but is next on my list), then this is also all in vain... But to be on the other side if I can use svnadmin setuid <repo path> to I get a fresh uuid on all of them, maybe that will make it work for sync after all? >> I have created dumpfiles for all 9 repos I want to sync, and now I am >> about to load these into the repos I had prepared for sync when I >> discovered that network problems interfered. >> > >svnadmin load takes the options "--use-pre-commit-hook" and >"--use-post-commit-hook". Assuming you're using your post-commit hook to >trigger the calls to sync, you could pass that flag. That seems weird to >me, though, in that such an approach would trigger a sync request per >loaded commit. I was just worried about the hooks interfering with the load operation. I have no need for them at all in that situation, but they will be used during synchronize. And I used no extra arguments to the load command. -- Bo Berglund Developer in Sweden
