Inspired by an ask.sagemath <https://ask.sagemath.org/question/38692/use-ttest-from-r-in-sage/> question, Trac#23980 <https://trac.sagemath.org/ticket/23980> adds a couple usage hints to the r<tab> help text. This very minor patch is unproblematic.
Trac#24026 <https://trac.sagemath.org/ticket/24026>, on the other hand, upgrades R to the last current version. As usual, special attention is needed on our problem children of platforms (namely Mac OS X and Erik's Cygwin-64 port). All our current patches have been rebased against the current version ; no new patch is needed on Debian. However, I still have doubts about our decision to lift upstream's requirement of an https-enabled version of the SSL libraries (meaning OpenSSL, nowadays...). Does the ongoing OpenSSL's change of license change this situation (and our decision) ? On Debian testing, both patches pass ptestlong with no failures whatsoever. R sort-of passes its own test suite (i. e. I get a couple of expected, announced failures, analogous to what we get with Python's test suite). -- Emmanuel Charpentier -- 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.
