Re: [sage-release] Re: Sage 6.4.rc0 released

Ah. Sorry for the noise. I was reading it as 6.5.rc0. On Sun, Dec 14, 2014, 21:06 Volker Braun wrote: The develop banch on https://github.com/sagemath/sage is currently at 6.5.beta2 which is where it should be. On Sunday, December 14, 2014 12:37:23 AM UTC+1, P Purkayastha wrote: I am restarti

[sage-release] Re: Sage 6.4.rc0 released

The develop banch on https://github.com/sagemath/sage is currently at 6.5.beta2 which is where it should be. On Sunday, December 14, 2014 12:37:23 AM UTC+1, P Purkayastha wrote: > > I am restarting a sage installation from scratch and realized that the > developer guide asks to clone from githu

[sage-release] Re: Sage 6.4.rc0 released

I am restarting a sage installation from scratch and realized that the developer guide asks to clone from github, but the github develop is not updated to the latest rc0. Perhaps the dev guide should give examples using git.sagemath.org, instead of github? On Thursday, October 30, 2014 10:12:20

[sage-release] Re: Sage 6.4.rc0 released

> > 35ae4fd Trac #16706: Update IML to 1.0.4 > > Turns out something here broke compilation on some Macs. Here's what I reported at the ticket (can continue conversation here): On an old Mac (slightly newer than my usual test machine, but still OS X 10.4 PPC) iml bails out with complaining abo

Re: [sage-release] Re: Sage 6.4.rc0 released

On 2014-10-31 21:33, kcrisman wrote: In general, how can I figure out what version of any Python site-package I am using, by the way? sage: import sagenb sage: sagenb '/usr/local/src/sage-config/local/lib/python2.7/site-packages/sagenb-0.11.0-py2.7.egg/sagenb/__init__.pyc'> -- You received thi

[sage-release] Re: Sage 6.4.rc0 released

http://trac.sagemath.org/ticket/17268 On Friday, October 31, 2014 8:33:19 PM UTC, kcrisman wrote: > > Bizarrely, after earlier today having things working fine, now I > unaccountably have the old notebook. I did sage -f sagenb several times > (and it unpacked the correct one) but no idea what h

[sage-release] Re: Sage 6.4.rc0 released

Bizarrely, after earlier today having things working fine, now I unaccountably have the old notebook. I did sage -f sagenb several times (and it unpacked the correct one) but no idea what happened, presumably due to some branch visiting at various times (though I don't recall having downgraded

[sage-release] Re: Sage 6.4.rc0 released

On OSX 10.9, I'm seeing sporadic failures with the zeromq test suite. If I run "./sage -f -c zeromq", then sometimes it passes, sometimes it fails with Invalid argument (ip.cpp:136) /bin/sh: line 1: 71673 Abort trap: 6 ${dir}$tst FAIL: test_shutdown_stress although the "Invalid argume

[sage-release] Re: Sage 6.4.rc0 released

Yes! On Friday, October 31, 2014 2:56:44 PM UTC, Dima Pasechnik wrote: > > doctest failures in ipython_notebook related to its dependence on > ssl. Should the corresponding (long) tests (9 out of 18) be marked as > optional? > > -- You received this message because you are subscribed to the G

[sage-release] Re: Sage 6.4.rc0 released

Fix is in http://trac.sagemath.org/ticket/1726 2 On Friday, October 31, 2014 12:24:47 PM UTC, Dima Pasechnik wrote: > building on Ubuntu 12.04 on an i7 Intel (that's my new Dell laptob, shipped with Ubuntu (!)) runs into trouble at ECM (unkn

[sage-release] Re: Sage 6.4.rc0 released

So gcc in Ubuntu 12.04 emits assembler that ubuntu's "as" doesn't understand, yay. On Friday, October 31, 2014 3:10:37 PM UTC, Dima Pasechnik wrote: > > Now building GMP-ECM... > [...] > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./x86_64 > -I/home/dima/software/sage/local/include > -I/h

[sage-release] Re: Sage 6.4.rc0 released

On 2014-10-31, Volker Braun wrote: > --=_Part_1806_1992617461.1414763378725 > Content-Type: text/plain; charset=UTF-8 > > Can you post the log for the failed ecm compile? GCC 4.6 is a bit old in > the tooth now, of course.. I suppose the relevant parts are (by the way, I notice it seems to b

[sage-release] Re: Sage 6.4.rc0 released

On 2014-10-30, Volker Braun wrote: > --=_Part_742_1112049983.1414678340265 > Content-Type: text/plain; charset=UTF-8 > > Notable changes are > > * OSX 10.10 support > * SageNB now can do 3d plots without Java, so it is usable again in chrome. > > Please test, especially if you are a notebook

[sage-release] Re: Sage 6.4.rc0 released

Can you post the log for the failed ecm compile? GCC 4.6 is a bit old in the tooth now, of course... On Friday, October 31, 2014 12:24:47 PM UTC, Dima Pasechnik wrote: > > On 2014-10-30, Volker Braun > wrote: > > --=_Part_742_1112049983.1414678340265 > > Content-Type: text/plain; charset=UT

[sage-release] Re: Sage 6.4.rc0 released

On 2014-10-30, Volker Braun wrote: > --=_Part_742_1112049983.1414678340265 > Content-Type: text/plain; charset=UTF-8 > > Notable changes are > > * OSX 10.10 support > * SageNB now can do 3d plots without Java, so it is usable again in chrome. > > Please test, especially if you are a notebook

[sage-release] Re: Sage 6.4.rc0 released

> > * OSX 10.10 support >> * SageNB now can do 3d plots without Java, so it is usable again in >> chrome. >> >> Please test, especially if you are a notebook user! >> > > For those testing, another thing to test is whether the Mac App binaries > build and work fine. > Also, we'll probably need

[sage-release] Re: Sage 6.4.rc0 released

Thanks for this release! Notable changes are > > * OSX 10.10 support > * SageNB now can do 3d plots without Java, so it is usable again in chrome. > > Please test, especially if you are a notebook user! > For those testing, another thing to test is whether the Mac App binaries build and work f