On Saturday, May 26, 2018 at 7:43:14 PM UTC-4, Julian Rüth wrote:
>
> Thanks for reporting this and even providing a workaround :)
>
> You are right, Sage was built with libssl-dev but the final container had
> been missing openssl. I fixed it for the 8.2 build and pushed a new image
> to the Doc
Thanks for reporting this and even providing a workaround :)
You are right, Sage was built with libssl-dev but the final container had
been missing openssl. I fixed it for the 8.2 build and pushed a new image
to the Docker Hub.
julian
On Wednesday, May 16, 2018 at 10:06:54 PM UTC+2, Nathan Dun
*ping* Julian who built the 8.2 docker image...
On Thu, May 17, 2018 at 3:53 PM, Nathan Dunfield wrote:
>> In the interim, could you try to install OpenSSL and its development files
>> a,d reinstall Sage's pip ?
>
>
> Actually, I fixed the problem simply by installing the (non-development)
> Ubun
>
> In the interim, could you try to install OpenSSL and its development files
> a,d reinstall Sage's pip ?
>
Actually, I fixed the problem simply by installing the (non-development)
Ubuntu package "openssl". In particular, I did not need to reinstall or
rebuild any part of Sage itself. I'm
I have met this problem, which occurs when OpenSSL isn't available
systemwide (there is a saga somewhere in sage-devel's archive, around
spring 2017 IIRC...). I have personally checked that Sage's pip is (or was,
at the time) unable to use SSL when compiled against Gnu TLS alone...
This should
