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

Failed stack solver run suggests --omit-packaes flag, which doesn't exist #2031

Closed
mitchellwrosen opened this issue Apr 13, 2016 · 5 comments
Closed

Comments

@mitchellwrosen
Copy link
Contributor

@mitchellwrosen mitchellwrosen commented Apr 13, 2016

Obviously some code is being shared between stack init --solver and stack solver, but the latter doesn't have an --omit-packages flag. Still, I'm seeing this error message:

$ stack solver                                                                             [mitchell@arch]
Using configuration file: stack.yaml
Using cabal packages:
- haddock.cabal
- haddock-api/haddock-api.cabal
- haddock-library/haddock-library.cabal
- haddock-test/haddock-test.cabal

Resolver 'lts-5.12' does not have a matching compiler to build some or all of your package(s).
ghc-7.10.3 cannot be used for these packages:
    - haddock-api
ghc version 7.10.3 found
    - haddock-api requires >=8.0 && <8.2

However, you can try '--omit-packages to exclude mismatching package(s).
$ stack solver --omit-packages                                                           1 [mitchell@arch]
Invalid option `--omit-packages'

Usage: stack solver [--[no-]update-config] [--help]
  Use a dependency solver to try and determine missing extra-deps

@mgsloan
Copy link
Contributor

@mgsloan mgsloan commented Apr 13, 2016

Yup, that should be fixed, shouldn't be hard.

mgsloan added a commit that referenced this issue May 15, 2016
@mgsloan
Copy link
Contributor

@mgsloan mgsloan commented May 15, 2016

Fixed!

@mgsloan mgsloan closed this May 15, 2016
@harendra-kumar
Copy link
Collaborator

@harendra-kumar harendra-kumar commented May 23, 2016

@mgsloan I added a comment to the commit. stack init is not suggesting --solver after this change.

@mgsloan
Copy link
Contributor

@mgsloan mgsloan commented May 23, 2016

Due to this change I guess cbbfb95#diff-b8b3eca5371c1446794562093981903cL676 ?

Do you want to fix it or should I?

@harendra-kumar
Copy link
Collaborator

@harendra-kumar harendra-kumar commented May 23, 2016

Go ahead if you want to, I can only get to it by the weekend.

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.

None yet
3 participants