-
Notifications
You must be signed in to change notification settings - Fork 525
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.
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
Support Ubuntu 20.04 and unify dockerfiles across debian/ubuntu #10194
Merged
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
…ing image as codename focal
… based off of the official release branch
…n the rosetta container officially and try to combine the build deps stages back together
…buntu and debian and enable end-to-end Focal Fossa pipeline
…MinaToolchain builds for Focal
…stently now that PoC is working
…oroughly and document the staged dockerfile more
… same degree as 1 and 4
…python2 to avoid dependency issues elsewhere
… 3 sections to distinguish each platform
… ubuntu:focal is the default deb_codename and image
…support to build-release-archives.sh
…uster toolchain for all of the old code
…es for ubuntu support
…try the new toolchain images
…etch-from-rosetta-tag
…s to support scripts/require-ppxs.py
…eflect python3 dependency change
…etch-from-rosetta-tag
… with some Stretch parts shared and more consistent formatting in MinaArtifact.dhall
…/ubuntu toolchains
…ve impish as its harder to support
…ackages cause CI to hang, keep building bionic packages with Stretch instead
…etch-from-rosetta-tag
This was referenced Feb 11, 2022
QuiteStochastic
approved these changes
Feb 11, 2022
stevenplatt
approved these changes
Feb 11, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the reported merge conflicts, I don't spot any items to flag in the code.
The conflicts are resolved in #10212 which will merge first |
… on MonoRepo.dhall
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.
Explain your changes:
stretch
. In practice these could even be identical packages with different manifests but this is saved for a future PR.Explain how you tested your changes:
Checklist: