Re: [sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-16 Thread Emmanuel Charpentier
Trac#22058 upgrades Sage's git to 2.11.0 and needs your review... HTH, -- Emmanuel Charpentier Le mercredi 14 décembre 2016 23:50:54 UTC+1, Emmanuel Charpentier a écrit : > > This is now Trac#22058 . > > Advice req

Re: [sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-15 Thread Emmanuel Charpentier
It was a typo for "SOS" :-). But it could as well have been "SOA". -- Emmanuel Charpentier Le 15 déc. 2016 16:46, "Dima Pasechnik" a écrit : > > > On Thursday, December 15, 2016 at 2:27:33 PM UTC, Samuel Lelievre wrote: >> >> >> >> Emmanuel Charpentier: >> >> the solution was an SOT to the rel

[sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-15 Thread Dima Pasechnik
On Thursday, December 15, 2016 at 2:27:33 PM UTC, Samuel Lelievre wrote: > > > > Emmanuel Charpentier: > > the solution was an SOT to the relevant R package author, >> > > For the acronym-unexperts here, could you spell out SOT in full? > it could be Same Old Thing, or Sex On Text, or 30+ other

[sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-15 Thread Samuel Lelievre
Emmanuel Charpentier: the solution was an SOT to the relevant R package author, > For the acronym-unexperts here, could you spell out SOT in full? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivin

Re: [sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-14 Thread Emmanuel Charpentier
This is now Trac#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 info

Re: [sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-14 Thread François Bissey
On 15/12/16 11:36, Dima Pasechnik wrote: 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). I'll admit that I cannot check that right now. In fact I am no

Re: [sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-14 Thread Dima Pasechnik
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 > gues

Re: [sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-14 Thread François Bissey
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 rela

[sage-devel] Re: Our current git doesn't build anymore with recent (>=1.1) openSSL

2016-12-14 Thread Dima Pasechnik
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). On Wednesday, December 14, 2016 at 10:05:09 PM UTC, Emmanuel Charpentier wrote: > > On my way to understant what can and can