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

MonadFail not in scope when building on GHC 8.4 #139

Open
parsonsmatt opened this issue Nov 18, 2022 · 7 comments
Open

MonadFail not in scope when building on GHC 8.4 #139

parsonsmatt opened this issue Nov 18, 2022 · 7 comments

Comments

@parsonsmatt
Copy link
Contributor

See persistent-mongoDB failure to compile.To fix, y'all need to put lower bounds on base for these releases as Hackage revisions, and then add support for GHC 8.4.4 or drop it in the actual cabal file

@parsonsmatt
Copy link
Contributor Author

Fortunately, this is limited to mongoDB-2.7.1.2 - a single Hackage revision ought to fix it :)

@Bodigrim
Copy link

As a Hackage trustee, I added the missing lower bound in https://hackage.haskell.org/package/mongoDB-2.7.1.2/revisions/

@parsonsmatt
Copy link
Contributor Author

This issue came up again with mongoDB-2.7.1.3. @Bodigrim Any chance we could get another revision? I made a PR #152 to fix the issue.

@parsonsmatt
Copy link
Contributor Author

Version 2.7.1.4 was released with a fix, but the hackage revision is important still because the solver will see that base does not match and try 2.7.1.3, which will trigger the issue.

@VictorDenisov
Copy link
Member

Last time I checked it wasn't possible to update a once uploaded package. I'll take a look.

@parsonsmatt
Copy link
Contributor Author

You can use a Hackage revision to edit the metadata, including package dependency bounds. You'd click the version linke for 2.7.1.3, then in the bottom left, there's a link edit package information. You can use that to edit the version bounds.

image

@Bodigrim
Copy link

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

Successfully merging a pull request may close this issue.

3 participants