Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-20 Thread kcrisman
Nicolas, can you have the person (if there is still the opportunity) try out using the menu icon to start a Jupyter notebook? I'm having trouble even doing that. On Tuesday, April 18, 2017 at 11:19:59 AM UTC-4, Nicolas M. Thiéry wrote: > >Hi Karl! > > I used the occasion of SD86 to try

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-19 Thread kcrisman
On Tuesday, April 18, 2017 at 11:19:59 AM UTC-4, Nicolas M. Thiéry wrote: > >Hi Karl! > > I used the occasion of SD86 to try out: > > sage-8.0.beta0-OSX_10.11.6-x86_64.app.dmg > > on a participant's mac. I dragged and dropped the app from the dmg > into Applications. I get an

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-18 Thread Nicolas M. Thiery
Hi Karl! I used the occasion of SD86 to try out: sage-8.0.beta0-OSX_10.11.6-x86_64.app.dmg on a participant's mac. I dragged and dropped the app from the dmg into Applications. I get an icon in the tray. However clicking the icon just starts the legacy notebook without reference

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-08 Thread kcrisman
On Friday, April 7, 2017 at 4:49:00 PM UTC-4, Matthias Koeppe wrote: > > On Friday, April 7, 2017 at 9:04:45 AM UTC-7, kcrisman wrote: >> >> I have some OS X beta0 binaries I hope some people could test out >> > > For testing the binaries, you could try > https://github.com/mkoeppe/sage_binary_t

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-07 Thread Matthias Koeppe
On Friday, April 7, 2017 at 9:04:45 AM UTC-7, kcrisman wrote: > > I have some OS X beta0 binaries I hope some people could test out > For testing the binaries, you could try https://github.com/mkoeppe/sage_binary_tester -- You received this message because you are subscribed to the Google Gr

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-07 Thread kcrisman
I have some OS X beta0 binaries I hope some people could test out - is there a good place to upload them? (I could send Harald a link if need be; unfortunately it isn't a place that can handle great bandwidth of downloads.) Thanks, - kcrisman -- You received this message because you are subsc

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-04 Thread Jeroen Demeyer
On 2017-04-04 18:41, Eric Gourgoulhon wrote: What could explain the difference? That's a very good question indeed... I'm afraid we need some web expert here. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-04 Thread Eric Gourgoulhon
Hi Jeroen, Le samedi 1 avril 2017 15:29:04 UTC+2, Jeroen Demeyer a écrit : > > I would like in particular feedback on the "Take me to the new > Sage/Jupyter notebook" button in ExportSageNB. > > When clicking that button, do you get > > (A) a directory listing of the current directory > (B) a

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-04-01 Thread Jeroen Demeyer
I would like in particular feedback on the "Take me to the new Sage/Jupyter notebook" button in ExportSageNB. When clicking that button, do you get (A) a directory listing of the current directory (B) a login screen where you are asked for a token You should get (A) but under certain unknown c

[sage-release] Re: Sage 8.0.beta0 released

2017-04-01 Thread Harald Schilly
On Friday, March 31, 2017 at 3:44:02 AM UTC+2, kcrisman wrote: > > Remember, we want LOTS OF TESTING of this one - including the Mac > interface. Any possible bugs in the move to the ExportSageNB interface > must be exposed. > I haven't checked it with ExportSageNB, but it's probably worth a

[sage-release] Re: Sage 8.0.beta0 released

2017-03-31 Thread Eric Gourgoulhon
On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + pull develop, parallel (-j8) build OK and make ptestlong successful. Eric. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop recei

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-03-31 Thread Henri Girard
Yes from a fresh sage-8 no problem compilation did it Henri Le 31/03/2017 à 08:52, Henri Girard a écrit : yes sorry but my first bad habit was to delete it ! I am doing it on a fresh sage-8 thanks Henri Le 31/03/2017 à 08:46, Vincent Delecroix a écrit : Henri, can you post the log SAGE_RO

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-03-30 Thread Henri Girard
yes sorry but my first bad habit was to delete it ! I am doing it on a fresh sage-8 thanks Henri Le 31/03/2017 à 08:46, Vincent Delecroix a écrit : Henri, can you post the log SAGE_ROOT/logs/pkgs/ singular-4.1.0p1.log? How should we guess why your build failed without any information? It m

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-03-30 Thread Vincent Delecroix
Henri, can you post the log SAGE_ROOT/logs/pkgs/ singular-4.1.0p1.log? How should we guess why your build failed without any information? It might be due to 96400c9 Trac #22606: singular build option --disable-polymake Vincent On 31/03/2017 08:19, Henri Girard wrote: Hi, ubuntu 16.04 , make

Re: [sage-release] Re: Sage 8.0.beta0 released

2017-03-30 Thread Henri Girard
Hi, ubuntu 16.04 , make doc-clean, make -j9 build after 7.6 any, I am compiling it on a fresh sage 8 regards Henri I got this error : make[2] : on quitte le répertoire « /home/pi/sage/build/make » Makefile:922 : la recette pour la cible « all » a échouée make[1]: *** [all] Erreur 2 make[1]

[sage-release] Re: Sage 8.0.beta0 released

2017-03-30 Thread kcrisman
Remember, we want LOTS OF TESTING of this one - including the Mac interface. Any possible bugs in the move to the ExportSageNB interface must be exposed. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop