politas

Looks like something is messed up in your CKAN/registry.json on line 287340

Sorry about that. PRs for your mods were submitted by someone outside the team, and it looks like we all forgot to ask whether that person had cleared it with you. All removed now.

Your licence string needs to be "public-domain". That's what's failing. The best way to get feedback on a new netkan is to submit a PR. The Jenkins checks will sometimes give you a better error message than the netkan client by itself.

There was an attempt to do it with a plugin, but it was extremely unreliable and has long since been abandoned. It goes against one of the core promises of the CKAN client, that CKAN will not touch any file it has not installed, which is why it isn't in the main client and likely never will be. If someone can get a working plugin to convert AD mods to CKAN control without requiring reinstallation, we'll promote the heck out of it, though!

If there aren't going to be any new releases on the old name/identifier, just freeze it. (rename the .netkan file to .frozen) No particular reason. They take some time to look over and process, and none of us have had the time or enthusiasm to do so. Merged with thanks!

This is correct. The CKAN client does not touch any files it did not install.

ResearchBodies should be right, now.

The author of TRR has made it clear that they do not want TRR on CKAN yet. We will respect their wishes. There's not a huge point in updating WindowShine just to make it disappear from CKAN.

Thanks for getting involved! That's mostly pretty good, but it's going to install all of the mutually exclusive options at the same time. We'll need separate NetKAN entries for each option.

Hi Kobymaru, sorry about that. The Netkan robot hasn't been looking at your AVC data. Fixing that now. The file you download is not an installer; it's the program. The prompt you are getting is asking you to tell CKAN where your KSP installation is.

That feature is being worked on. In the meantime, you can get the same result by replacing the "downloads" folder in each KSP instance's CKAN directory a symlink to a single shared location.

The easiest way for a mod author to force a file to be deleted by CKAN is to include a dummy blank file in the distribution. I think an "apt purge" equivalent would require mod authors to meet CKAN specifications in a way that I just don't see happening, or significant levels of effort by CKAN metadata maintainers beyond "does this put all the included files in the right places".

It first deletes all the previously CKAN-installed files, deletes any empty directories, then installs the new files, creating directories as required. If a mod has created any extra files at (game) run-time, they are untouched.

In the GUI, it's File - Select KSP Install, which brings up a dialog box that lets you add, remove and choose KSP instances, including setting a default instance to open on launch. On the command line, you can perform operations on the non-default instance by using the `--ksp` option (as opposed to the `ksp` subcommand), for example: ckan.exe install <modname> --ksp <name> The question of being able to set a download location is one that I'm working on currently (my first attempt was a complete disaster, so it may be a while) Hopefully, that'll be in the next release! Symbolic links are a functional workaround on all platforms, to my understanding. You mean the KSP log files? I suppose we could make an attempt to archive the current log when you launch KSP from within the CKAN GUI client. If you think that would be useful, please raise a feature request on GitHub

No, it doesn't, from my understanding. If you have some code experience, and can think of a way to do it without breaking what it does, we welcome contributions! https://github.com/KSP-CKAN/NetKAN-bot is the specific repo. I don't know Perl at all, so I only know how it works by what I've been told.

Have you got the latest CKAN 1.22.3? Yep, it would be useful, but given the way that our automatic indexing of new updates works, that information is just not available for the client. We'd need to maintain a whole separate data structure in order to compare the new repo data with past repo data, and then the client would need to spend time comparing every mod's current release with what it last knew as the current release, working out what to do with that information,... We'd basically need to program an AI to do what we do keeping the repo up to date so that it can understand some changes. I know that it seems like an easy thing to do, but trust me, it really isn't. If it was easy, we'd have done it by now. If you have deleted everything in your GameData folder (other than the Squad folder, obviously), then you shouldn't be getting any AD mods. I know I sound like a broken record, but try a Clean & Reinstall. (Or the relevant parts of it) It really does solve most problems in the CKAN client.

Once the mods are fixed on Curse and the CKAN metadata updates, a Clean & reinstall will get the correct versions on all mods installed. (Or you can just uninstall and reinstall the specific mods) If the metadata is controlled by us rather than the mod author, we can also add an override to force the correct mod compatibility util Curse gets around to fixing it, and you can force installation of a particular version of a mod using the command line by saying: ckan.exe install <Modidentifier>=<version> (Make sure you get the full version string and the mod identifier from the mod details)

I'm pretty sure that a Clean & Reinstall will sort that out Ok, I'd closed the PR so it won't get added to CKAN. As far as the TechTree config, I'm not sure where to get help for that, but this thread is probably not the best for it.

You'll have to talk to the Spacedock folks. I believe they can turn it off. What's your mod's name? I'll delete the auto-generated PR if you would rather it is not listed. You mean the Squad mod that is now part of stock? You should just uninstall it. It's in stock, now.

There's a missing comma in the .version file that's holding up CKAN update - https://github.com/CYBUTEK/KerbalEngineer/pull/129

Hi, just popped in to let you know that the current versions of KerbinSide should now be available in the CKAN! If anyone can test the installation and let me know if there are any issues, that would be helpful. I've never used much of KerbinSide other than the Air Race.

Ah, I see what's gone wrong, there. USITools min_version is "v0.9.0.0" in USI-Core, but there are no "v"s in the USITools version numbers. https://github.com/BobPalmer/CKAN/pull/26 should fix it.

There's a "name" and an "identifier". Identifiers have no spaces, and relationships are all defined using the identifiers. If you're getting weird "Module Not Found" errors that make no sense, it means there's an difference between your registry.json and the data in the repo that is confusing the CKAN client. The Clean & Reinstall process is the best way to fix it.

The CKAN AVC Transformer will only increase compatibility, not decrease it, so the compatibility from Curse gets turned into the minimum version.