amazonka: fix build after hackage update #38496
Merged
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
shlevy
approved these changes
Apr 6, 2018
| amazonka-test = super.amazonka-test.overrideScope amazonkaOverrides; | ||
| in { | ||
| inherit amazonka amazonka-core amazonka-test; | ||
| }) |
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.
fixes #38306
Note that this partially resurrects an approach that was abandoned in #6584, so it may or may not be okay. cc @peti, @shlevy, and @fmap.
I got some leads about what direction to flail in from the "Journey into the Haskell NG infrastructure" postings, but I'm definitely still a newbie at the Haskell infrastructure, so might be missing something obvious. :)
Things done
build-use-sandboxinnix.confon non-NixOS)nix-shell -p nox --run "nox-review wip"./result/bin/)