Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Henri Girard
Well, the tree/develop gives sage-develop in zip but in git clone it's sage.git, I am compiling it and will see if it's sage 6.9 maybe I used to make a mistake ? But last time I did it I had sage6.8 Le 06/10/2015 05:23, Dima Pasechnik a écrit : On Monday, 5 October 2015 18:15:23 UTC-7, HG w

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Dima Pasechnik
On Monday, 5 October 2015 18:15:23 UTC-7, HG wrote: > > Hi, > I build sage 6.9.rc2 on ubuntu 15.04 and got it working but then latex was > n't working in ipython notebook command ouput was between frame like a > table. > By the way a question : Sage 6.9 rc2 can't be otbain with git clone ? > I

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Henri Girard
Hi, I build sage 6.9.rc2 on ubuntu 15.04 and got it working but then latex was n't working in ipython notebook command ouput was between frame like a table. By the way a question : Sage 6.9 rc2 can't be otbain with git clone ? I could get only the tar download. Otherwise with git it have versio

[sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Volker Braun
Well why can't you import notebook then? On Monday, October 5, 2015 at 10:56:54 PM UTC+2, Eric Gourgoulhon wrote: > > > > Le lundi 5 octobre 2015 21:45:22 UTC+2, Volker Braun a écrit : >> >> You need to install Sage (i.e. run "make") >> >> > I did; it recompiled many things and took a while. > B

[sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Eric Gourgoulhon
Le lundi 5 octobre 2015 21:45:22 UTC+2, Volker Braun a écrit : > > You need to install Sage (i.e. run "make") > > I did; it recompiled many things and took a while. But the problem is still there: ./sage -n jupyter results in the same error message. -- You received this message because you ar

[sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Volker Braun
You need to install Sage (i.e. run "make") On Monday, October 5, 2015 at 9:43:46 PM UTC+2, Eric Gourgoulhon wrote: > > PS: note that with sage 6.8 (where ./sage -n ipython works), I have the > same error message: > $ ./sage -python > Python 2.7.9 (default, Aug 1 2015, 11:59:13) > [GCC 4.8.2] on

[sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Eric Gourgoulhon
PS: note that with sage 6.8 (where ./sage -n ipython works), I have the same error message: $ ./sage -python Python 2.7.9 (default, Aug 1 2015, 11:59:13) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from notebook.notebookapp import NotebookApp

[sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Eric Gourgoulhon
Le lundi 5 octobre 2015 21:17:43 UTC+2, Volker Braun a écrit : > > whats the output of > > > $ sage -python > >>> from notebook.notebookapp import NotebookApp > > > Sorry for the previous truncated message; the output is $ ./sage -python Python 2.7.9 (default, Oct 5 2015, 20:41:58) [GCC 4.8.2]

[sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Eric Gourgoulhon
Le lundi 5 octobre 2015 21:17:43 UTC+2, Volker Braun a écrit : > > whats the output of > > > $ sage -python > >>> from notebook.notebookapp import NotebookApp > > It is Python 2.7.9 (default, Oct 5 2015, 20:41:58) [GCC 4.8.2] on linux2 Type "help", "copyright", "credits" or "license" for mor

[sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Volker Braun
whats the output of $ sage -python >>> from notebook.notebookapp import NotebookApp On Monday, October 5, 2015 at 9:07:18 PM UTC+2, Eric Gourgoulhon wrote: > > Hi, > > On Ubuntu 14.04 64bits, the build was OK but when I try > ./sage -n jupyter > I get > > The IPython notebook requires ssl, even

[sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Eric Gourgoulhon
Hi, On Ubuntu 14.04 64bits, the build was OK but when I try ./sage -n jupyter I get The IPython notebook requires ssl, even if you do not use https. Install the openssl development packages in your system and then rebuild Python (sage -f python2). Now the openssl development packages (libssl-dev

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread kcrisman
By the way, all normal tests passed on the build from scratch once I got the proxy issue sorted out, which is nice. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread kcrisman
> Right. You bug report actually shows 3 independent bugs: > > Haha! -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.co

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Jeroen Demeyer
Right. You bug report actually shows 3 independent bugs: * GCC shouldn't be downloaded in the first place * The failed download of the mirror_list doesn't give an error message * The blank line without failed packages The first one is fixed at #19347. The third one was fixed at #18731, but the f

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread kcrisman
> > > gcc should be contained in the source tarball. This is fallout from the > build system changes. Fix needs review at > > What about the blank line with no failed packages? Clearly a package failed. So somehow whatever mechanism causes the package to be listed (I used to know what that i

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Jeroen Demeyer
On 2015-10-05 09:46, kcrisman wrote: That's not good either. Also, just setting the env var to blank didn't seem to negate it, currently trying with unsetting it. That's probably my ignorance of bash, though. Aagh, it's *still* trying to download it, even though the env var SAGE

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread kcrisman
Also, I still get The following package(s) may have failed to build (not necessarily during this run of 'make all'): -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an emai

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread kcrisman
>From a fresh untarred ball on Mac Lion: Found local metadata for gcc-4.9.2.p1 Attempting to download package gcc-4.9.2.tar.bz2 from mirrors Downloading the Sage mirror list CRITICAL [mirror_list|_refresh:164]: Downloading the mirror list failed Traceback (most recent call last): File "/Users/..

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread kcrisman
> I compiled it on ubuntu 15.04 successfully, sage --notebook=ipython > worked, but I had no latex displaying, raw one. > > Interesting. I was in the meantime able to upgrade my previous installation and sagenb seems to work fine. Still interested in that ccache thing - I had to reduce the l

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread Henri Girard
I compiled it on ubuntu 15.04 successfully, sage --notebook=ipython worked, but I had no latex displaying, raw one. Le 05/10/2015 09:46, kcrisman a écrit : That's not good either. Also, just setting the env var to blank didn't seem to negate it, currently trying with unsetting it.

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread kcrisman
> > > That's not good either. Also, just setting the env var to blank didn't > seem to negate it, currently trying with unsetting it. That's probably my > ignorance of bash, though. > Aagh, it's *still* trying to download it, even though the env var SAGE_INSTALL_CCACHE is now not even showin

Re: [sage-release] Re: Sage 6.9.rc2 released

2015-10-05 Thread kcrisman
With SAGE_INSTALL_CCACHE=yes I get (from tarball) Found local metadata for ccache-3.2.2 Attempting to download package ccache-3.2.2.tar.bz2 from mirrors Downloading the Sage mirror list CRITICAL [mirror_list|_refresh:164]: Downloading the mirror list failed Also, this causes the entire build to f