Jump to content

politas

Members
 View Profile  See their activity

  • Posts

    751

  • Joined

  • Last visited

 Content Type 

Status Replies posted by politas

  1. politas

    Hi StarCrusher96,

    We're working through our Spacedock submissions to CKAN at the moment and have gotten to your Kerbol Starsystem mod. It's quite a tricky one to handle in CKAN. 

    So far, we're just installing the "Main Mod" part and ignoring the options, but I see that you've included a modified GameData/Kopernicus/config/system.cfg file. CKAN does not overwrite files, and the standards for Kopernicus is that you should use ModuleManager AFTER:Kopernicus to change the system config, rather than replacing the file.

     

    1. politas

      politas

      We haven't added it so far. As far as taking the "CKAN" label off Spacedock, I can't help you there.

    2. (See 2 other replies to this status update)

  2. politas

    Hi there! 

    Sorry for the long delay, but I am just now looking at the Spacedock automated submission of your Fourian Fuel Systems mod to CKAN. The automated process is very limited, and doesn't include things like dependencies or any other relationships, so we often create a fresh pull request. 

    You've specified that Fourian Fuel Systems requires InterstellarFuelSwitch - am I correct in thinking that it is only the plugin that is actually required?

    I also see that your mod uses ModuleManager, so I have put that down as a dependency, too. 

    Are there any other details about your mod that might cause problems for you from users installing it via CKAN?

    1. politas

      politas

      Cool. Should be in CKAN soon.

    2. (See 1 other reply to this status update)

  3. politas

    Hi there,

    Very sorry to hear that you took your Deadskins mod down completely due to the CKAN team's policies and actions. I only just realised you had done so. 

    I've taken references to DeadSkins off of CKAN as per our new policy, and it will not be added back without your approval.

    Sorry for the delay, and for any problems the CKAN has caused you.

    Myk

    1. politas

      politas

      That's a coincidence! I've been working my way through mods that were failing inflation.

    2. (See 1 other reply to this status update)

  4. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      We get the sunflare from the Low res, yes, since it's the smallest overhead. Once you've got that downloaded, it wouldn't have to do it again for Medium Resolution.

    2. (See 27 other replies to this status update)

  5. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      I'm on Linux, and I'm using the CKAN installation. It has a dependency on Kopernicus, and puts the "SVE-Kopernicus" folder and all its contents in GameData.

    2. (See 27 other replies to this status update)

  6. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Nope. That was a stock installation with nothing installed other than SVE, sourcing all the Scatterer and EVE stuff from SVE. I'll have another look at Minmus and Stock Visual Terrain, though. From memory, it was just gone. No orbit line at all.

    2. (See 27 other replies to this status update)

  7. politas

    Hi Bob!

    Would you like a hand with your CKAN metadata? USITools is failing because there are two .version files being installed. You can specify a specific file in the $vref entry, like this:

        "$vref": "#/ckan/ksp-avc/GameData/000_USITools/USITools.version",

     

    1. politas

      politas

      Done.

    2. (See 1 other reply to this status update)

  8. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      I'm getting a weird visual on the main menu screen on launch, too. Serious moire pattern.

    2. (See 27 other replies to this status update)

  9. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Hey, what's up with Stock Visual Terrain and Minmus? Is it supposed to make it go away?

    2. (See 27 other replies to this status update)

  10. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Worked out the problem. SVE-High, Medium and Low Resolution are available on CKAN once more, and SVE-Terrain is also there! Congrats on making the KSP-Dev blog!

    2. (See 27 other replies to this status update)

  11. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      I'm having some troubles getting the SVE netkan working, actually. Not sure what's happening. I'll see if I'm getting the same issue with the Terrain one. It seems to be an issue that only crops up when the zip file is being read.

      Have you dropped the Ultra resolution version entirely?

    2. (See 27 other replies to this status update)

  12. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      It is indeed looking much easier.

    2. (See 27 other replies to this status update)

  13. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Or is http://spacedock.info/mod/847/Stock Visual Terrain going to be the replacement for the TextureReplacer parts? That seems like a good way to do it.

    2. (See 27 other replies to this status update)

  14. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Which is going to change their config?

    2. (See 27 other replies to this status update)

  15. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Have any of the config files in DistantObject, PlanetShine or TextureReplacer been replaced? 

    2. (See 27 other replies to this status update)

  16. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Oh. Is Astroniki's sunflare broken in 1.1.3? I haven't had a chance to actually play KSP since 1.1.3 came out.

       

    2. (See 27 other replies to this status update)

  17. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Do you provide a unique Sunflare, or do you use the original?

    2. (See 27 other replies to this status update)

  18. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      That would help, yes. We can treat it like we do EVE, and have SVE provide and conflict with Scatterer.

    2. (See 27 other replies to this status update)

  19. politas

    Hi Berlin,

    I gather you've taken over the maintenance of StockVisualEnhancements. Congratulations! I would very much like to get SVE listed in CKAN properly. We had a good set of metadata at a couple of points in time, but quite significant structural changes kept breaking our metadata. For now, SVE is completely delisted. 

    Would you be happy for SVE to be back on CKAN? If so, I'd like to discuss what we can do to make CKAN install SVE correctly in the future.

    1. politas

      politas

      Ok, thanks. Let me have a look at your downloads and I'll get back to you. One issue I find with the last version I have downloaded (0.7.1) is that there are a couple of scatterer config files, but not a complete set. It wouldn't be too hard for us to split out the Scatterer config into a dependency, but in order for SVE to fulfil that dependency, it would need to provide a complete set of scatterer config files (even if most are just the same as the original Scatterer)

      CKAN currently won't overwrite any files, whether they're installed by another mod in CKAN, or just happen to exist (So we don't overwrite files in GameData/Squad, for example), we can't just replace the specific files.

    2. (See 27 other replies to this status update)

  20. politas

    politas    -MM-

    Hi there! I'm a friendly CKAN-wizard offering to help you out with getting your mod listed in CKAN. 

    Your KRnD.netkan looks pretty good, apart from the license, which I'm guessing you updated after creating it. The reason you're getting JSON deserialisation errors (and I am too), is that your Github releases don't have a packaged ZIP file in the release contents. There is an undocumented feature implemented earlier this year that will let us use your GitHub releases as they are, though.

    If you would like to self-host your netkan, so you can update the KSP version compatibility as required, I can submit changes to your netkan file and then add a metanetkan pointer to your github.

    Or if you'r rather we CKAN people handle it for you, I can just put all the details into the main Netkan repo.

    1. politas

      politas

      Cool. It's now in CKAN, using your self-hosted netkan metadata, so you can keep it up to date. Feel free to send me a message if there's any questions you have about how to best make changes in the future.

    2. (See 5 other replies to this status update)

  21. politas

    politas    -MM-

    Hi there! I'm a friendly CKAN-wizard offering to help you out with getting your mod listed in CKAN. 

    Your KRnD.netkan looks pretty good, apart from the license, which I'm guessing you updated after creating it. The reason you're getting JSON deserialisation errors (and I am too), is that your Github releases don't have a packaged ZIP file in the release contents. There is an undocumented feature implemented earlier this year that will let us use your GitHub releases as they are, though.

    If you would like to self-host your netkan, so you can update the KSP version compatibility as required, I can submit changes to your netkan file and then add a metanetkan pointer to your github.

    Or if you'r rather we CKAN people handle it for you, I can just put all the details into the main Netkan repo.

    1. politas

      politas

      Just one small change still required. You'll need to change the first line to this 

       

          "spec_version" : "v1.4",

    2. (See 5 other replies to this status update)

  22. politas

    politas    -MM-

    Hi there! I'm a friendly CKAN-wizard offering to help you out with getting your mod listed in CKAN. 

    Your KRnD.netkan looks pretty good, apart from the license, which I'm guessing you updated after creating it. The reason you're getting JSON deserialisation errors (and I am too), is that your Github releases don't have a packaged ZIP file in the release contents. There is an undocumented feature implemented earlier this year that will let us use your GitHub releases as they are, though.

    If you would like to self-host your netkan, so you can update the KSP version compatibility as required, I can submit changes to your netkan file and then add a metanetkan pointer to your github.

    Or if you'r rather we CKAN people handle it for you, I can just put all the details into the main Netkan repo.

    1. politas

      politas

      On another point, there is a set of mods we've identified that would fit into the "not 100% compatible" you talk about. It's been suggested that we might set up a "conflicts" relationship like this:     

      "conflicts" : [
    { "name" : "B9AerospaceProceduralParts"},
    { "name" : "InterstellarFuelSwitch"},
    { "name" : "ProceduralAirships"},
    { "name" : "ProceduralDynamics"},
    { "name" : "ProceduralFairings"},
    { "name" : "ProceduralParts"},
    { "name" : "ProceduralParts-Extended"},
    { "name" : "ProceduralProbes"},
    { "name" : "TweakScale" }
],

       

      Which would prevent your mod and any of those mods being installed at the same time. Would you say that is a reasonable choice, or is the incompatibility too minor to justify a complete block? (I am leaning towards the latter) There is a proposed "warning" relationship that should create a dialogue letting users know about minor compatibility issues, but that may not be implemented for some time.

    2. (See 5 other replies to this status update)

  23. politas

    I once tried to submit the mod to the ckan-repo (as you can tell by my already included .netkan-file in the git-repo). But the netkan validation-tool always just said "JSON deserialization error", which I was unable to fix. So I just stopped trying a while ago. If there is a ckan-wizard out there who can give me a few pointers or even add the mod for me? That would be greatly appreciated.

    Hi there! I'm a friendly CKAN-wizard offering to help you out with getting your mod listed in CKAN. 

    Your KRnD.netkan looks pretty good, apart from the license, which I'm guessing you updated after creating it. The reason you're getting JSON deserialisation errors (and I am too), is that your Github releases don't have a packaged ZIP file in the release contents. When drafting your releases on Github, there's a text/data entry field taht appears, into which you can click and drag files from your computer. If you make a ZIP file containing just the files a user needs to install (leaving out the source code) and attach it there, CKAN will use that as the download for the release. The Source Code files that are automatically generated are unfortunately not available for downloading.

    You can look at my own tiny little mod's github releases to see the difference - You can see that in addition to the "Source Code" zips, there is Sarkomand-1.0.zip in the Downloads section, which is the release zip I created locally and attached to the release when I created it.

     

    1. politas

      politas

      Ah, turns out I had missed an undocumented feature implemented earlier this year that will let us use your GitHub releases as they are. 

      If you would like to self-host your netkan, so you can update the KSP version compatibility as required, I can submit changes to your netkan file and then add a metanetkan pointer to your github.

      Or if you'r rather we CKAN people handle it for you, I can just put all the details into the main Netkan repo.

    2. (See 1 other reply to this status update)

  24. politas

    politas    Sobol

    Hi Sobol,

    I'm trying to fix up the CKAN metadata for your Space Launch Systems mods. Is the original SLSPartPack meant to only work with Realism Overhaul? I don't understand the distinction between the different packs and the dropbox download and how they should be installed.

    1. politas

      politas

      Oh, and when you say RealismOverhaul, do you actually mean RealisticSolarSystem, or is it about the RealFuels stuff? The "Dimension" part of the name is also confusing.

    2. (See 2 other replies to this status update)

  25. politas

    politas    Sobol

    Hi Sobol,

    I'm trying to fix up the CKAN metadata for your Space Launch Systems mods. Is the original SLSPartPack meant to only work with Realism Overhaul? I don't understand the distinction between the different packs and the dropbox download and how they should be installed.

    1. politas

      politas

      So SLS Stock Dimension and SLS Part Pack without the additional Dropbox download are the same thing? I'm really quite confused.

    2. (See 2 other replies to this status update)

×
×
  • Create New...