-
Notifications
You must be signed in to change notification settings - Fork 698
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
cabal gen-bounds fails when using Nix integration #6731
Comments
/cc @mightybyte |
I'm still experiencing this issue. In the meantime, I'm using the |
This bug is still around |
Does anybody have an idea if this is blocked on something? Did someone mention exact-print as the blocker? |
I don't think it is blocked on anything. That said, I'm not sure it is a bug. When --enable-nix is set, all commands are run in a subprocess, after nix-shell has been entered, using shell.drv. So any cabal command enters the nix-shell this way when --enable-nix is set. Correspondingly any cabal command would fail this way if the drv were missing. In which case this bug report is just that this particular command fails that way? |
It doesn't have a v1-/v2- distinction. It's a very simple command that reads a single cabal file and doesn't accept any flag except global ones |
@mhwombat: I'm trying to understand what severity this issue has and so if the workaround is sufficient. Is the main problem for you that you want to keep |
BTW, people report in #4646 and other tickets with the nix label that |
@Mikolaj Thank you for following up on this. For me, it's just a minor annoyance to have to specify --disable-nix for this command. I didn't expect this particular command to need the .drv file, so the error message didn't help me, and the only way I found the solution was by searching the web. My suggestions for resolving this are, in decreasing order of preference:
I don't bother with the |
I'm asking, in particular, because we recently debated whether to remove --enable-nix (will probably happen in the long run) or to improve the docs and we ended up with #8333, which is probably incorrect in light of your experience. Or at least could be improved, which would also be a way to put this ticket to rest and make it easier for people to find an answer in a similar situation. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
If you set
nix: True
in~/.cabal/config
you can get the same error.Entering a nix shell first doesn't solve the problem.
Here's a version with
verbose
output.Expected behavior
I expect
cabal --enable-nix gen-bounds
to produce the same output ascabal --disable-nix gen-bounds
. I don't understand why this this particular command would be looking for a.drv
file. I would have thought that it only needs to examine the.cabal
file.System information
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: