deferred v18.x release - to apply in v19.0? #35
Conversation
This file contains 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
…les and some tidying - althought perhaps we should just copy and update upstread examples?
- group relevant code - remove redundant canvas workarounds - additional cache cleaning - reduces ISO by 200M! - leave canvas init script patch - ease future canvas update - update name of canvas "super" admin for clarity - set https_proxy during install - only http_proxy set previously - other minor tweaks/tidy
JedMeister
changed the title
JedMeister
changed the title
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.
Due to issues building Canvas, the v18.1 release will now be a patch of v18.0 - as per PR:
turnkeylinux/buildtasks#89
The changes applied to Canvas in that patch are synced with the build code too - as per PR:
#36
The changes in this PR still have some value IMO so I will leave it open for now. However, it should be considered a PoC rather than an intended update "as is". At the very least it will almost certainly need refactoring/rewriting/rebasing.
This PR succeeds #34 (which I've just closed).Proper fix for turnkeylinux/tracker#1965
Closes turnkeylinux/tracker#1978
Closes turnkeylinux/tracker#1979
Hopefully closes turnkeylinux/tracker#1977 - but needs testing to confirm