Jump to content

CKAN (The Comprehensive Kerbal Archive Network); v1.28.0 - Dyson


politas

Recommended Posts

  On 7/20/2017 at 6:42 PM, nobodyhasthis2 said:

Yes it is there.

EDIT: right got it now. You mean  "depends": ?

This netkan not maintained by anyone. So if the folder structure changed. It will not be noticed by anyone and will not work with the current netkan. So manual install from now on till a fix comes along. I did take the liberty to post your repot to github. So at least it is on the "to do" list.

EDIT: I have not looked at this in a very long time but depending on health of the SpaceDock API. Changes may get picked up later but it still needs nurturing.

Expand  

Yep, I meant in the "depends" field.

A direct download of ResearchBodies from SpaceDock has the right folder structure, so I'm curious why CKAN is installing it incorrectly. Nothing in its NetKAN file says to install to a specific folder, so I assumed CKAN would be able to install the correct folder structure by default. Thanks for putting it on the to-do list.

Link to comment
Share on other sites

Dear CKAN maintainers including @politas,

I have marked Trajectories compatible with every KSP version up to 1.3.99. I have done this in the Trajectories.version file inside the zip file, on http://ksp-avc.cybutek.net/ and on spacedock.

 

Yet, this is how CKAN shows it:

bWXOKds.png

It says Max KSP version 1.2.2, when I marked it as being 1.3.99-compatible everywhere. What's going on?

Link to comment
Share on other sites

Could I convince someone to have a look at this exception I'm getting when I start up CKAN? I don't think CKAN is the root issue, but it might be useful to know exactly what problem it's having.

 

  Reveal hidden contents

 

 

Link to comment
Share on other sites

I seem to have trouble installing it. I run Ckan and I click new path to tell it were to install it. It pulls open a folder and I navigate to My ksp folder. The problem is there is no accept button only an open button and I'm not sure what I'm doing anymore. Do I need to create a ckan folder in side the KSP folder? If so I tried that and it doesn't work still.

Link to comment
Share on other sites

  On 7/27/2017 at 6:30 PM, Kobymaru said:

Dear CKAN maintainers including @politas,

I have marked Trajectories compatible with every KSP version up to 1.3.99. I have done this in the Trajectories.version file inside the zip file, on http://ksp-avc.cybutek.net/ and on spacedock.

 

Yet, this is how CKAN shows it:

bWXOKds.png

It says Max KSP version 1.2.2, when I marked it as being 1.3.99-compatible everywhere. What's going on?

Expand  

Hi Kobymaru, sorry about that. The Netkan robot hasn't been looking at your AVC data. Fixing that now.

  On 7/28/2017 at 5:32 PM, Phoenix Nebula said:

I seem to have trouble installing it. I run Ckan and I click new path to tell it were to install it. It pulls open a folder and I navigate to My ksp folder. The problem is there is no accept button only an open button and I'm not sure what I'm doing anymore. Do I need to create a ckan folder in side the KSP folder? If so I tried that and it doesn't work still.

Expand  

The file you download is not an installer; it's the program. The prompt you are getting is asking you to tell CKAN where your KSP installation is.

Link to comment
Share on other sites

  On 8/1/2017 at 4:45 PM, Phoenix Nebula said:

I must be stupid because I still don't understand. So I need to download the installer then? If so were can I download it because I can only find a link to download the program.

Expand  

No, you're not stupid.  It took me a bit to figure it out as well.  Ok...well, maybe we're both on the wrong side of the bell curve :confused:

There is no installer.  What you are correctly downloading is the CKAN program itself.  Put it in a convenient place.  I put mine in root directory of all my separate KSP versions (i.e. KSP v1.22 and several KSP 1.3 each with a different mod set).  Then, when you start CKAN, it needs to know where your KSP installs are.  You accomplish this in CKAN by going to File > Select KSP install...Add new, navigating to the appropriate KSP directory and selecting the buildID or buildID64 text file (depending on which version of the game your running, 32 or 64-bit).

I think it's the last step that confuses some people.

Link to comment
Share on other sites

  On 8/1/2017 at 7:11 PM, Phoenix Nebula said:

Okay now I have a new problem. For some reason Ckan won't let me update any mods and it stopped letting me add or remove mods.

Expand  

Glad you have got this far; well done.  You can have multiple versions of KSP "installed" for various reasons - different versions of the game, different mod combinations, etc. All you have to do is copy the KSP directory as many times as you like and tailor each one.  CKAN can update each KSP install separately and can limit the mods you can install in the game by compatible KSP version.

What might be happening is you are trying to download mods that are not compatible with your version of KSP.

Do you have only 1 KSP install and if so what version is it?  What version of KSP mods are you permitting in CKAN?  To figure this out, in CKAN go to Settings > Compatible KSP versions and ensure that you've matched your KSP version with the versions of the mods in which you're interested.  CKAN can prevent you from installing mods made for KSP v1.2 in a KSP v1.3 install, and vice versa, depending on your compatibility selections.

I hope that's clear enough :confused:

Link to comment
Share on other sites

  On 7/26/2017 at 9:33 PM, ev0 said:

Yep, I meant in the "depends" field.

A direct download of ResearchBodies from SpaceDock has the right folder structure, so I'm curious why CKAN is installing it incorrectly. Nothing in its NetKAN file says to install to a specific folder, so I assumed CKAN would be able to install the correct folder structure by default. Thanks for putting it on the to-do list.

Expand  

Your right there is nothing in its NetKAN file says to install to a specific folder. That was ok up to this point as the default behaviour is to place it in a folder with same name as the mod. Things have changed. Since the mod has been adopted by another author and moved in Gamedata. To the same folder as all the other mods they maintain.

So install path has changed and is not the same as the mods name. Spacedock assumed ResearchBodies goes in the ResearchBodies folder. Which is now wrong. The NetKan will automatically pick up changes to Spacedock files but if folders get moved it needs to know about this through a manual NetKan update. The non-default install path needs added. After this done in the whole thing will carry on with automatic updates through spacedock.

 

Link to comment
Share on other sites

Could someone take a look at

It's been updated for 1.3 now, but ckan isn't listing the new version yet.

Thanks

Edit: Oh and its dependant on:

now instead of the original version, which isn't listed at all

Edited by Torih
Link to comment
Share on other sites

It's about time I learn to add things to CKAN. So @linuxgurugamer how does this look? This mod in particular has mutually exclusive options.

  Reveal hidden contents

 

Edited by JadeOfMaar
paging linux
Link to comment
Share on other sites

  On 8/8/2017 at 4:52 PM, JadeOfMaar said:

It's about time I learn to add things to CKAN. So @linuxgurugamer how does this look? This mod in particular has mutually exclusive options.

  Reveal hidden contents

 

Expand  

Thanks for getting involved! That's mostly pretty good, but it's going to install all of the mutually exclusive options at the same time. We'll need separate NetKAN entries for each option.

Link to comment
Share on other sites

  On 8/7/2017 at 6:54 PM, Torih said:

Could someone take a look atIt's been updated for 1.3 now, but ckan isn't listing the new version yet.

Thanks

Edit: Oh and its dependant on:

now instead of the original version, which isn't listed at all

Expand  

The author of TRR has made it clear that they do not want TRR on CKAN yet. We will respect their wishes. There's not a huge point in updating WindowShine just to make it disappear from CKAN.

Link to comment
Share on other sites

  On 8/3/2017 at 1:20 PM, nobodyhasthis2 said:

Your right there is nothing in its NetKAN file says to install to a specific folder. That was ok up to this point as the default behaviour is to place it in a folder with same name as the mod. Things have changed. Since the mod has been adopted by another author and moved in Gamedata. To the same folder as all the other mods they maintain.

So install path has changed and is not the same as the mods name. Spacedock assumed ResearchBodies goes in the ResearchBodies folder. Which is now wrong. The NetKan will automatically pick up changes to Spacedock files but if folders get moved it needs to know about this through a manual NetKan update. The non-default install path needs added. After this done in the whole thing will carry on with automatic updates through spacedock.

 

Expand  

ResearchBodies should be right, now.

Link to comment
Share on other sites

CKAN failed on me on fresh gentoo linux install with ssl error (Error: TrustFailure (The authentication or decryption has failed.)). CKAN helpfuly suggests to run mozroots but that does not help. Looks to me like it fell victim mozilla cutting off seamonkey. Anyway, what did help was to run update-ca-certificates (should not be needed, but gentoo CA package somehow missed this) and cert-sync --user /etc/ssl/certs/ca-certificates.crt as user to push system root certs to mono.

Link to comment
Share on other sites

This has probably been asked before, but does CKAN provide any method for preserving certain files during an upgrade?

I'm thinking in particular of settings or configuration files that users would want to keep. In my case these would always be in the PluginData folder, and would always be created after the mod is installed (the files aren't included in the download package).

There are a few issues related to this, including the oldest open issue, along with 653, and maybe 1610. But I'm not really sure about the status of the issue as a whole.

Link to comment
Share on other sites

  On 8/17/2017 at 1:28 AM, DMagic said:

This has probably been asked before, but does CKAN provide any method for preserving certain files during an upgrade?

I'm thinking in particular of settings or configuration files that users would want to keep. In my case these would always be in the PluginData folder, and would always be created after the mod is installed (the files aren't included in the download package).

There are a few issues related to this, including the oldest open issue, along with 653, and maybe 1610. But I'm not really sure about the status of the issue as a whole.

Expand  

If you don't include the file in the download and instead have it generated on runtime then it should stay (iirc). I'll test and edit.

Edited by TheRagingIrishman
Link to comment
Share on other sites

  On 8/17/2017 at 1:28 AM, DMagic said:

This has probably been asked before, but does CKAN provide any method for preserving certain files during an upgrade?

I'm thinking in particular of settings or configuration files that users would want to keep. In my case these would always be in the PluginData folder, and would always be created after the mod is installed (the files aren't included in the download package).

There are a few issues related to this, including the oldest open issue, along with 653, and maybe 1610. But I'm not really sure about the status of the issue as a whole.

Expand  

 

  On 8/17/2017 at 1:29 AM, TheRagingIrishman said:

If you don't include the file in the download and instead have it generated on runtime then it should stay (iirc). I'll test and edit.

Expand  

This is correct. The CKAN client does not touch any files it did not install.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...