This is now Trac#22058 <https://trac.sagemath.org/ticket/22058>.
Advice requested about what to upgrade to : 2.10.2 is abou 11 weeks old, 2.11.0 about two weeks old, and might be judged a bit wet behind the ears ; OTOH, it has been probably checked against openssl's newfangled version. For information, 2.11.0 has been in Debian unstable for 9 days, and has a bug filed against it, which complains about a missing dependency for gitweb (which seems unrelated...). I'm tempted to go to 2.11.0, but I'm eager to listen to advice. HTH, -- Emmanuel Charpentier Le mercredi 14 décembre 2016 23:36:19 UTC+1, Dima Pasechnik a écrit : > > > > On Wednesday, December 14, 2016 at 10:30:14 PM UTC, François wrote: >> >> On 15/12/16 11:17, Dima Pasechnik wrote: >> > IIRC, Sage's current git also does not build on OSX properly, and this >> > was also related to SSL. >> > I'd open a ticket to upgrade to the current stable git (2.10.2, I >> guess). >> > >> > >> Definitely. You are encouraged to open a ticket. And yes some OS X >> problem are related to SSL. However OS X ship with a recent enough git >> to do sage work. >> > > except that this makes it unclear how one can ship a fully functioning > (with SSL) Sage binary on OSX > that does not depend on system git being available (and the latter I > presume needs Xcode). > > >> >> Francois >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
