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

Base.LibGit2 test fails, Pkg.update() error #26168

Closed
zhangliye opened this issue Feb 23, 2018 · 3 comments
Closed

Base.LibGit2 test fails, Pkg.update() error #26168

zhangliye opened this issue Feb 23, 2018 · 3 comments

Comments

@zhangliye
Copy link

zhangliye commented Feb 23, 2018

  1. I got the following error when I tried to update the packages. I use Pkg.checkout(“CSV”) to get the latest version of CSV.jl. Today, I called Pkg.free(“CSV”). After doing this, I cannot update the packages. (Window 7, pro, 64bit, Julia0.6.2)
    1
  2. When I run the test of “libgit2”, and the test fails as follows.
    Base.runtests("libgit2")
    2
    3
@zhangliye
Copy link
Author

zhangliye commented Feb 23, 2018

According to the explanation by [avik] , this could be caused by the dropping support for old cipher suits by Github. (https://discourse.julialang.org/t/pkg-update-error-base-libgit2-test-fails/9272/7)

Github dropped support for old cipher suits last night. Apparently our windows MbedTLS builds ask for old versions. Julia on Linux works for 0.6, but fails on 0.5.

"Last year we announced the deprecation of several weak cryptographic standards. Then we provided a status update toward the end of last year outlining some changes we’d made to make the transition easier for clients. We quickly approached the...
https://githubengineering.com/crypto-removal-notice/"

This does look like a critical issue (at least on windows – 0.5 is really really unsupported at this time for linux), and hopefully we’ll come up with a workaround as the day goes by.

@KristofferC
Copy link
Sponsor Member

The LibGit2 failures seems to have something to do with different line endings \r\n vs \n which I don't think is related to the first issue.

@andreasnoack
Copy link
Member

The first part of this is a dup of #26167 and given that libgit2 has completely changed in 0.6 it is probably not worth keeping this open for the second issue. Please reopen or comment if you disagree.

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

3 participants