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
opam confuses "A depends on B" with "B depends on A" #5035
Comments
FWIW, it seems to make a difference. I fixed the package (Blaisorblade/dot-iris@89c3c2b), reinstalled it (and recompiled
|
I don't know if you can still reproduce, but the output of Worth noting is that there are 2 different things at play here:
The reason for the 2nd point is that the solvers we use (SMT, in general) are black boxes that don't justify their choices.If you use unconventional solver criteria like maximising downgrades, the reasons are unlikely to make sense. |
That would imply there's a critical bug? Because #5035 (comment) recompiles |
Even taking that into account, the heuristics should not invent dependency edges that are outright absurd: |
The line You can check those "pending recompilations" with As for the original confusing
Pro tip: you can use |
Thanks for the tips. I tried to reproduce this, got more confusing outputs, but failed to identify any sensible patterns (or to capture cudf files for the strange results). I don't think I have tweaked my solver criteria:
|
Self-closing as unactionable. |
An example where opam's actually proposing the wrong choice:
Where coq-dot-iris is a locally installed copy of https://github.com/Blaisorblade/dot-iris/blob/master/coq-dot-iris.opam — I swear that's not meant to be a Bobby tables, and even passes opam lint. (I see the
name
is mistaken, and I'm testing if that makes a difference).The above was maybe cheating a bit, as I had removed the
default
repo from the switch (to avoid updatingocaml
yet). But if I put if back, I see that all dependencies ofcoq-dot-iris
are inverted, claiming thatcoq
,coq-iris
andcoq-autosubst
depend on coq-dot-iris.The text was updated successfully, but these errors were encountered: