-
Notifications
You must be signed in to change notification settings - Fork 841
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
stack --nix --resolver doesn't work as expected #1641
Comments
mboes
added a commit
that referenced
this issue
Jan 11, 2016
Even when abstract resolver is provided. Fixes #1641.
mboes
added a commit
that referenced
this issue
Jan 11, 2016
Even when abstract resolver is provided. Fixes #1641.
mboes
added a commit
that referenced
this issue
Jan 11, 2016
Even when abstract resolver is provided. Fixes #1641.
mboes
added a commit
that referenced
this issue
Jan 11, 2016
Even when abstract resolver is provided. Fixes #1641.
mboes
added a commit
that referenced
this issue
Jan 12, 2016
Stack now selects the correct GHC version in the following cases: * an abstract resolver was given, * a concrete resolver was given, * a compiler version was given. Previously, we could only deal with concrete resolvers correctly. Fixes #1641.
mboes
added a commit
that referenced
this issue
Jan 12, 2016
Stack now selects the correct GHC version in the following cases: * an abstract resolver was given, * a concrete resolver was given, * a compiler version was given. Previously, we could only deal with concrete resolvers correctly. Fixes #1641.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Passing a concrete resolver on the command-line correctly overrides the resolver found in the stack.yaml, but passing an abstract resolver does not.
Example:
Compared to:
The text was updated successfully, but these errors were encountered: