-
-
Notifications
You must be signed in to change notification settings - Fork 345
CKAN installing mods for higher version than what's installed. #2060
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Some updated mods uploaded to Curse have gotten incorrect metadata due to Curse not adding the "1.3" version yet. Our NetKAN scraper is being told by Curse that they are compatible with KSP 1.2.2, so the CKAN client reflects that. When the mods are corrected on Curse, they should update automatically. You can force a downgrade of a specific mod by uninstalling in the GUI and then using the command line to install the previous version with
|
Hey there! I'm a fun-loving automated bot who's responsible for making sure old support tickets get closed out. As we haven't seen any activity on this ticket for a while, we're hoping the problem has been resolved and I'm closing out the ticket automaically. If I'm doing this in error, please add a comment to this ticket to let us know, and we'll re-open it! |
Hi Guys, sorry to wake up this old ticket, but I seem to be having the same problem. I'm running ckan v1.24.1+9712f94116e8 under Debian 9. I have mono version 5.10.160 installed. I'm using KSP 1.3.1 and CKAN is recommending from Both the GUI and CLI, Chatterer 0.9.94 which is the version for KSP 1.4.1, and doesn't work on 1.3.1. If I try the trick above and do:
Then I get the correct version and it works. Though I thought the whole idea of CKAN / apt-get is to take care of these things for you. Am I missing something? If you go here, and click the Changelog button, you will see which versions of Chatterer go with which version of KSP: https://spacedock.info/mod/208/Chatterer Please enlighten me! Thanks :-) |
Hi @clifcox, your question isn't related to this issue unfortunately. Chatterer 0.9.94 contains a .version file that says this: "KSP_VERSION_MIN":
{
"MAJOR":1,
"MINOR":3,
"PATCH":0
},
"KSP_VERSION_MAX":
{
"MAJOR":1,
"MINOR":4,
"PATCH":99
}, So Chatterer itself is saying that this version is compatible with KSP 1.3.0 and later. CKAN tries to take care of these things for you, but if the data that feeds into it is incorrect, it has no way of knowing that. If you are sure that this data is incorrect, please alert the author of Chatterer so it can be corrected. |
Ok that's good info. Here is another one. :-)
As before I'm using KSP 1.3.1 and I'd like the Docking Port Alignment Indicator mod. CKAN offers me version 6.8.0, however it's .version file says:
{"NAME":"Docking Port Alignment Indicator","URL":"http://ksp-avc.cybutek.net/version.php?id=361",
"DOWNLOAD":"http://forum.kerbalspaceprogram.com/index.php?/topic/40423-11-docking-port-alignment-indicator-version-621-beta-updated-04122016/",
"VERSION":{"MAJOR":6,"MINOR":8,"PATCH":0,"BUILD":0},
"KSP_VERSION":{"MAJOR":1,"MINOR":4,"PATCH":0},
"KSP_VERSION_MIN":{"MAJOR":1,"MINOR":4,"PATCH":0},
"KSP_VERSION_MAX":{"MAJOR":1,"MINOR":4,"PATCH":0}}
I'm not sure what I'm doing wrong.
Thanks for a great project! :-)
Clif
…On 03/14/2018 09:50 PM, HebaruSan wrote:
Hi @clifcox <https://github.com/clifcox>, your question isn't related
to this issue unfortunately. Chatterer 0.9.94 contains a .version file
that says this:
"KSP_VERSION_MIN":
{
"MAJOR":1,
"MINOR":3,
"PATCH":0
},
"KSP_VERSION_MAX":
{
"MAJOR":1,
"MINOR":4,
"PATCH":99
},
So Chatterer itself is saying that this version is compatible with KSP
1.3.0 and later. CKAN tries to take care of these things for you, but
if the data that feeds into it is incorrect, it has no way of knowing
that. If you are sure that this data is incorrect, please alert the
author of Chatterer so it can be corrected.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2060 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYIqoQgERU5Q7_JGvWMd525AbYqzU9-aks5tefL9gaJpZM4Noy4u>.
|
Hi @clifcox, thanks for the FYI. It appears that there was a version 6.8 of DPAI with incorrect versioning info that appeared briefly and was removed, leaving behind a ghost in CKAN. I have removed this now, please click Refresh and try again. |
Hey thanks, it works now. :-) Though AVC still complains. Is there a way to set a compatibility range for AVC like there is in CKAN?
|
@clifcox, I don't know, maybe ask the AVC devs? |
The DPAI dev wrote on forums
This indicates a preference to not use new mod versions on old KSP versions. @clifcox you should completely uninstall DPAI 6.8.0 and try again. CKAN should now fetch you DPAI 6.7.0 instead. If CKAN still insists on getting 6.8.0 then there's other problems. |
Navyfish here. Thanks @clifox and @HebaruSan That explains a lot. Next time if I make a version file mistake I'll poke over here and inform someone. I ain't afraid of no ghosts. |
Yep, thanks it's installing the correct version and working great now. :-)
Clif
…On 03/24/2018 09:26 PM, cake>pie wrote:
The DPAI dev wrote on forums
<https://forum.kerbalspaceprogram.com/index.php?/topic/40423-141-docking-port-alignment-indicator-version-681-updated-031418/&do=findComment&comment=3316301>
6.8 recompiled w/ new KSP DLLs so probably best not to use that on
1.3.x
This indicates a preference to not use new mod versions on old KSP
versions.
@clifcox <https://github.com/clifcox> you should completely uninstall
DPAI 6.8.0 and try again. CKAN should now fetch you DPAI 6.7.0
instead. If CKAN still insists on getting 6.8.0 then there's other
problems.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2060 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYIqoZviF3P78VPmpyHmVJ7-wUe7Rzteks5thxx4gaJpZM4Noy4u>.
|
Using latest version of CKAN v1.22.3
When using older version of KSP, CKAN updates and installs mods designed for newer versions of KSP.
The text was updated successfully, but these errors were encountered: