-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Nightly regression: The SSL certificate is invalid #3340
Comments
Lots of people reporting this problem today. cc @alexcrichton |
On IRC camlorn said the workaround for #598 worked for this too. |
This commit includes alexcrichton/git2-rs@a8f4a7faa which switches the order of initialization of libgit2. That commit ensures that the relevant env vars which a statically linked OpenSSL needs to function are set before libgit2 is initialized to ensure that libgit2 uses them. This was regressed accidentally in alexcrichton/git2-rs@071902aa when initialization was tweaked. Closes rust-lang#3340
Fixed in #3342 |
Bump git2 dep to fix SSL paths This commit includes alexcrichton/git2-rs@a8f4a7faa which switches the order of initialization of libgit2. That commit ensures that the relevant env vars which a statically linked OpenSSL needs to function are set before libgit2 is initialized to ensure that libgit2 uses them. This was regressed accidentally in alexcrichton/git2-rs@071902aa when initialization was tweaked. Closes #3340
FWIW, that #598 workaround isn't quite right for Fedora 25 -- instead it's |
The new nightly doesn't include the new Cargo, maybe the nightly build of Cargo is broken?
|
A new rust nightly didn't go out, so a new Cargo nightly didn't go out. The fix isn't in nightlies. |
ci: work around rust-lang/cargo#3340 Today's "rust up" didn't give me a fixed Cargo so let's work around the problem to fix Travis builds.
This commit includes alexcrichton/git2-rs@a8f4a7faa which switches the order of initialization of libgit2. That commit ensures that the relevant env vars which a statically linked OpenSSL needs to function are set before libgit2 is initialized to ensure that libgit2 uses them. This was regressed accidentally in alexcrichton/git2-rs@071902aa when initialization was tweaked. Closes rust-lang#3340
This is also experienced in Arch Linux rolling release. Pretty excited to come find there's a fix on the way. |
New nightly doesn't contain a new cargo, still from 2016-11-26, rustc is from 2016-12-01. |
Ah I can't believe I forgot about that, this is now a rustup issue -- rust-lang/rustup#844 |
Could you (I think @alexcrichton and @brson) please also do a postmortem on this issue? From what I can see the bug was introduced in |
@sanmai-NL yes I can try to write something up when everything is working again. Unfortunately I don't know how to test this, it's a very specific issue that seems like it could greatly complicate the test infrastructure naively at least. |
We're having cargo trouble on rust-num/num#243, and it appears to be a new regression in the nightly. Note the initial Travis build succeeded, which was using
cargo 0.16.0-nightly (b26d672 2016-11-25)
. Then several homu builds have all failed usingcargo 0.16.0-nightly (3568be9 2016-11-26)
.I confirmed the error locally after updating to the same cargo, running on Fedora 25.
The text was updated successfully, but these errors were encountered: