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 init doesn't suggest --solver if no resolver matches requirements #2525

Closed
sjakobi opened this issue Aug 22, 2016 · 4 comments
Closed

Comments

@sjakobi
Copy link
Member

sjakobi commented Aug 22, 2016

~/tmp $ stack unpack hoogle-5.0.2
Unpacked hoogle-5.0.2 to /home/simon/tmp/hoogle-5.0.2/
~/tmp $ cd hoogle-5.0.2/
~/t/hoogle-5.0.2 $ stack init
Looking for .cabal or package.yaml files to use to init the project.
Using cabal packages:
- hoogle.cabal

Selecting the best among 8 snapshots...

* Partially matches lts-6.13
    haskell-src-exts version 1.17.1 found
        - hoogle requires >=1.18 && <1.19

* Partially matches nightly-2016-08-22
    haskell-src-exts version 1.17.1 found
        - hoogle requires >=1.18 && <1.19

...

Selected resolver: lts-6.13
Resolver 'lts-6.13' does not have all the packages to match your requirements.
    haskell-src-exts version 1.17.1 found
        - hoogle requires >=1.18 && <1.19

This may be resolved by:
    - Using '--omit-packages to exclude mismatching package(s).
    - Using '--resolver' to specify a matching snapshot/resolver

~/t/hoogle-5.0.2 $ stack --version
Version 1.1.3, Git revision 63f203d7886801c9ec3c303db0c459f08687a3c8 (dirty) (4017 commits) x86_64 hpack-0.14.0

Using --solver should be the first suggestion, before --omit-packages and --resolver.

@harendra-kumar
Copy link
Collaborator

Introduced by #2031 / cbbfb95#commitcomment-17586844. Slipped off my radar.

@mgsloan
Copy link
Contributor

mgsloan commented Aug 23, 2016

Argh, yeah, I had some edits to fix, but didn't make it into a commit yet. My mistake!

Anyone should feel free to address this, the edits are from quite a while back.

@vlad-shatskyi
Copy link

Already fixed by 00cf71c.

@mgsloan
Copy link
Contributor

mgsloan commented Nov 8, 2016

Good point @ShockOne , I forgot there was a ticket for this.

@mgsloan mgsloan closed this as completed Nov 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants