Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CKAN gets confused by dependency #1189

Closed
ghost opened this issue Jun 26, 2015 · 4 comments
Closed

CKAN gets confused by dependency #1189

ghost opened this issue Jun 26, 2015 · 4 comments

Comments

@ghost
Copy link

ghost commented Jun 26, 2015

Selected mods to install:
ksp1

The mods are downloaded and preped to be installed... then this shows up:
ksp2

Which is freaking weird as that, you will notice, was already selected... but it gets weirder. Reaffirming my desire to get the stock config, it appears that everything worked...
ksp3

...except, what's that? Go to changes? But they're all applied!
ksp4

Attempting to install that sets you back to the second image. No idea what's happening.

@pjf
Copy link
Member

pjf commented Jun 26, 2015

Oh my. I'm guessing something odd is going on during relationship resolution. :/

We start off with a pretty big changeset here; if it's convenient for you, is it possible to see you can reproduce the behaviour with a smaller number of mods selected for install? That might give us an insight as to exactly where things are going weird.

@ghost
Copy link
Author

ghost commented Jun 26, 2015

What the fuck. I figured it out. It ONLY happened when FAR wanted to add the default ships... the issue was that I had nuked the %KSP%/Ships folder. When I installed FAR separately, it gave me a "could not find part of path" error. Upon resolving the issue (creating a directory structure identical to the normal KSP ships folder), FAR installed correctly.

HOWEVER. To verify that that was the issue, I uninstalled FAR and installed FAR + Distant Object Enhancement.... same error. So I tried installing FAR again. Since the folders were empty after it uninstalled FAR... it hammered my recreated ships folder flat, causing the error to occur again when I tried to reinstall it.

TL;DR: Missing KSP folder structure confused FAR and masqueraded as a dependency error. Fixing folder structure let stuff get installed correctly, but it turns out CKAN will remove important directories if they get emptied during uninstall.

(p.s. recreating the folder a second time let FAR and DOE install without issue)
EDIT: p.p.s. deployment of the "don't tase me bro!.txt" files in the troubled folders has quelled the rebellion.

@pjf
Copy link
Member

pjf commented Jun 26, 2015

@skymarshal : You are awesome.

Since the folders were empty after it uninstalled FAR... it hammered my recreated ships folder flat

Oh dang, nooo! CKAN, don't do that.

Opening a bug, because this is definitely one. (And which should be easy to fix)

@ghost
Copy link
Author

ghost commented Jun 26, 2015

I can honestly say I would never have guessed that to be the cause. As the true culprit has been apprehended--and I got all the mods to install--I am closing this.

@ghost ghost closed this as completed Jun 26, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant