Jump to content

politas

Members
 View Profile  See their activity

  • Posts

    751

  • Joined

  • Last visited

 Content Type 

Everything posted by politas

  1. politas
    If this stretches out much longer, I'll look into cutting the Spacedock downloads over to http. That should sort it out. Spacedock will be changing CAs eventually, @VITASjust needs to find the time to do it.
  2. politas
    Can you give some details about what you're doing when it crashes? There are at least three different situations when CKAN tries to talk to GitHub, up to two at startup, depending on whether you have "Check for new releases" or "Refresh on startup" turned on in settings.
  3. politas
    The CKAN is sourcing downloads of SurfaceExperimentPack from http://spacedock.info/mod/318 Alternatively, https://github.com/CobaltWolf/Surface-Experiment-Pack/releases/latest
  4. politas
    A quick announcement: If you're getting a lot of authentication/trust failures when downloading mods, that is due to Spacedock's SSL certificate being issued by a certifying authority that is rapidly becoming untrusted by the organisations you're trusting to tell you who you can trust.
  5. politas
    Ooh, this sounds excellent! Can you submit a change to the KSP-CKAN Github with the correct packaging?
  6. politas
    It's a challenge to allow for poor network connections - if you timeout early, you can handle it gracefully, but then you also mess up people with slow connections. It's a bit of the code I haven't looked at personally, and I don't know if any of our gun coders have had a chance to examine it.
  7. politas
    And here's a temporary thread for the CKAN. Any chance I can get it stickied?
  8. politas
    -= Download the latest release =- The Comprehensive Kerbal Archive Network (CKAN) The CKAN is a mod management solution for Windows, Mac and Linux that targets the .NET 4.5 framework and Mono 5.0 or higher. It installs, updates, and uninstalls mods automatically, leveraging strong metadata about the mods it installs to ensure they are compatible with the version of KSP in the installation it is working on, free of conflicts, and are installed in a reliable and predictable fashion. If you've used Linux, then the CKAN is apt-get for KSP. Like the App Store or Play Store for your phone, the CKAN knows which version of KSP you're running, which mods are compatible, and how to install, uninstall, and manage them. The CKAN provides strong guarantees on consistency. It will not allow conflicting mods to be installed unless you explicitly override the version awareness, nor will it allow a mod to be installed without its dependencies. It will never leave mods in a half-installed state. It will never overwrite a file owned by another mod, nor a mod that was installed outside of the CKAN. The CKAN has a GUI which is stable on Windows and Linux. To run it, simply double-click the ckan.exe file, run it with mono ckan.exe, or look for the CKAN Launcher in your menu system. Mac users will launch into the consoleui by default, since Apple decided to break backwards compatibility and stop supporting 32-bit GUI calls. Further resources: FAQ CKAN wiki CKAN clean & reinstall process (Solves most CKAN errors) CKAN IRC channel CKAN Discord Github page Client issues tracker (please report bugs here) Metadata issues here (report problems with mod availability or installation) Releases page Adding a mod to the CKAN CKAN metadata specification Code of Conduct We love contributions of all sorts, and have just a few simple rules for those who wish to help the CKAN awesome! NOTE: Due to the widespread move to TLS 1.2, CKAN clients older than v1.24.0 are no longer functional CKAN is licensed under the MIT licence. -= Download the latest release =-
  9. politas
    Nothing happening until Monday, which I guess means Tuesday for us people of the future (aka Australia/NZ/Japan). I'm guessing that support staff are frantically working on the whole issue.
  10. politas
    In the case of RO, I think poking them is valid, given that a) they manage the metadata for CKAN, and b) they actively recommend using CKAN for installation in order to ensure dependencies.
  11. politas
    That is exactly the problem. RealPlume-StockConfigs depends on RealPlume, so thanks to a CKAN bug ("Compatible" mods with incompatible dependencies aren't listed in any filters) it doesn't appear at all. The RealismOverhaul team are managing both mods' metadata.
  12. 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. StarCrusher96

      StarCrusher96

      okay, If you know how to remove my mod from CKAN, please tell me. thx for noticing.

    2. politas

      politas

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

    3. StarCrusher96

      StarCrusher96

      okay thx

  13. politas
    That's fine. Yes, please tag me on releases if that's not too much trouble. I gather from some of the conversation that you have at least one user who is using CKAN, so you can also leave it to them to let us know.
  14. politas
    Hi, just noticed that Search And Rescue has been removed from Spacedock. CKAN can source downloads from dropbox links, but none of our automated updating can handle such. Anyone wanting to install future releases of Search And Rescue via CKAN could help us out hugely by notifying us when there's a new release to index. @TMasterson5, if you'd like to support CKAN for your mod, there are a lot of options depending on how much effort you're willing to invest, none of which are particularly overwhelming. PM me if you wish.
  15. politas

    Hi Roverdude,

    CommunityResourcePack v0.6.2.0's AVC version file is limiting its compatibility to KSP 1.2.0. Your forum thread declares compatibility with 1.2 generally. Are you planning a new release for 1.2.1? I can give you a PR for your netkan file to add a KSP version override for CKAN if you'd like.

    1. RoverDude

      RoverDude

      Yup I have new 1.2.1 releases coming out today

  16. politas
    Hey, Squad, can you ask Steam to launch the 64 bit version of KSP on Linux?
  17. politas
    1.1.4's restructure should make things much smoother going forward for SVE on CKAN. What took time was undoing all the tricky stuff we had for the old config and reorganising all the dependencies and new downloads. The separate download for the Scatterer stuff will reduce the excess downloads (HR + LR), too. The Snow download will need some further investigation to figure out, so that hasn't been added, yet. Might ask for some minor changes there in the future, but I'll get back to you.
  18. politas

    Hi Papa_Joe,

    Not sure how the discussion between you and @Olympic1 is going in regard to the Burn Together mod. Perhaps I can help make the issue clear from CKAN's end.

    The zip file that's included in Burn Together is an optional add-on for the mod, to add the functionality to command modules as well as cockpits. As it's an option, CKAN will not attempt to install it by default. Normally, we would create a second mod entry in CKAN to extract the specific files for the option and install them, while filtering them out from the main installation. Unfortunately, CKAN currently has no iteration built in to look inside zip files within the main zip file, so we can't expand that zip file without a significant addition to our code (with all the potential for new bugs inherent). What would be handy for us is if that zip file, with it's simple MM script, was available as a separate Spacedock entry, or a separate zip file in the GitHub release (We can identify those zip files by naming patterns). 

    Then we could create a new mod entry in CKAN, "Burn Together for Command Modules" that depends on Burn Together, and adds that functionality, without users needing to know the details of how to enable that functionality.

    Cheers,

    Politas

  19. politas
    There are modifiers on ModuleManager instructions to make them happen AFTER another mod has done its thing, you ought to be able to use them? I'm not entirely sure of the details, though.
  20. politas

    Hi GregroxMun!

    Sorry for the long delay, but I am just now looking at the Spacedock automated submission of your JupiteryJoolRecolor 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. 

    I note there are a couple of other colour options, so I've made a single virtual mod identifier "JoolRecolor", so that users don't try to install two at once, and I've split JupiteryJoolRecolor into two mods, one for Kopernicus, and one for TextureReplacer, with the appropriate dependencies.

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

  21. 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. WillThe84th

      WillThe84th

      Nope, not that i'm aware of.

    2. politas

      politas

      Cool. Should be in CKAN soon.

  22. politas
    The changes that @JPLRepois looking at on the RO side should fix it, and that broken filter can just be removed from the metadata. I'll need to do something to try to discourage users from installing TACLS-ROConfig, which will require changing all the previous ckans. I'll probably lock them to the specific RealismOverhaul version they match up to.
  23. politas
    Ah, now that's why we had the TACLS-StockConfig mod, so that CKAN wasn't trying to overwrite files. Back in May, we did this change: Remove dependency for config file as it now uses CRP resources Which should mean that the LifeSupport.cfg file isn't installed at all, but perhaps the filter for that file is broken.
  24. politas
    @Conventia has it right. It's the GitHub release tag. The filename is irrelevant.Some mods have the same filename with every release.
  25. politas
    Yes, that would do it. Case matters to the CKAN. @JPLRepo, I can use the CKAN's epoch hack to force the latest release, or you could re-release that version with the same version header string used on previous releases so the version numbers in CKAN look the same as the GitHub ones. Which would you prefer?
×
×
  • Create New...