We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In h2.opam we depend on hpack without any constraints. I suspect this is likely usually fine as the interface hasn't changed at all.
ocaml-h2/h2.opam
Line 20 in 9f9f29d
However, due to a behavior in opam-monorepo (tarides/opam-monorepo#331) this lack of constraint makes opam-monorepo choose the wrong version: mirage/mirage#1411 (comment)
To work around the behavior in opam-monorepo we could add a constraint "hpack" {= version} in h2.opam.
"hpack" {= version}
The text was updated successfully, but these errors were encountered:
Not opposed to it. Wanna send a PR?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
In h2.opam we depend on hpack without any constraints. I suspect this is likely usually fine as the interface hasn't changed at all.
ocaml-h2/h2.opam
Line 20 in 9f9f29d
However, due to a behavior in opam-monorepo (tarides/opam-monorepo#331) this lack of constraint makes opam-monorepo choose the wrong version: mirage/mirage#1411 (comment)
To work around the behavior in opam-monorepo we could add a constraint
"hpack" {= version}
in h2.opam.The text was updated successfully, but these errors were encountered: