Skip to content
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

OpenSSL version error during installation #1

Open
sridharraman opened this issue May 10, 2019 · 7 comments
Open

OpenSSL version error during installation #1

sridharraman opened this issue May 10, 2019 · 7 comments

Comments

@sridharraman
Copy link

Trying to install using cargo install timetable throws this error:

error: could not find timetable in registry https://github.com/rust-lang/crates.io-index

When I try to install from source, I get an error related to the version of OpenSSL:

error: failed to run custom build command for openssl-sys v0.9.23
...
This crate is only compatible with OpenSSL 1.0.1, 1.0.2, and 1.1.0, or LibreSSL
2.5 and 2.6.0, but a different version of OpenSSL was found. The build is now
aborting due to this version mismatch.

Any idea what I can do?

@vinc
Copy link
Owner

vinc commented May 10, 2019

Thanks for opening the issue! What OS and Rust/Cargo versions are you using?

The project has not been published on crates.io because at the time it was depending on a crate from a git repo, and that might not be necessary anymore. I'll look into updating the dependencies, see if I can publish it, and if the update might solve your problem.

@sridharraman
Copy link
Author

I am using Ubuntu 18.04 and the latest versions of Rust and Cargo.

@vinc
Copy link
Owner

vinc commented May 10, 2019

Strange, with Ubuntu 18.04 it seems that you have OpenSSL 1.1.0 and the openssl crate claim to be compatible with it. I found an issue with the next version 1.1.1 here: sfackler/rust-openssl#994

I updated all the dependencies of this project and switched from openssl version 0.9.23 to 0.9.24 so maybe that'll fix your issue if you try to build it again after pulling the change?

And I'll try it too later today on Arch Linux with the latest Rust and Cargo so if there's an issues with the latest version of OpenSSL on the system I'll probably be able to reproduce it.

I was also hopping that transitfeed has been updated in that time so I could publish the crates but that don't seem to be the case: https://github.com/bfrog/transitfeed/releases

@sridharraman
Copy link
Author

with Ubuntu 18.04 it seems that you have OpenSSL 1.1.0

I actually have 1.1.1b. Could that be the problem?

I re-pulled the changed code and tried building it. This is the error I get:

error: failed to run custom build command for openssl v0.9.24
thread 'main' panicked at 'Unable to detect OpenSSL version',

So, the option for me is to downgrade to 1.1.0?

@vinc
Copy link
Owner

vinc commented May 10, 2019

No don't downgrade, it's my project's responsibility to work with recent versions of OpenSSL if that's the issue. And it seems that this is indeed the issue! Worst case it seems that I'll need to adapt the build instructions while waiting for the openssl crate to be fixed.

@sridharraman
Copy link
Author

Thanks @vinc

For now, I have another container which has an older version of OpenSSL. It works fine there.

@vinc
Copy link
Owner

vinc commented May 10, 2019

Okay I could reproduce the problem on my Arch Linux computer with OpenSSL 1.1.1b! I updated the reqwest crate that has a lot of dependencies including openssl that got updated too. And now the issue is resolved I think.

I'll add @dependabot to this repo to stay up to date.

(I also found a lot of changes on the local repo of this computer that I had not committed, I'll have to check that)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants