[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread Eric Gourgoulhon
Hi, I've tried sage-6.10.rc1-Ubuntu_14.04-x86_64.tar.bz2 on a x86-64 laptop with Ubuntu 14.04. I've noticed some issues: 1/ The patching at first run took ages (12 min on Intel Core i5-2410 M with 4 GB RAM) (maybe one should warn the user about this, since he might expect a binary to run

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread kcrisman
Can users still contribute binaries under this new packaging? Especially for other Linuces and older Mac OS that would be something we want to encourage. Here is a final test for the binaries, using the new binary packaging. That > is, now binaries are patched automatically on first run, no m

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread Volker Braun
Yes, use https://github.com/sagemath/binary-pkg On Tuesday, December 15, 2015 at 3:08:13 PM UTC+1, kcrisman wrote: > > Can users still contribute binaries under this new packaging? Especially > for other Linuces and older Mac OS that would be something we want to > encourage. > > -- You recei

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread kcrisman
> Yes, use https://github.com/sagemath/binary-pkg > > On Tuesday, December 15, 2015 at 3:08:13 PM UTC+1, kcrisman wrote: >> >> Can users still contribute binaries under this new packaging? Especially >> for other Linuces and older Mac OS that would be something we want to >> encourage. >> >> O

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread Volker Braun
Yes. Patches to the documentation are welcome ;-) On Tuesday, December 15, 2015 at 8:53:23 PM UTC+1, kcrisman wrote: > > Yes, use https://github.com/sagemath/binary-pkg >> > Okay. Should we use this rather than `sage -bdist`? > -- You received this message because you are subscribed to the

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread Eric Gourgoulhon
Hi, Le mardi 15 décembre 2015 10:41:49 UTC+1, Eric Gourgoulhon a écrit : > > > 2/ The Jupyter notebook opened with ./sage -n jupyter starts with an > error message > > Failed to retrieve MathJax from '/nbextensions/mathjax/MathJax.js' > > Math/LaTeX rendering will be disabled. > The source of t

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread Eric Gourgoulhon
The cause of the 3D graphics issue is similar: in the binary version, the symlink SAGE_ROOT/local/share/jupyter/nbextensions/jsmol points wrongly to a remnant of the buildbot: /mnt/highperf/buildbot/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/share/jsmol w

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread kcrisman
On Tuesday, December 15, 2015 at 3:20:17 PM UTC-5, Volker Braun wrote: > > Yes. Patches to the documentation are welcome ;-) > > > In this case, nice try - I haven't even used binary-pkg yet! If and when I may try. > On Tuesday, December 15, 2015 at 8:53:23 PM UTC+1, kcrisman wrote: >> >>

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread Samuel Lelievre
Mon, 14 Dec 2015 15:43:54 -0800 (PST), Volker Braun: > Here is a final test for the binaries, using the new > binary packaging. That is, now binaries are patched > automatically on first run, no more relocation after that. Thank you for that. On a MacBook Air running OS X 10.10.5, I downloaded

[sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-16 Thread Volker Braun
The mathjax issue is clear, I'll fix it in the next version (change symlinks to relative) On Wednesday, December 16, 2015 at 8:36:29 AM UTC+1, Samuel Lelievre wrote: > > $ ./sage -n jupyter > From there, I couldn't figure out how to navigate > to my home folder to create a jupyter notebook. >

Re: [sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-15 Thread Henri Girard
I have same problem with 16.04 using binary, but I compiled it successfully with not problem. Le 15/12/2015 10:41, Eric Gourgoulhon a écrit : Hi, I've tried sage-6.10.rc1-Ubuntu_14.04-x86_64.tar.bz2 on a x86-64 laptop with Ubuntu 14.04. I've noticed some issues: 1/ The patching at first run

Re: [sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-16 Thread Samuel Lelièvre
2015-12-16 00:26:48 -0800 (PST) Volker Braun: > The mathjax issue is clear, I'll fix it in the next version (change symlinks > to relative) Thank you. > On Wednesday, December 16, 2015 at 8:36:29 AM UTC+1, Samuel Lelievre wrote: >> >> $ ./sage -n jupyter >> From there, I couldn't figure out

Re: [sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-17 Thread kcrisman
> > Another thing I wanted to mention is the following. > > When I started Sage for the first time from the SageMath 6.10.rc1 > binaries for OS X, it started ouputting a bunch of lines (roughly > 2300 of them) starting with "patching", before finally giving the > Sage welcome header and the Sa

Re: [sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-17 Thread Eric Gourgoulhon
Hi, Le jeudi 17 décembre 2015 18:10:43 UTC+1, kcrisman a écrit : > > > I'd +1 that; I haven't tested these binaries yet since I don't have El > Capitan but I agree that is not very user-friendly. > Note that this issue is not specific to OS X: the long patching takes place with Linux as well (

Re: [sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-17 Thread Volker Braun
The patching can be done faster, but it has to work first ;-) Also I'm pretty sure that it even now is much faster than the unpacking of the tarball. In any case I've added a message. On Thursday, December 17, 2015 at 6:51:03 PM UTC+1, Eric Gourgoulhon wrote: > > Note that this issue is no

Re: [sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-17 Thread Eric Gourgoulhon
Le jeudi 17 décembre 2015 20:30:52 UTC+1, Volker Braun a écrit : > > The patching can be done faster, but it has to work first ;-) Also I'm > pretty sure that it even now is much faster than the unpacking of the > tarball. In any case I've added a message. > > > Thanks. I think that with a m

Re: [sage-release] Re: Sage-6.10.rc1 binaries test

2015-12-17 Thread Dima Pasechnik
On Thursday, 17 December 2015 19:30:51 UTC, Volker Braun wrote: > > The patching can be done faster, but it has to work first ;-) Also I'm > pretty sure that it even now is much faster than the unpacking of the > tarball. In any case I've added a message. > unless you've already sped it up, i