hakan

The cache file for the visual pack should be called: D:\SteamLibrary\SteamApps\common\Kerbal Space Program>dir CKAN\downloads\*astronome* Volume in drive D is DATA Volume Serial Number is 5269-5BA6 Directory of D:\SteamLibrary\SteamApps\common\Kerbal Space Program\CKAN\downloads 12.02.2015 18:46 398.413.030 13625883-AstronomersPack-Interstellar.V2.zip 1 File(s) 398.413.030 bytes 0 Dir(s) 124.492.562.432 bytes free Just take your pre-existing zip file, and drop it into the right directory with the right name... And, best, verify the file size beforehand...

Sorry, my cache has no copies of those files as they are "restricted" from the license If you could give me the identifier of the Astronomer's Pack addons you are trying to install (there are multiple files, for clouds, etc), I could download them on my system and then send you the hash code for the URL.

Just dropped by to announce that the Initial Contracts are available on CKAN too.

You do it the other way round... You provide (or ask a contributor to do so for you) a netkan file to CKAN, which in turn is used by a daemon process to periodically ask kerbalstuff for new releases. The "CKAN" checkbox on your mod page just simplifies the initial creation of the netkan file (which in and of itself is a huge help)

Welcome back Thank you so very much for this. This will clean up my issue list over at github considerably...

nice

Is it possible to modify the image of a craft after upload? I have a few vessels on kerbalx with the default image and would love to upload the "real" image as I got around to make screenshots by now

Honestly, we don't have a good way (yet) to recognize such dll name changes. It bites us with the ModuleManager installation too, for which we write up new ckans by hand every time... So, untill someone comes up with a good enhancement to netkan, having the author stick to his old naming scheme would be your best bet... - - - Updated - - - Interesting suggestion. We already use the pre-release thingy from github so we should index only "final" releases. Would you mind to write a github issue for the "Latest Release" tag so it does not get buried in this thread? Issues have a much higher chance of being worked on whenever one of us finds some time

In case of BackgroundProcessing, the netkan file and/or the distribution is very slightly broken. It looks for a "BackgroundProcessing.dll" in the zip archive, but the version 0.4.0.0 zip contains a "BackgroundProcessing-0.4.0.0.dll". You should ask the author whether he has changed his packaging in the last few releases... Aaah, actually, yes, he has changed it after 0.3.5. This is the reason we have only up to 0.3.5 in CKAN

The only thing I can think of is alphabetical comparison of version strings... is 1.1 smaller or larger than 1.1.3 ?

what mod would that be? Knowing that makes searching / debugging easier

Wooooho! I hope we can have a "official" binary hosted on github, many pull requests for CKAN depend on Kopernicus... ah, that's a given... Any code is by definition broken half a second after being released

Let's split work, you upload it to github, and I'll do the CKAN file

Ah, RoverDude, whatever happened to putting this on github? Just asking

Ah well, do you have an idea where we might obtain this data from? All I could think of off the top of my hat is some kind of plugin that runs on your local installation and reports (via opt-in of course) how much memory your complete installation takes... Nice, I might steal this one

Cool, and even better... Does this mean that I can display parts from any mod? I really reall really need to get cracking on that Vertical Propulsion Emporium contract set I keep mumbling about

@SmarterThanMe: You have in your KSP directory, in "CKAN", a file called "installed-default.ckan". That file holds all your mods with package name and version. Could you upload that to somewhere we can access it to verify that you really have updated everything?

In the end, it is about how much time you have in life for managing your mods and how much you have for actually playing missions. If I would not waste all my time actually maintaining the ckan description files for all the other community members, my gaming would be like: ckan update ckan upgrade --all ksp Compare that with trawling through the forums all day long to check for updates. By now, we should take this to the ckan thread itself, but... Basically CKAN ist for KSP what CPAN is for perl, NuGet for C# (and other packaging systems for other languages). Over time, some standard crystallizes and in the end, saves everyone that bit of life time and debugging. Yes, it seems rude and it *is* actually a bit rude. Not everyone has the kind of time you seem to have to click on zip archives and move files around like a champ.

YESSSSS Can I show an image on one of the sides of the artifact?

Amaaaaziballs cool

Pashidar, could you please tell us which code version (hash) this dll was compiled from? Also, being asked in CKAN quite often for Kopernicus packages, I would love to package this. Do you mind me taking the current dll from your dropbox and putting it into one of our archive servers? Or even better, could someone put this on [Moderator removed defunct website]?

We have no binary release of Kopernicus. I believe I asked in the thread for a release, but nothing came forward... So, whatever depends on Kopernicus will be incomplete as well. And no, cutting a Kopernicus binary out of the distribution archive of Outer Planets is not something I would like to do. This is too hacky even for my much-reduced sensibilities

No, we cannot give the servers a kick. However the author has uploaded the releases to github, the github API is showing us no releases for it: root@ksp-ckan:~# curl https://api.github.com/repos/m4v/RCSBuildAid/releases [ ] I have written up a bug repo on his repo: https://github.com/m4v/RCSBuildAid/issues/20 - - - Updated - - - We have an open issue for this: https://github.com/KSP-CKAN/CKAN-core/issues/4 No one did really get around to implement this, though. - - - Updated - - - RCSBuildAid v0.5.5 is in CKAN now: https://github.com/KSP-CKAN/CKAN-meta/commit/a485ba0ac7a6773ff3bb437bf2e7c72068d4b892

Ah guys, just to cut the CKAN discussion on this thread short: 0.5.5 is not shown because the releases on github are not marked properly, see https://github.com/m4v/RCSBuildAid/issues/20 Aaaaand, RCSBuildAid-v0.5.5.ckan is written up and merged.

Northstar, could I ask you to kindly upload the sources to a github repository? It is not much more work, and would save me lots of time of explaining people why of of your kerbalstuff mods is in CKAN and the other not @Kerbas: sorry, I read your posting too late