Skip to content

Procedural Fairings has some very strange version numbers #2455

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.

Sign up for GitHub

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

Jump to bottom
Closed
rsparkyc opened this issue May 30, 2018 · 5 comments
Closed

Procedural Fairings has some very strange version numbers #2455

rsparkyc opened this issue May 30, 2018 · 5 comments

Comments

@rsparkyc
Copy link

CKAN Version:
1.25.1

KSP Version:
1.4.3.2152

Operating System:
Windows

Have you made any manual changes to your GameData folder (i.e., not via CKAN)?
No

Problem

Procedural Parts shows some interesting version numbers. Versions 1.4.3.1 & 1.4.3.2 are showing up with a 1: before them, apparently making them seem more recent than 1.4.3.3 and the just released but not indexed yet 1.4.3.4

image
@HebaruSan
Copy link
Member

@linuxgurugamer worked on this in KSP-CKAN/NetKAN#6547 and KSP-CKAN/NetKAN#6552. Looks like an epoch was added briefly, creating the two versions with a 1: prefix, then removed, creating the newest numbers at the bottom of the list.

@rsparkyc
Copy link
Author

should I add an epoch to my ProceduralFairings.version file? I'm assuming the epoch was added because of the change is versioning.

@HebaruSan
Copy link
Member

Don't change your version file, but yes, that's the reason for the epoch. Probably makes sense to add it back in.

Sorry, something went wrong.

@rsparkyc
Copy link
Author

Ok, I'll update https://github.com/KSP-CKAN/NetKAN/blob/master/NetKAN/ProceduralFairings.netkan

Sorry, something went wrong.

@HebaruSan HebaruSan mentioned this issue May 30, 2018
Merged
@rsparkyc
Copy link
Author

Ahh, sweet, thx

Sorry, something went wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@HebaruSan @rsparkyc