minimal-revision option will add corresponding configuration option to the generated SubGit configuration file, so that subsequent import will start from that minimal revision. This will make the import to start since that revision, but I’m afraid this won’t help on the configuration stage (actually, this r17572 revision may also be affected during import, depending on the branches configuration as SubGit may translate configured branches history beyond the minimal revision in some cases).
You’re probably right about timeout, especially if there’s no delay prior to the fault, but still, this issue happens when the network communication is broken. It might be caused by timeouts, but it might as well be caused by other limitations, such as number of bytes transferred. Lack of permission might also be the cause, by the way, it would worth to check it as well, I assume.
Honestly, I didn’t get you mention about upgrade: did you mean you tried to upgrade SVN version on your server? What is the buggy revision that prevents the upgrade from success, is that the same r17572? And which way you tried to use to import the repository to VisualSVN, dumping and importing the repository or some other way?
So, as I mentioned, on way to resolve the problem is to resolve the very problem that causes the network interruption, yet it’s not clear to the very end what it actually is. Also, the issue might be worked around – one way is to use another protocol but
http, for example,
ssh, those are not apt to issues like this one. Also, it’s possible to use
file:// protocol if it’s allowed to run SubGit on the same machine where SVN resides – in fact, this would be the best way as the network is fully excluded and protocol overhead is minimal. Another possible way is to not to use
layout auto option during the configuration creating the standard configuration instead – in this case SubGit won’t scan the repository history and thus won’t hit the issue. To not to hit the issue during the import, SubGit may be set to use http spooling:
httpSpooling = true
but I must say this way does not 100% guarantee the resolution as, for example, if that is permissions issue, then it’ll still be there.