Alexander Bantyev
Alexander Bantyev
This is fixed by https://github.com/ocaml/dune/pull/11801 . I will keep this open until it lands in a dune release, that dune release lands in `opam-repository`, and that version of `opam-repository` gets...
The fix has been released now, and with the opam-repository repin the repro case succeeds out of the box.
Looks like the tests are trying to call `opam` and thus doesn't actually work. I'd try disabling the tests first, just to see it if helps.
Actually, I got a different error from you. I fixed that error, so now `nix build github:tweag/opam-nix#opam-dune-lint.latest` works.
Hmmm, interesting :) I'll see if just faking `opam config env --sexp` will let it go further, but somehow I'm not hopeful.
Ah, I forgot to report on my findings. I remember that when I made a fake `opam` script that produced the correct output for `opam config env --sexp`, it failed...
I've been busy with a lot of other things, and as such didn't pay any attention to this project. I apologize for that. I've now granted maintainer status to @GTrunSec....
I think another solution would be to filter out the `opam` file for `a.opam` when you're building the `b` package somehow.
> @balsoft if I correctly understood your suggestion: the problem is that we would like to have a single nix shell to build all packages. With your suggestion, for nix...
> In any case it doesn't work, I have the same error as in the original issue: Ah, you may also want to add your original override ```nix final: prev:...