Skip to content

Conversation

@briaguya0
Copy link
Contributor

@briaguya0 briaguya0 commented Mar 14, 2023

This PR updates the LUS version used in develop-khan to be https://github.com/briaguya-ai/libultraship/tree/khan

As of this PR, that branch is just LUS as of khan with Kenix3/libultraship#145 cherry-picked in

If we'd rather have khan use an LUS fork that lives somewhere other than https://github.com/briaguya-ai/libultraship/ I'll gladly change this to use a different fork, but I know there will not be a "LUS stable" available on https://github.com/Kenix3/libultraship

Having divergent LUS versions will be slightly annoying for the next "khan -> dev" merge, but after that's resolved it should be a non-issue

This has been tested

  • On a Switch running 16.x, Atmosphere 1.5.x (verified by McBedtime)
  • On a Switch running 15.x, Atmosphere 1.4.x (verified by @briaguya-ai)

Build Artifacts

@Malkierian
Copy link
Contributor

Is this version of LUS going to have the sequence duplication issue?

@briaguya0
Copy link
Contributor Author

Is this version of LUS going to have the sequence duplication issue?

No, it is just LUS as of khan with Kenix3/libultraship#145 cherry picked in

@briaguya0 briaguya0 merged commit 0ade1aa into HarbourMasters:develop-khan Mar 14, 2023
@briaguya0 briaguya0 deleted the atmosphere-fix branch March 14, 2023 08:59
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

Successfully merging this pull request may close these issues.

3 participants