GHC 9.10 support #141
Closed
GHC 9.10 support #141
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
postgresql-libpq has made the required changes but has not yet released to github. Proposed PR for other required updates once that is done
|
Removed temporary cabal.project entry for postgresql-libpq |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I know there is issue #139, so adding this as a draft so that once everything is ready hopefully this helps with the last few required changes.
I think the blockers for haskellari/postgresql-libpq#60 are sorted
E.g. inspection-testing fixed today with a hackage metadata release
What I've done here is
cabal outdatedreports nothing now)cabal.projectnewer entry forcryptohashcabal.projectentry forpostgresql-libpq:9.10just to prove that it all works. Once that is merged this should obviously be removed.Hope this helps