politas

Is anyone getting these "Too many mods provide..." errors on Linux? Just trying to chase down where the problem is.

New CKAN Release v1.22.5 "Xichang (西昌)" Changes since 1.22.4 Bugfixes [GUI] Fix crash on startup (#2138 by HebaruSan; reviewed: Olympic1) [Core] Fix exception installing some mods (#2137 by HebaruSan; reviewed: Olympic1) Notes Windows users must have .NET 4.5 installed. libcurl is no longer used by CKAN for Linux or Mac. If you experience problems downloading, please contact us Mac/Linux/Mono users: please use the new cert-sync tool, to update mono's certificate store. Mac Users: There is a MacOS CKAN App launcher available thanks to the wonderful Maxzhao. This release of the CKAN has not been tested on Mono 3.2.8. We highly recommend upgrading to the latest stable release of Mono from mono-project.com You will need the equivalent of the mono-complete package for your OS. Release image CC-BY-SA, courtesy CGWIC Once again, we've had to rush out a quick urgent bug-fix release. Excellent work by @HebaruSan identifying and fixing the bugs so quickly!

I don't understand why you people want to run CKAN as administrator. It is indicative that you have some serious issues with permissions on your PCs, that are not CKAN's fault. You should not be running CKAN as administrator!!!!!!! CKAN is not "installed" in the sense of a regular Windows app; it is simply an executable file that you run as required. Your ordinary user account should be able to run such executables on your own machine. Save ckan.exe in your user directory and run it from there. If it doesn't prompt you to select your KSP installation, open up RegEdit, Go to CurrentUser\software\ckan and delete everything, then try again, adding your KSP installation from scratch (select the BuildID.txt file, not the folder) You should not be running CKAN as administrator!!!!!!! You should not be running CKAN as administrator!!!!!!! You should not be running CKAN as administrator!!!!!!! I don't know how seriously I can stress this. I believe CKAN is a safe application, but you are giving your entire computer over to an unsigned program downloaded from the Internet. This is such a bad idea that I am frankly astounded that anybody even considers it!

It's still being built. Should be there in a few minutes. Ignore the .zip unless you want to build the code from scratch. CKAN 1.22.3 had a new record for us of 145,936 client downloads, which as was noted earlier in the thread, pushed us over 1 million total downloads! Massive, massive thanks to the great @pjf and every other CKAN contributor individually and collectively, and especially to all of you users for putting your trust in us to look after your precious KSP installations! I am awed and humbled by it all. Sorry for the delay. The ckan.exe file is there now!

New CKAN Release - v1.22.4 "Uchinoura" Japanese M-V rocket with Astro-E satellite in Uchinoura Space Center, Japan Changes since 1.22.3 Bugfixes [GUI] Update Forum Thread link to new thread (#2079 by: politas; reviewed: linuxgurugamer) [core] Move downloads outside of gui transaction (#2073 by: archer884; reviewed: politas) [CLI] Fix crash in "ckan available" with curly braces in mod name (#2111 by: HebaruSan; reviewed: politas) [core] Check grandparent+ directories for find and find_regexp (#2120 by: HebaruSan; reviewed: politas) [core] Add test to cover missing directory entries (#2125 by: HebaruSan; reviewed: politas) [Build] Fix build.ps1 script failing when spaces exist in source path (#2121 by: ayan4m1; reviewed: dbent) [core] Perform directory root comparison in case-insensitive way (#2122 by ayan4m1; reviewed: politas) [Build] Expand .gitignore to handle packages in subdirectories and build output (#2116 by ayan4m1; reviewed: politas) [GUI] Allow uninstall of incompatible mods in GUI (#1929 by ayan4m1; reviewed: politas) [core] Loop to find max KSP version instead of assuming ordering (#2131 by hebaruSan; reviewed: politas) Features [GUI] Quit on ctrl-q and alt-f,x (#2132 by hebaruSan; reviewed: politas) Notes Windows users must have .NET 4.5 installed. libcurl is no longer used by CKAN for Linux or Mac. If you experience problems downloading, please contact us Mac/Linux/Mono users: please use the new cert-sync tool, to update mono's certificate store. Mac Users: There is a MacOS CKAN App launcher available thanks to the wonderful Maxzhao. This release of the CKAN has not been tested on Mono 3.2.8. We highly recommend upgrading to the latest stable release of Mono from mono-project.com You will need the equivalent of the mono-complete package for your OS. Release image public domain, courtesy NASA A sudden flood of bugfixes has pushed me to release a new version of the CKAN client (to be fair, a few of them have been in the dev branch for some time) Ayan4m1 is back from hibernation, and making some great contributions, but I have to give special props for this release to @HebaruSan, who has been making some great contributions both in code and metadata, and has joined the CKAN team. An excellent first contribution also by archer884, moving downloads outside the timed transaction for installs, which should prevent a few issues where a transaction fails simply because a download is slow.

We welcome plugins, and have a plugin API available. Believe me, I'm completely with you on manual maintaining of mods being infeasible for large mod collections (though there are a few people who insist that it is not a problem and all, and don't understand why anyone feels the need for the CKAN. I generally try to ignore those people. There has been a past attempt to write a plugin to get CKAN to take over a set of manually installed mods, which was not successful. If someone can figure it out, we'd welcome a plugin or code contributions!

That's a definite error. EarnYourStripes 1.2.0.1 in the CKAN metadata is only marked as compatible with KSP 1.3.1 It may have accidentally had wider compatibility at an earlier stage? That's really hard for us to prevent, I fear, when we scrape the data from an author-supplied KSP-AVC .version file.

Mod authors are generally focused on ensuring support for the latest KSP release. I think assuming that a new mod release will work with older KSP releases (as opposed to relying on what the mod author specifies in a KSP-AVC .version file) is fraught with danger I would say if the notes on a release only say "recompiled for KSP 1.3.1" you can assume that a) the previous version doesn't quite work with 1.3.1 and b) there is no real change in functionality between the two releases. If I was fixing up any metadata with such information, I'd cap the ksp_version_max of the previous release to 1.3.0, and set the ksp_version_min of the new release to 1.3.1. Staying with an older KSP version means increasing stability of your mod platform. You'll slowly get less and less mods' latest releases being marked compatible. Getting the KSP compatibility details correct is a significant chunk of the manual edits we do to CKAN metadata. The more people report any cases where the CKAN metadata is either too permissive or not permissive enough, the better we can make the data.

Those are the KSP-AVC rules. CKAN operates a little more loosely. Some mod releases have just a ksp_version_min, because the mod authors feel the interfaces they are using are intended to be stable. Also, in CKAN metadata, ksp_version is not required for min/max; they are treated as alternatives. The full CKAN spec is here. Possibly the biggest issue CKAN has with KSP compatibility is Spacedock mods that have no KSP-AVC .version files. Spacedock does not support multiple KSP release compatibility, so mod authors are forced to select, say, 1.3.0, even if what they want to say is 1.3.

Hi there! You've requested this mod be added to CKAN using the Spacedock interface, but the way you've written this mod, it can't be installed via CKAN. The proper way to apply SigmaDimensions settings is to use ModuleManager patches, as described in the SigmaDimensions README.md file.

That's not quite correct. The "Max KSP" value is drawn from the most recent version of a mod, not the installed version. It will show you which of your installed mods are ready for an upgraded KSP if you switch to the "Installed" filter. Clicking on the Max KSP column header to sort will group all the incompatible mods together. Messing with your KSP version compatibility is not required. Unfortunately, we don't retain local information about mods that aren't installed. When you refresh, the client replaces all of its information about mod versions from the repository, so there's no way to handle local, personal tags.

Been working on sorting out the dependencies for that PR for the last half hour. Aaaaand, it's done!

Or just use the "Installed" filter, for that matter, then click on Max KSP version to sort by that, grouping the non-upgraded mods together.

This lets you install mods that are not marked compatible with the current KSP version, but it doesn't let you select an older version of a mod to force a mod release downgrade.

And it's done

No worries. I'm on it.

Am I correct in thinking that the KerbalXMod replaced the old KerbalX PartMapper.exe? Sorry it's taken so long for any CKAN folks to notice this change.

Ah, so it is. Should arrive soon, I'm sure. Our Netkan robots are working hard this morning!

@linuxgurugamer sorted it out for you here. Because one of your dependencies (B9PartSwitch) is not yet updated for KSP 1.3.1, your mod won't show up in any CKAN views on KSP 1.3.1 installs until that is updated, due to an embarrasingly-longstanding bug. It should show up for 1.3.0 installs, though, or if the KSP compatibility function is employed to force matching of KSP 1.3.0

I don't think we had the version list in the GUI back then, which meant we had no convenient hooks to different versions.

For really large modpacks, it can be very helpful to use the "Download" button on the mod Contents tab. It lets you download one zipfile at a time and puts it in your local CKAN downloads cache. This is surprisingly difficult to do. As has been mentioned, reporting compatibility issues is a much better idea This can be done with the CLI like this: ckan install AwesomeMod=v3.4 It would be good to add this functionality to the mod version list in the GUI. This is a feature I really want to add (at least the ability for users to easily place downloaded zips into the CKAN cache) Some of them have. Others have not.

The issue there was that we didn't have an override for 1.3.9, since most people use .99 as the <end of version> marker. Should be fine, now.

In CKAN, use File - Select KSP Install and click on Add new to add another KSP instance.

Ah. You have your own Netkan. That makes it a little trickier for me to fix. The 1.3.3.1 release is going to be messing up all your KSP 1.2 CKAN users, and simply deleting the .ckan from the repo won't fix things. I'll do a PR to your .netkan file.

I don't think @techman83 visits the forums often, but if you post an issue on the CKAN github and tag him there, he should respond. I'm afraid I haven't the faintest idea how that system works.