[CORE UPDATE - PART VI] Fix scrypt #1547
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
6 tasks
21e0778 to
b56926b
Compare
Because since the python/openssl build system changed this recipe stopped to work.
b56926b to
39c6b5b
Compare
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.
This is one more part for the pr #1537 (discussed previously in #1460 and #1534)
Here I fix scrypt recipe to make it work with the core-update pull request, which also contains a new version of the openssl libs. Also grants compatibility for both versions of python.
Note: this has to be merged only when the core-update has been merged because it depends on the new python2 recipe and the openssl libs (1.1)