-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version on crates.io (0.3.0) does not support openssl 1.1.1 #245
Comments
Thanks for the report! @ordian, I saw you merged some PRs just now. Do you have time to bump request (and other crates if useful) and make a release? |
Hey Pascal! Was planning to, but I'm on a bad wifi right now (and for the rest of the week), so you might as well do it yourself ;) The reqwest is bumped already btw. |
Cool, will do so when I get home :)
… Am 24.09.2018 um 11:35 schrieb Andronik Ordian ***@***.***>:
Hey Pascal! Was planning to, but I'm on a bad wifi right now (and for the rest of the week), so you might as well do it yourself ;) The reqwest is bumped already btw.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Merged
Published: https://crates.io/crates/cargo-edit/0.3.1 |
Can confirm it works! 👍 |
Awesome, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running
cargo install cargo-edit
resulted in an "unknown openssl version" error reported by the rust-openssl crate, which was built as version 0.9.x. My system-installed openssl is 1.1.1, and it seems rust-openssl 0.9.x can't detect that.The recent update of
reqwest
seems to already have bumped the dependency up on master, and cloning the current master and runningcargo install --path .
worked fine.So probably doing a new release to crates.io would be a good idea.
The text was updated successfully, but these errors were encountered: