Jump to content

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


politas

Recommended Posts

  On 5/30/2017 at 9:10 PM, gerishnakov said:

I have, but now if I touch anything in cKan I get the error I mentioned.

Expand  

I'm pretty sure that a Clean & Reinstall will sort that out

  On 5/30/2017 at 2:09 PM, Warsoul said:

MaErDa Beta Tester Pack V0.95

I edited the tech tree, i need a checkup if ive done it correctly please :

  Reveal hidden contents

 

Expand  

Ok, I'd closed the PR so it won't get added to CKAN. As far as the TechTree config, I'm not sure where to get help for that, but this thread is probably not the best for it.

Link to comment
Share on other sites

  On 5/31/2017 at 10:02 AM, ItsSeanBroleson said:

for my own curiosity, is there any delay on the CKAN end when authors complete their work on an update? Like, do they submit it and then CKAN indexing takes system/developer action or is it pretty instant after an author sends it out to be indexed?

Expand  

Depends on where CKAN gets the releases from. CKAN can pull from SpaceDock, Github, Curse, Jenkins or other websites.

When releasing on SpaceDock, that release is immediately (max 1min) added to CKAN. Releases on other platforms however (see above), get added when our bot detects it (max 3 hours).

Link to comment
Share on other sites

I have a small problem with the new ksp 1.3 release...

The mod Devs who upload there mods to curse can't choose the option to upload for 1.3 and some other websites are also having this problem.

I'm playing on ksp 1.2 and I don't want to update yet, and CKAN is downloading mods that are meant for 1.3 and causing all sorts of problems.

Even if you do fix this can you add an option to downgrade all your current mods to the correct version?

       -Thanks

Devan

Link to comment
Share on other sites

  On 5/31/2017 at 3:25 PM, Devan kerman said:

I have a small problem with the new ksp 1.3 release...

The mod Devs who upload there mods to curse can't choose the option to upload for 1.3 and some other websites are also having this problem.

I'm playing on ksp 1.2 and I don't want to update yet, and CKAN is downloading mods that are meant for 1.3 and causing all sorts of problems.

Even if you do fix this can you add an option to downgrade all your current mods to the correct version?

       -Thanks

Devan

Expand  

Once the mods are fixed on Curse and the CKAN metadata updates, a Clean & reinstall will get the correct versions on all mods installed. (Or you can just uninstall and reinstall the specific mods) If the metadata is controlled by us rather than the mod author, we can also add an override to force the correct mod compatibility util Curse gets around to fixing it, and you can force installation of a particular version of a mod using the command line by saying: 

ckan.exe install <Modidentifier>=<version>

(Make sure you get the full version string and the mod identifier from the mod details)

Link to comment
Share on other sites

  On 5/30/2017 at 5:09 PM, HebaruSan said:

It's not the same as having it in CKAN itself, but try sorting this page by "Last Indexed":  http://status.ksp-ckan.org/

Expand  

Thanks HebaruSan, I didn't see this because the software does not have that colum. I didn't knew about the link you sent to me. I will use it but I still think that adding a colum like I described would be very handy.

Link to comment
Share on other sites

so.. raster prop monitor updated to 1.3 a couple days ago, yet CKAN still shows 1.2.2 as the max supported version... moarDV says to ask here if there are CKAN issues, so... I'm asking here... is there a problem with this mod or its metadata?

Link to comment
Share on other sites

  On 6/1/2017 at 4:05 AM, ss8913 said:

so.. raster prop monitor updated to 1.3 a couple days ago, yet CKAN still shows 1.2.2 as the max supported version... moarDV says to ask here if there are CKAN issues, so... I'm asking here... is there a problem with this mod or its metadata?

Expand  

Latest release is marked as a prerelase on Github.  Prereleases will not be indexed for CKAN.

Link to comment
Share on other sites

So with the launch of 1.3 I decided to give Ckan a try on my fresh install of KSP.  I deleted my old KSP folders and started a new however when I downloaded my mods through CKAN they still show up as AD as if I manually installed them. Not sure whats going on, anyone have an idea?

Link to comment
Share on other sites

  On 5/30/2017 at 5:09 PM, HebaruSan said:

It's not the same as having it in CKAN itself, but try sorting this page by "Last Indexed":  http://status.ksp-ckan.org/

Expand  

HebaruSan,

I just played a bit with the link you sent me, there are a lot of recently indexed mods that are not available in CKAN software.

I also found a solution to the problem. I post here for other users reference.

If you are in CKAN and want to know the latest additions you can just click on the FILTER BUTTON in the side of the blue arrows buttons, once you click in there you will find some interesting options being one of them the NEW IN REPOSITORY option.

 

Link to comment
Share on other sites

  On 6/1/2017 at 3:57 PM, Rafael acevedo said:

Anyone experiencing slow download speed on ckan when getting mods from spacedock. I tested my connection and it is not on my end.

Expand  

Spacedock is a community ran site so it occasionally has low connection speeds. You can check to make sure it's not ckan by going to spacedock.info and trying to download something.

Link to comment
Share on other sites

  On 6/1/2017 at 5:23 PM, TheRagingIrishman said:

Spacedock is a community ran site so it occasionally has low connection speeds. You can check to make sure it's not ckan by going to spacedock.info and trying to download something.

Expand  

tried it downloaded in 1 second versus 2 hours through ckan. I also reported the issue on spacedock

Link to comment
Share on other sites

  On 6/1/2017 at 3:57 PM, Rafael acevedo said:

Anyone experiencing slow download speed on ckan when getting mods from spacedock. I tested my connection and it is not on my end.

Expand  

Have you got the latest CKAN 1.22.3?

  On 6/1/2017 at 2:56 AM, felcas said:

Thanks HebaruSan, I didn't see this because the software does not have that colum. I didn't knew about the link you sent to me. I will use it but I still think that adding a colum like I described would be very handy.

Expand  

Yep, it would be useful, but given the way that our automatic indexing of new updates works, that information is just not available for the client. We'd need to maintain a whole separate data structure in order to compare the new repo data with past repo data, and then the client would need to spend time comparing every mod's current release with what it last knew as the current release, working out what to do with that information,... We'd basically need to program an AI to do what we do keeping the repo up to date so that it can understand some changes. I know that it seems like an easy thing to do, but trust me, it really isn't. If it was easy, we'd have done it by now.

  On 6/1/2017 at 6:58 AM, KSPNoob said:

So with the launch of 1.3 I decided to give Ckan a try on my fresh install of KSP.  I deleted my old KSP folders and started a new however when I downloaded my mods through CKAN they still show up as AD as if I manually installed them. Not sure whats going on, anyone have an idea?

Expand  

If you have deleted everything in your GameData folder (other than the Squad folder, obviously), then you shouldn't be getting any AD mods. I know I sound like a broken record, but try a Clean & Reinstall. (Or the relevant parts of it) It really does solve most problems in the CKAN client.

Link to comment
Share on other sites

  On 6/1/2017 at 10:14 PM, politas said:

Yep, it would be useful, but given the way that our automatic indexing of new updates works, that information is just not available for the client. We'd need to maintain a whole separate data structure in order to compare the new repo data with past repo data, and then the client would need to spend time comparing every mod's current release with what it last knew as the current release, working out what to do with that information,... We'd basically need to program an AI to do what we do keeping the repo up to date so that it can understand some changes. I know that it seems like an easy thing to do, but trust me, it really isn't. If it was easy, we'd have done it by now.

Expand  

What about tracking the timestamp when a new version was added? Solving the 100% case of same-version updates with full metadata checking would be AI-level processing and lots of storage, but I think that the date of the latest release is all that anyone actually cares about. Doesn't the crawler know when the version it downloaded wasn't already indexed?

registry.json:available_modules/<modname>/module_version/<version>/initial_timestamp?

Link to comment
Share on other sites

  On 6/1/2017 at 10:43 PM, HebaruSan said:

What about tracking the timestamp when a new version was added? Solving the 100% case of same-version updates with full metadata checking would be AI-level processing and lots of storage, but I think that the date of the latest release is all that anyone actually cares about. Doesn't the crawler know when the version it downloaded wasn't already indexed?

registry.json:available_modules/<modname>/module_version/<version>/initial_timestamp?

Expand  

No, it doesn't, from my understanding. If you have some code experience, and can think of a way to do it without breaking what it does, we welcome contributions! https://github.com/KSP-CKAN/NetKAN-bot is the specific repo. I don't know Perl at all, so I only know how it works by what I've been told.

Edited by politas
expand
Link to comment
Share on other sites

  On 6/1/2017 at 6:58 AM, KSPNoob said:

So with the launch of 1.3 I decided to give Ckan a try on my fresh install of KSP.  I deleted my old KSP folders and started a new however when I downloaded my mods through CKAN they still show up as AD as if I manually installed them. Not sure whats going on, anyone have an idea?

Expand  

If you start over, you need to delete the old CKAN folder as well, since CKAN keeps track of what it's installed... basically to do a KSP reset:

1. delete CKAN GameData Ships (from your KSP install dir)
2. ensure ckan.exe is in the KSP install dir
3. have steam verify local files to restore GameData and Ships
4. run CKAN
5. install mods

Link to comment
Share on other sites

  On 5/21/2017 at 6:56 PM, loppnessmonsta said:

Hey all! Sorry if this has been covered before and I missed it, but it's been driving me nuts for a while now and I can't find anything to fix it. All of Sarbian's mods give an error when installing, including ModuleManager. His are the only mods I have noticed doing this.

 

This is the error I get:

Failed to download "https://ksp.sarbian.com/jenkins/job/ModuleManager/126/artifact/ModuleManager-2.7.6.zip" - error: The request was aborted: Could not create SSL/TLS secure channel.

I have done a clean install, which resolved all the other errors I'd been getting, but this one is proving stubborn.

Expand  

Just in case you didn't solve your problem, firewall andor antivirus software is the cause, in my case it was FSECURE blocking connections with invalid/outdated/unsure certificates

Link to comment
Share on other sites

  On 6/1/2017 at 10:14 PM, politas said:

Yep, it would be useful, but given t Hhe way that our automatic indexing of new updates works, that information is just not available for the client. We'd need to maintain a whole separate data structure in order to compare the new repo data with past repo data, and then the client would need to spend time comparing every mod's current release with what it last knew as the current release, working out what to do with that information,... We'd basically need to program an AI to do what we do keeping the repo up to date so that it can understand some changes. I know that it seems like an easy thing to do, but trust me, it really isn't. If it was easy, we'd have done it by now.

Expand  

Hy Politas, thanks for the reply and yes I believe in you. After that I discovered the option  FILTER > NEW IN REPOSITORY

However I would like to point out some discrepancies.

1-HebaruSan sugested I check the new indexed mods in this link http://status.ksp-ckan.org/ , it was a good solution, I found some mods I was looking for but and headed for CKAN for the upgrade but I didn't found them there. I tried several other recently indexed mods and searched for them in CKAN, again they was not listed. APPEAR to not working properly

2-The option  FILTER > NEW IN REPOSITORY, was working nicely, until I noticed yesterday that there was no new mods (zero), however I also noticed the number of compactible mods rised. I just finished going thru 337 of them and indeed found some new stuff I was waiting for, and others I didn't see before. Soo this filter also APPEAR to not be working properly.

When I say APPEAR is really that, because I am also considering I am doing something wrong and I will apreciate if you can correct me.

 

Thanks

Link to comment
Share on other sites

  On 6/2/2017 at 3:12 AM, ss8913 said:

If you start over, you need to delete the old CKAN folder as well, since CKAN keeps track of what it's installed... basically to do a KSP reset:

1. delete CKAN GameData Ships (from your KSP install dir)
2. ensure ckan.exe is in the KSP install dir
3. have steam verify local files to restore GameData and Ships
4. run CKAN
5. install mods

Expand  

Thnx but I got it working with earlier advice (to clear and reset)  however I put my Ckan.exe simply on my desktop and it works fine.

Link to comment
Share on other sites

Just a quick question.  I was wondering if there is any way to set CKAN to only download mods for a certain KSP version. I'm still using KSP 1.2.2 until all the mods that I use have been updated to 1.3.

Problem is, my install was borked yesterday and I had to do a clean install (KSP 1.2.2), and CKAN seems to insist on installing mods that are updated to 1.3 (which kills my saves).  Is there any way to set CKAN to install  the mod version that are 1.2.2 compatible only, excluding 1.3 versions ?

Thanks in advance, and cheers!

Edited by Slaver0110
Edited for clarity
Link to comment
Share on other sites

  On 6/2/2017 at 8:25 PM, Slaver0110 said:

Just a quick question.  I was wondering if there is any way to set CKAN to only download mods for a certain KSP version. I'm still using KSP 1.2.2 until all the mods that I use have been updated to 1.3.

Problem is, my install was borked yesterday and I had to do a clean install (KSP 1.2.2), and CKAN seems to insist on installing mods that are updated to 1.3 (which kills my saves).  Is there any way to set CKAN to install  the mod version that are 1.2.2 compatible only, excluding 1.3 versions ?

Expand  

CKAN is supposed to do this already. It can tell which version of the game you have, and it tracks which versions of each mod are compatible with which versions of the game. By default it should only be showing you mods that are compatible with your KSP version.

If it's showing you incompatible mod versions, the most likely cause is incorrect metadata for those mods. The most likely cause for that is the fact that Curse has not added a 1.3.0 version option to their web site, but modders are uploading updated mods anyway and selecting 1.2.2 instead, which incorrectly marks that mod as 1.2.2 compatible. No, there's not much you as a user can do about that; it might get straightened out once Curse adds a 1.3.0 option and modders start using it, or it might not.

Link to comment
Share on other sites

  On 6/2/2017 at 8:42 PM, HebaruSan said:

CKAN is supposed to do this already. It can tell which version of the game you have, and it tracks which versions of each mod are compatible with which versions of the game. By default it should only be showing you mods that are compatible with your KSP version.

If it's showing you incompatible mod versions, the most likely cause is incorrect metadata for those mods. The most likely cause for that is the fact that Curse has not added a 1.3.0 version option to their web site, but modders are uploading updated mods anyway and selecting 1.2.2 instead, which incorrectly marks that mod as 1.2.2 compatible. No, there's not much you as a user can do about that; it might get straightened out once Curse adds a 1.3.0 option and modders start using it, or it might not.

Expand  

Ah, ok.  Thanks for the info.  For the time being I'll just manually hunt for the compatible versions and manually install.  Not a big deal, just tedious.

Thanks for the reply, and have a good weekend.  Cheers.

Link to comment
Share on other sites

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