GitHub no longer supports updating a GitHub hosted script via SVN.
This can create problems when KoLmafia attempts to update all of the SVN scripts.
To keep the "update all" functionality from failing (and stopping other things) it should be disabled by changing the GLOBAL setting svnUpdateOnLogin to false. Then use the Scripts menu to update the scripts of your choice manually and individually. This is definitely an inconvenience for users of some scripts that have always been hosted on SourceForge and updated via SVN but that is not going to be fixed anytime soon.
The cli command "checksvngit" can be used to identify scripts that are hosted on GitHub but installed via SVN. Some of these scripts have been "migrated" and are now using git. If that seems to be the case then the SVN version should be manually uninstalled and the git version manually installed. A user can choose to manually install a GitHub script via git (after uninstalling the SVN version) but this may break updating if the author makes some decisions about hosting.
The cli command "checkrepo" might also be useful as it attempts to identify scripts that have been installed by both git and SVN.
This can create problems when KoLmafia attempts to update all of the SVN scripts.
To keep the "update all" functionality from failing (and stopping other things) it should be disabled by changing the GLOBAL setting svnUpdateOnLogin to false. Then use the Scripts menu to update the scripts of your choice manually and individually. This is definitely an inconvenience for users of some scripts that have always been hosted on SourceForge and updated via SVN but that is not going to be fixed anytime soon.
The cli command "checksvngit" can be used to identify scripts that are hosted on GitHub but installed via SVN. Some of these scripts have been "migrated" and are now using git. If that seems to be the case then the SVN version should be manually uninstalled and the git version manually installed. A user can choose to manually install a GitHub script via git (after uninstalling the SVN version) but this may break updating if the author makes some decisions about hosting.
The cli command "checkrepo" might also be useful as it attempts to identify scripts that have been installed by both git and SVN.