See https://github.blog/2023-01-20-sunsetting-subversion-support/
When exactly will this happen?
The 8th of Jaunary 2024.
Who does this affect?
KoLmafia supports
Script authors should update their instructions to use those commands instead (remember if a script is hosted on GitHub, the command is as easy as
Script users should expect to no longer receive automatic updates via
Okay, but in more detail?
This section by Ryo_Sangnoir
As a user, if you run the command
As an example, suppose you see "https://github.com/Loathing-Associates-Scripting-Society/philter/trunk/release" in the output of that command. If you go to "https://github.com/Loathing-Associates-Scripting-Society/philter", you'll see that the README contains a "git checkout" command, so you can run
As an author, what you do depends on where your "scripts", "relay" etc. folders are.
aaAAH?
Aaa! It's not a big deal, but it may make some older GitHub scripts less easily accessible. If they're not regularly updated enough to fix this issue in one whole calendar year, you're not really missing out on anything because this only breaks updates.
When exactly will this happen?
The 8th of Jaunary 2024.
Who does this affect?
- Authors of scripts who host them on GitHub and advise they are installed using
svn checkout - Users of the above scripts
KoLmafia supports
git as well as svn for checking out and updating hosted scripts.Script authors should update their instructions to use those commands instead (remember if a script is hosted on GitHub, the command is as easy as
git checkout <user>/<repo> [<branch>] since we assume GitHub if a full URL is not provided). You may be interested in the manifest.json file support. Lots of this isn't on the wiki, so we will endeavour to rectify that in due course.Script users should expect to no longer receive automatic updates via
svn update after the 8th of January 2024. They can try deleting the script via the svn delete command and installing again via git checkout, but that may not always work without the author having updated their code.Okay, but in more detail?
This section by Ryo_Sangnoir
As a user, if you run the command
js svnList().map(s => svnInfo(s)).map(i => i.url).filter(i => i.includes("github")) in the Graphical CLI, you can see which SVN scripts you have installed that are on GitHub. If you look at their README file in the root of the repo, you may be able to install these using git instead. If not, you may be able to install them using git checkout <user>/<repo> <branch> if they keep the release code in a separate branch. If not, you will have to raise the issue with the author, or use a fork.As an example, suppose you see "https://github.com/Loathing-Associates-Scripting-Society/philter/trunk/release" in the output of that command. If you go to "https://github.com/Loathing-Associates-Scripting-Society/philter", you'll see that the README contains a "git checkout" command, so you can run
svn delete philter followed by git checkout https://github.com/Loathing-Associates-Scripting-Society/philter.git main.As an author, what you do depends on where your "scripts", "relay" etc. folders are.
- if they're in the root directory of branch "my-scripts", tell your users to run "git checkout <user>/<repo> my-scripts"
- if "my-scripts" is the default branch of your repository, you don't have to provide it, but you probably should as it'll affect the id of the installed script, which will affect what gets installed when your script is installed as a dependency
- if they're in some directory deeper into the repo, you'll have to add a "manifest.json" file in the root of the repo (on the branch you tell your users to install), with the contents
Code:{ "root_directory": "<where_the_files_are>" }
aaAAH?
Aaa! It's not a big deal, but it may make some older GitHub scripts less easily accessible. If they're not regularly updated enough to fix this issue in one whole calendar year, you're not really missing out on anything because this only breaks updates.
Last edited by a moderator:
