-
Notifications
You must be signed in to change notification settings - Fork 7
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
metadata revision for package memory #422
Comments
@wrengr Could you please spell out how exactly the revision should look like? Currently it says:
And I am getting this behavior:
|
doesn't trigger cabal-install solver backtracking. It will solve for it but fail to build. There are issues about this in |
Revisions are limited in scope (e.g. Hackage forbids removing the
@wrengr Is this what you want? |
@andreasabel you can always add |
Ok, did that. |
This is separate from the maintainership and deprecation issues discussed in #419.
The changelog for 'memory' says that version 0.18 drops support for ghc < 8.8, and yet there is no lower bound on its 'base' dependency. Can we get a metadata revision to make this explicit and help cabal not fall over.
(Yes I know ghc-8.6.5 was released 2019-04-23 and is therefore no longer supported by most folks; but I have reasons, and it's just good hygiene anyways)
The text was updated successfully, but these errors were encountered: