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

Can't build lens master #315

Closed
bitemyapp opened this issue Jun 15, 2015 · 4 comments
Closed

Can't build lens master #315

bitemyapp opened this issue Jun 15, 2015 · 4 comments

Comments

@bitemyapp
Copy link
Contributor

boura:lens callen$ stack build --prefetch --dry-run
Downloaded lts-2.14 build plan.
Fetched package index.
Populated index cache.
Checking against build plan lts-2.14
Downloaded lts-1.15 build plan.
Checking against build plan lts-1.15
Downloaded nightly-2015-06-15 build plan.
Checking against build plan nightly-2015-06-15
No matching snapshot was found for your package, falling back to: lts-2.14
This behavior will improve in the future, please see: https://github.com/commercialhaskell/stack/issues/253
Writing default config file to: /Users/callen/work/lens/stack.yaml
While constructing the BuildPlan the following exceptions were encountered:

--  While attempting to add dependency,
    Could not find package base-orphans in known packages

--  Failure when adding dependencies:
      base-orphans: needed (>=0.3 && <1), but not present in build plan
      bifunctors: needed (>=5 && <6), but 4.2.1 found
      profunctors: needed (>=5 && <6), but 4.4.1 found
      semigroupoids: needed (>=5 && <6), but 4.3 found
    needed for package: lens-4.11
@snoyberg
Copy link
Contributor

Why is this a bug? Is there a reason why lens master should be expected to build with LTS 2.14?

@gregwebs
Copy link
Contributor

Perhaps the implied suggestion is that stack should by default take packages from hackage if it helps with the build?
The problem for stack is that the package index being up to date effects things. So stack is going to need some level of user intervention.

If there is a cabal.config file is is safe to take package from there.

@snoyberg
Copy link
Contributor

Doing this is being tracked in #116

@snoyberg
Copy link
Contributor

Closing in favor of #116

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants