Is svnadmin load affected by hooks?

[Bo Berglund]

When I load a dump into an empty repo, will the operation be affected
by the hooks I have already set up for svnsync?
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.

[Eric Johnson]

Hi Bo,

Post by Bo Berglund
When I load a dump into an empty repo, will the operation be affected
by the hooks I have already set up for svnsync?

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.

Post by Bo Berglund
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.

Eric.

[Bo Berglund]

Post by Eric Johnson
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?

Post by Eric Johnson

Post by Bo Berglund
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.

[Eric Johnson]

Hi Bo,

Post by Bo Berglund

Post by Eric Johnson
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?

Yes.

Eric.