Increase lower bound on crypton to >= 1.1 - #2
Open
sternenseemann wants to merge 1 commit into
Open
Conversation
http-client-tls >= 0.4 does not actually cause crypton >= 1.1 to be picked, but since aws uses ram now, the necessary ByteArray conversion instances are missing if a crypton version that depends on memory is picked.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
http-client-tls >= 0.4 does not actually cause crypton >= 1.1 to be picked, but since aws uses ram now, the necessary ByteArray conversion instances are missing if a crypton version that depends on memory is picked.
Publishing a Hackage revision with this change would help make some invalid install plans impossible. I've had cabal pick this combination (crypton < 1.1, aws >= 0.25.3) on its own a few times when building git-annex.