Repossess abandoned metanetkans#7516
Merged
HebaruSan merged 2 commits intoKSP-CKAN:masterfrom Nov 21, 2019
Merged
Conversation
Member
Author
|
Inflated these locally with a token and they worked fine. We may need to set a token in Jenkins. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problems
See KerboKatz/Netkan#11 and Y3mo/SETI-NetKAN#2; these modules have metanetkans with bad or outdated metadata that users have noticed and reported. We have reached out to the authors to try to address these problems in their copies of the files, but so far neither has responded.
Changes
Now the contents of these metanetkans are pulled back into their main netkans, with the fixes from the above pull requests applied.
@Y3mo or @KerboKatz, if you want to have these files back, let us know and we can collaborate on the problems users have noted and how to address them. Otherwise we are happy to maintain them going forward.