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.

Sign up for GitHub

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

Jump to bottom

hledger-* and base-compat #3706

Closed
6 tasks
mihaimaruseac opened this issue Jun 5, 2018 · 5 comments
Closed
6 tasks

hledger-* and base-compat #3706

mihaimaruseac opened this issue Jun 5, 2018 · 5 comments
Labels
failure: bounds

Comments

@mihaimaruseac
Copy link
Contributor

mihaimaruseac commented Jun 5, 2018 •
edited
Loading

Due to the revision adding an upper bound on base-compat for hledger-* package the following constraints are unsatisfied

base-compat-0.10.1 (Simon Hengel [email protected] @sol) is out of bounds for:

hledger-lib-1.9 (Simon Michael [email protected] @simonmichael) is out of bounds for:

I will have to upper bound hledger packages until this is fixed, as upper bounding base-compat will harm many more packages.

        - hledger < 1.9.1
        - hledger-lib < 1.9.1
        - hledger-ui < 1.9.1
        - hledger-web < 1.9.2
        - hledger-api < 1.9.1
        - hledger-interest < 1.5.2
mihaimaruseac added a commit that referenced this issue Jun 5, 2018
@mihaimaruseac
Upper bound several hledger-* packages (#3706)
3b9ed4b
@simonmichael
Copy link
Contributor

Ack.. thank you, I will do a minor release to fix this soon.

@simonmichael simonmichael mentioned this issue Jun 5, 2018
Closed
@simonmichael
Copy link
Contributor

For users of old ghc, I added revision 1 restricting base-compat's upper bound to fix the build.
For stackage nightly, the previous revision 0 is what's needed.
@mihaimaruseac do you think it would make sense to add my packages temporarily to the no-revisions list, forcing stackage to use their rev 0 ?

@mihaimaruseac
Copy link
Contributor Author

I think that can also work

simonmichael added a commit to simonmichael/stackage that referenced this issue Jun 13, 2018
@simonmichael
allow latest hledger* again, but stick to revision 0 (commercialhaske…
35cf6d5 
…ll#3706)

Revision 1 was good for cabal installers with old GHC, but bad for
stackage nightly. This should fix the latter. I might continue this
policy - use revisions to patch up the cabal install experience,
but avoid them in stackage.
@simonmichael
Copy link
Contributor

Great! I do that. #3737

@mihaimaruseac
Copy link
Contributor Author

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
failure: bounds
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@simonmichael @mihaimaruseac