-
Notifications
You must be signed in to change notification settings - Fork 238
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
Custom stack resolver in stack.yaml fails #1157
Comments
I found out in libera.chat#haskell.nix that this is not a bug but something that nix intentionally doesn't allow. |
It appears there is an option thanks to @balsoft I came up with this but still have an issue:
Output:
|
It seems this is working, but two things made it tricky:
After addressing both of those though things work! |
When I try your exact example I get:
|
Here's a reproduction using your flake.nix expression and a stack manifest with your resolver in resulting in https://github.com/locallycompact/custom-stack-resolver-bug |
Ok, the name: field needs to be in the resolver, for some reason I'd convinced myself it was going in the stack.yaml. Ignore me. |
Ok, related though is this behaviour, setting:
is a valid stack configuration, but this will fail in stack2nix with the fetchurl error above. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I can work around this by inlining the contents of that resolver in changing packages to extra-deps So I know I have everything else working. Sadly my team needs that for other stuff and doesn't see the work around of removing the resolver and using a plain stack.yaml as an option.
Results in:
Full log:
The text was updated successfully, but these errors were encountered: