Skip to content
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

Closed
mboes opened this issue Jan 11, 2016 · 0 comments
Closed

stack --nix --resolver doesn't work as expected #1641

mboes opened this issue Jan 11, 2016 · 0 comments
Assignees

Comments

@mboes
Copy link
Contributor

@mboes mboes commented Jan 11, 2016

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:

$ stack new --bare --resolver lts-4.1 foo
$ stack --nix --resolver lts-2.22 build
...

Compared to:

$ stack --nix --resolver lts-2 build
Selected resolver: lts-2.22
Compiler version mismatched, found ghc-7.10.2 (x86_64), but expected minor version match with ghc-7.8.4 (x86_64) (based on resolver setting in /tmp/foo/stack.yaml).
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
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants
You can’t perform that action at this time.