removed upper bound on quickcheck in test-framework-quickcheck2 #48
Conversation
This file contains hidden or 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
|
@batterseapower Can you please apply this or at least bump the upper bound to 2.6? |
|
Hi. This makes test-framework incompatible with the the haskell platform. Can we have a compatibe upload to Hackage soon? Thanks, |
|
Any news on this front? Note that this is also filed as #50. |
|
Just checking: What is the maintenance status of test-framework? |
Contributor
|
This is fixed in haskell/test-framework. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The upper bound on quickcheck < 2.6 was causing cabal to resolve back to test-framework-quickcheck2-0.2.4 (or thereabouts) which no longer builds.
This change fixes that, but without knowing why the upperbound was introduced, I'm not sure if removing it will cause other problems.