-
Notifications
You must be signed in to change notification settings - Fork 239
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
Attribute resourceRepo
missing when evaluating call-cabal-project-to-nix.nix
#2252
Labels
bug
Something isn't working
Comments
It looks like there is a bug in the haskell.nix cabal.project parser. It does handle trailing whitespace correctly. Workaround is to delete the trailing white space from the |
hamishmack
added a commit
that referenced
this issue
Sep 24, 2024
hamishmack
added a commit
that referenced
this issue
Sep 24, 2024
hamishmack
added a commit
that referenced
this issue
Sep 24, 2024
hamishmack
added a commit
that referenced
this issue
Sep 24, 2024
Thanks for the fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I am attempting to produce a Nix flake of the Plutus Pioneer Program so that I could use
nix develop
instead of Docker (I got some network problem which caused the Docker image to fail at a cloning step repeatedly).I followed this guide to integrate with the existing
cabal.project
file and eliminated the sha256 reference problem with the dependencies.However, the next problem is that Nix failed to evaluate
call-cabal-project-to-nix
because the attributesourceRepo
is missing fromx
, which I assume is the variable for the source object.This is a deeply nested function call, so it isn't immediately clear to me how to I can pass the correct attribute to it. Furthermore, the fetching functions seem to be dependent on the remote resources, which appears to be missing the mentioned attribute.
System information:
x86_64-linux
Steps To Reproduce
cabal.project
.Additional Context
I am still new to Nix so I am not sure how to resolve this problem.
The text was updated successfully, but these errors were encountered: