-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Restore Mirage build in CI after upstream fixes #344
Comments
You'll need to wait for a release of the mirage tool -- with mirage/mirage#1559 being merged. I will ping you here once I think this should be a smooth sail. :) |
Great, thank you! |
@hannesm I see the tool has been released with that PR. Is this ready for attention again? |
Oh yes indeed. Sorry I forgot to notify you. With the latest mirage you should be able to get dream-mirage and its examples working :) If you need help with that, let me know and I'll try to find some time to look into that. |
Is it possible that building The central issue I am running into is I assume this broke with a888e44, which removed all vendored dependencies and the corresponding I also tried migrating away from the vendored dependencies in |
During #337 we discovered that many of the dependencies of
dream-mirage
are still being updated to mirage-crypto 1.0.0. This is fine, but it eventually prevented us from getting the Mirage build working again within a reasonable amount of time. This issue is a reminder to try it again once robur-coop/ocaml-letsencrypt#34 is released, and any other dependencies that are still waiting that we may discover subsequently.The text was updated successfully, but these errors were encountered: