Yep, relocate is what you should be using.
Switch is for moving the root path within a larger repository.
Relocate is for changing the URL for the entire repository.
svnThreadPoolSize=5 worked for me. 1 is slow.
Did svn update used to update scripts that were moved into folders under the scripts folder? I try to add a little bit of organization since there are so many.
(apparently, you can spell svn relocate as svn switch --relocate ? or maybe it's just that the second command can do both things at once?)
I never had any reason to use switch and the last time I used relocate was many years ago. The new hotness for my employer has been git for the past few years. That has very different complications.
It is user configurable for a reason and the best answer for any system is the highest number that does not trigger Sourceforge to reject connections.
Update All traverses the svn subdirectory in the mafia directory tree and updates everything there. AFAIK I did not change the behavior where mafia fetches an update and then pushes it to scripts or elsewhere. What would be most helpful would be to a) confirm that something is broken; b) write a detailed bug report so that I can reproduce it locally; and c) make sure I know about it. If I really broke something I accept responsibility for fixing it. :-)
Since we are using that code, prudence dictates some investigation and experimentation. "First, do no harm." seems to apply.Users who have used svn switch on some of their project should not use this.
I will confess that I am not too worried about changing https: to svn: on legacy scripts. The thread pool provides an absolute upper bound on the number of simultaneous Sourceforge connections. The exact number does depend upon protocol but the existence of a user configurable bound does not.
I think the repository URL is "embedded" in the local working copy and the KoLmafia always goes to the working copy to get update info. So I think it would be safe to replace all the https: with svn: for SouceForge links in our json file. AFAIK that will have no impact on people who have already installed and all new installations will use the friendly protocol.
There are ash commands that will display the URL so users with "legacy" URLs could follow my procedure and delete and check out or someone can see whether we exposed some kind of relocate command and how well it works :-)
1) updated and built mafia from current svn
2) installed current tortoisesvn (1.10)
3) upgraded all my mafia/svn/ script directories (to workspace version 1.8)
4) relocated them all from https://... to svn://...
5) ran mafia and did "svn update" in it
All scripts checked revision and updated without any error. It was slow, but that might be because the thread pool is only 2.