Skip to content
New issue

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

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

Already on GitHub? # to your account

[Mod]: JFA #10281

Closed
D4RKN3R opened this issue Nov 8, 2024 · 8 comments · Fixed by #10282
Closed

[Mod]: JFA #10281

D4RKN3R opened this issue Nov 8, 2024 · 8 comments · Fixed by #10282

Comments

@D4RKN3R
Copy link

D4RKN3R commented Nov 8, 2024

Mod Name

JFA

Author(s)

D4RKN3R

License

MIT

Homepage link

https://forum.kerbalspaceprogram.com/topic/223852-jfa-jeb-far-away-1125-alpha-12/

Download link

https://github.com/D4RKN3R/JFA

@D4RKN3R
Copy link
Author

D4RKN3R commented Nov 8, 2024

"Hey, this is already on CKAN!" I just need it updated and have assumed this is the correct way to do that. I am sorry for the trouble if it isn't, but if so, please direct me to the proper way to do this.

@SofieBrink
Copy link
Contributor

I’m not on the ckan team but just gathering information, do you plan to post this release to spacedock too or will you only be using github releases from now on? As that’s what i think reading the release notes

@D4RKN3R
Copy link
Author

D4RKN3R commented Nov 8, 2024

I’m not on the ckan team but just gathering information, do you plan to post this release to spacedock too or will you only be using github releases from now on? As that’s what i think reading the release notes

It's a spacedock issue. There should be details in the comments of the forum page of the mod. I plan to return to spacedock after it's resolved.

@HebaruSan
Copy link
Member

HebaruSan commented Nov 8, 2024

Hi @D4RKN3R, sorry for the inconvenicence; this mod has a mysterious inflation error that I haven't been able to figure out yet:

image

http://status.ksp-ckan.space/

image

"central directory" most likely means there's something wrong with the ZIP file, but when I downloaded it and inspected it locally, the usual tools for validating ZIP files don't report any issues (otherwise I would have tried to contact you with a recommendation of how to fix it).

So I have to try to think of other places to start investigating: Which tools are you using to make the ZIPs for this mod? Maybe there's some quirk of incompatibility between them and the ZIP library that CKAN uses. If we can figure that out, then maybe we can also figure out a workaround.

@SofieBrink
Copy link
Contributor

I’m not on the ckan team but just gathering information, do you plan to post this release to spacedock too or will you only be using github releases from now on? As that’s what i think reading the release notes

It's a spacedock issue. There should be details in the comments of the forum page of the mod. I plan to return to spacedock after it's resolved.

Just read your forum message, I believe that to be a firefox issue not a spacedock issue. Try using a different browser to access spacedock

@D4RKN3R
Copy link
Author

D4RKN3R commented Nov 8, 2024

"central directory" most likely means there's something wrong with the ZIP file, but when I downloaded it and inspected it locally, the usual tools for validating ZIP files don't report any issues (otherwise I would have tried to contact you with a recommendation of how to fix it).

I use the default compression thing on my PC (Pop OS). The file extracts fine, and works fine after being extracted. Not sure what the issue with it would be.

@HebaruSan
Copy link
Member

Well, the good news is that whatever that issue is, it might be specific to the upload that's currently on SpaceDock.
Or it might start happening again in the next release after this one. 🤷

So switching the hosting over to GitHub should address both problems. I can do that in a couple of minutes...

@HebaruSan
Copy link
Member

Just read your forum message, I believe that to be a firefox issue not a spacedock issue. Try using a different browser to access spacedock

Alternately, a Firefox dev (!) apparently just posted a very jargon-heavy explanation of the issue that includes a workaround:

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants