search

KSP-CKAN / CKAN

The Comprehensive Kerbal Archive Network
https://forum.kerbalspaceprogram.com/index.php?/topic/197082-*
Other
1.98k stars 347 forks source link

Metadata repo - EditorExtensions stuck at older version #699

Closed MachXXV closed 9 years ago

MachXXV commented 9 years ago

Client is still getting v2.3, and is still downloading from an old url at github instead of the newer kerbalstuff link - both GitHub(old v2.3) and newer kerbalstuff (v2.4/soon 2.5) metadata files show in the CKAN-Meta repo.

olasundell commented 9 years ago

I second this. Two things I noticed: 2.3 is called EditorExtensions-v2.3.ckan and has KSP version 0.90.0. EE 2.4 and 2.5 are called EditorExtensions-2.[45].ckan and have KSP version 0.90. Might it be a broken metadata problem?

Ippo343 commented 9 years ago

Actually no, it's an issue with the version number itself. In ASCII, v > 2, therefore v2.3 > 2.5.

Unfortunately it's not an easy problem: humans understand version numbers with no problems, computers don't. If you change the format, the computer is too dumb to notice :(

In the meantime, you can install the newer version from the command line using

 ckan install EditorExtensions=2.5

(or upgrade if you have already installed EE)

olasundell commented 9 years ago

I consider the name of the ckan file to be metadata. :)

Ippo343 commented 9 years ago

But it's metadata that has been provided by @MachXXV on KerbalStuff ;)

MachXXV commented 9 years ago

It appears that the "v2.3" entry was added by one of the bots that picked it up from KSP-AVC's data which is pointing to my GitHub repo, before I added the mod to Kerbalstuff - can we get the GitHub one removed? I had added the mod to Kerbalstuff without the v prefix since that appeared to be the syntax used vs. the Semantic Versioning style. CKAN may need to eventually support that in it's sorting approach.

Should I submit a pull req to CKAN-Meta to get them deleted? or revise the mod's versioning syntax on Kerbalstuff?

Ippo343 commented 9 years ago

This should now be fixed with KSP-CKAN/CKAN-meta#192, could you please try again and see if it's better now?

Ippo343 commented 9 years ago

This issue was moved to KSP-CKAN/CKAN-meta#194