Repository navigation
Update Cargo.lock to allow project to build against OpenSSL 4.1.0 - #321
Open
maximveligan wants to merge 1 commit into
Open
maximveligan wants to merge 1 commit into
maximveligan wants to merge 1 commit into
Conversation
…project building against OpenSSL 4.1.0
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
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.
Currently, asm-lsp refuses to build against OpenSSL 4.1.0, panicking with the following message:
The pull request contains the minimum changes required to get the project building again. The Cargo.lock file was generated using
cargo update -p, starting with openssl, and then updating whatever dependencies that ended up breaking. The Cargo.lock file in this PR is the result of the minimum required updates.