{"action":"created","issue":{"url":"https://api.github.com/repos/Swamp-Ig/ProceduralParts/issues/97","labels_url":"https://api.github.com/repos/Swamp-Ig/ProceduralParts/issues/97/labels{/name}","comments_url":"https://api.github.com/repos/Swamp-Ig/ProceduralParts/issues/97/comments","events_url":"https://api.github.com/repos/Swamp-Ig/ProceduralParts/issues/97/events","html_url":"https://github.com/Swamp-Ig/ProceduralParts/issues/97","id":53958388,"number":97,"title":"Incomplete AVC file causes CKAN grief","user":{"login":"hakan42","id":352641,"avatar_url":"https://avatars.githubusercontent.com/u/352641?v=3","gravatar_id":"","url":"https://api.github.com/users/hakan42","html_url":"https://github.com/hakan42","followers_url":"https://api.github.com/users/hakan42/followers","following_url":"https://api.github.com/users/hakan42/following{/other_user}","gists_url":"https://api.github.com/users/hakan42/gists{/gist_id}","starred_url":"https://api.github.com/users/hakan42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hakan42/subscriptions","organizations_url":"https://api.github.com/users/hakan42/orgs","repos_url":"https://api.github.com/users/hakan42/repos","events_url":"https://api.github.com/users/hakan42/events{/privacy}","received_events_url":"https://api.github.com/users/hakan42/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-01-10T13:37:31Z","updated_at":"2015-01-10T16:10:49Z","closed_at":null,"body":"CKAN tries to expand version information from the .version file. It stumbles over the one-item version string in your package.\r\n\r\nCould you, by any chance, change your version file to look like (also, please make sure that it is valid JSON, verifying especially the comma signs...\r\n\r\n```\r\n     \"VERSION\":{\r\n         \"MAJOR\":0,\r\n         \"MINOR\":9,\r\n         \"PATCH\":21,\r\n         \"BUILD\":4711\r\n     },\r\n     \"KSP_VERSION\":{\r\n         \"MAJOR\":0,\r\n         \"MINOR\":90,\r\n         \"PATCH\":0\r\n     },\r\n     \"KSP_VERSION_MIN\":{\r\n         \"MAJOR\":0,\r\n         \"MINOR\":90,\r\n         \"PATCH\":0\r\n     },\r\n     \"KSP_VERSION_MAX\":{\r\n         \"MAJOR\":0,\r\n         \"MINOR\":90,\r\n         \"PATCH\":0\r\n     }\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/Swamp-Ig/ProceduralParts/issues/comments/69460908","html_url":"https://github.com/Swamp-Ig/ProceduralParts/issues/97#issuecomment-69460908","issue_url":"https://api.github.com/repos/Swamp-Ig/ProceduralParts/issues/97","id":69460908,"user":{"login":"pjf","id":12072,"avatar_url":"https://avatars.githubusercontent.com/u/12072?v=3","gravatar_id":"","url":"https://api.github.com/users/pjf","html_url":"https://github.com/pjf","followers_url":"https://api.github.com/users/pjf/followers","following_url":"https://api.github.com/users/pjf/following{/other_user}","gists_url":"https://api.github.com/users/pjf/gists{/gist_id}","starred_url":"https://api.github.com/users/pjf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pjf/subscriptions","organizations_url":"https://api.github.com/users/pjf/orgs","repos_url":"https://api.github.com/users/pjf/repos","events_url":"https://api.github.com/users/pjf/events{/privacy}","received_events_url":"https://api.github.com/users/pjf/received_events","type":"User","site_admin":false},"created_at":"2015-01-10T16:10:48Z","updated_at":"2015-01-10T16:10:48Z","body":"@hakan42 : Gosh, this is weird. What error are we getting? The file in PP 0.9.21 looks like this:\r\n\r\n```\r\n{\r\n  \"NAME\": \"Procedural Parts\",\r\n  \"URL\": \"https://raw.githubusercontent.com/Swamp-Ig/ProceduralParts/master/ProceduralParts.version\",\r\n  \"VERSION\": \"0.9.21\",\r\n  \"KSP_VERSION\": {\r\n    \"MAJOR\": 0,\r\n    \"MINOR\": 90,\r\n    \"PATCH\": 0\r\n  }\r\n}\r\n```\r\n\r\nWhich is both a valid JSON file, and *should* be sufficient for what the netkan indexer wants. I imagine we ignore the name and URL fields, and we use the VERSION and KSP_VERSION fields (but it's been a while since I checked).\r\n\r\nI hope we allow a `KSP_VERSION` without the MIN/MAX fields, as the [AVC spec](http://ksp.cybutek.net/kspavc/Documents/README.htm) supports that, and we *should* support the spec (even if we ignore the bits we don't need).\r\n\r\nHowever I can't spot a \"one line\" version file at all, so I might be looking at entirely the wrong file here."}}