Skip to content
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

Update of opam-repository commit to retrieve solo5 0.7.5 #167

Merged
merged 2 commits into from Dec 7, 2022

Conversation

hannesm
Copy link
Member

@hannesm hannesm commented Dec 7, 2022

This fixes #166

@palainp
Copy link
Member

palainp commented Dec 7, 2022

Is there a way to exclude solo5 before 0.7.5 ? Solo5 is currently not restricted in config.ml.

@hannesm
Copy link
Member Author

hannesm commented Dec 7, 2022

Since solo5 is a dependency of ocaml-solo5, and not of the unikernel (and thus installed in the opam switch), we can't easily specify this. What we can do:

  • mark old solo5 as available: false in opam-repository
  • add a lower bound to the mirage tool in respect to solo5

Neither is optimal. On the flipside, our build process uses the latest opam repository commit, and there the opam solver will pick solo5 0.7.5. I reproduced this built on builds.robur.coop (sorry, there may be DNS issues), and will cut a release with this change.

@hannesm hannesm merged commit 09740b7 into mirage:main Dec 7, 2022
@hannesm hannesm deleted the update branch December 7, 2022 19:42
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.

Mirage v0.8.x DoS from untrusted Qube by sending arbitrary UDP payload
2 participants