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
So I've accidentally generated something similar to this opam file: opam-monorepo.opam
opam-monorepo.opam
opam-version: "2.0" depends: [ "opam-monorepo" ] dev-repo: "opam-monorepo" url { src: "https://github.com/ocaml/opam-monorepo.git" }
where the main problem is that the package depend on itself.
Surprisingly, the solver doesn't complain and write a lockfile with 0 entries.
0
If the opam file has another name (no cycle), the solver works as expected and writes a lockfile with 36 entries.
36
The text was updated successfully, but these errors were encountered:
Good cacth! I have a slight idea how this might happen and it shouldn't be too hard to fix!
Sorry, something went wrong.
No branches or pull requests
So I've accidentally generated something similar to this opam file:
opam-monorepo.opam
where the main problem is that the package depend on itself.
Surprisingly, the solver doesn't complain and write a lockfile with
0
entries.If the opam file has another name (no cycle), the solver works as expected and writes a lockfile with
36
entries.The text was updated successfully, but these errors were encountered: