Closed ogrisel closed 6 years ago
Oops - sorry I missed this issue. I don't know why this problem came up now, but the fix is to install certifi - as in:
https://github.com/MacPython/numpy-wheels/commit/c139b75fd07db3d4f83e50e6f6eacc7002368384
See also: https://github.com/matthew-brett/multibuild/issues/178
@matthew-brett I have released wheelhouse-uploader 0.9.7 with an explicit dependency on certifi but that does not seem to solve the SSL verification issue on this appveyor build:
https://ci.appveyor.com/project/sklearn-ci/scikit-learn/build/job/9knfe7ggk6emogto
The log shows that certifi-2018.4.16 has been installed (as a dependency from wheelhouse-uploader 0.9.7).
You've still got '--no-ssl-check' set :)
ah yes, thanks.
@matthew-brett I just realized that I am the sole maintainer of wheelhouse-uploader. I've just sent you a github invite to get push rights on this repo.
I would also like to give you the rights on pypi.org if you agree. I would need your pypi.org username (or email address) to do so.
That would increase the bus factor to 2 for this infra tool project.
Thanks - yes - that's fine - my PyPI username is matthew.brett
Done. Welcome on board :)
Closing the issue. I confirm that installing certifi and not using --no-ssl-check
fixes the issue on appveyor.
The fact that the --no-ssl-check
causes a SSL_VERIFY_FAILED error is probably a bug in its own respect but at least we now have a safe way to upload wheel from appveyor.
Recently we started to observe SSL: CERTIFICATE_VERIFY_FAILED errors on the appveyor build of scikit-learn, for instance:
We probably need to unpin the apache-libcloud dependency but that probably require to make a code update to wheelhouse-uploader itself.