Remove constraints on package versions in conflicts, it's unsupported #23736
Conversation
After a debugging session with @kit-ty-kate as part of fixing tarides/opam-monorepo#349 and ocaml-opam/opam-0install-solver#46 we realized that OPAM doesn't support resolving package variables in `conflicts` fields (the linter complains about this in `depends` fileds but not in `conflicts` fields, but the solver never resolves these variables). So this constraint doesn't do anything in OPAM and it causes issues in the opam-0install-solver which attempts to resolve them.
|
@kit-ty-kate can we merge this or we should wait to avoid triggering rebuilds? |
|
The package linting is pointing out that some fields are missing. |
|
@tmcgilchrist None of the |
|
No need to make any other changes. The ocaml-options packages are special in that respect, they only turn on or off flags in the ocaml compiler packages and mark mutual incompatibilities. You can ignore these warnings and errors in this case. For compiler packaes, we wait for thumbs up from compiler maintainers and if there is a risk of retriggering builds in many switches for non-critical changes, we wait for a release and bulk together the merge of the compiler changes. |
|
Lets go ahead and get this in, as it's a violation of the opam format spec. |
After a debugging session with @kit-ty-kate as part of fixing tarides/opam-monorepo#349 and ocaml-opam/opam-0install-solver#46 we realized that OPAM doesn't support resolving package variables in
conflictsfields (the linter complains about this independsfileds but not inconflictsfields, but the solver never resolves these variables). So this constraint doesn't do anything in OPAM and it causes issues in the opam-0install-solver which attempts to resolve them.