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
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:
>>
>>
this was a result of
b2094a8a (Jeroen Demeyer 2015-11-18 15:53:34 +0100 1402)
which did change
description = G._gap_().StructureDescription().__str__()
to
description = str(G._gap_().StructureDescription())
but these calls are not 100% the same:
sage: groups.matrix.GL(4,2
Hi,
On Tue, Dec 15, 2015 at 12:35:12PM -0800, Eric Gourgoulhon wrote:
[...]
> The source of the problem may be a wrong symlink in the binary version:
>
> cd SageMath
> ls -l local/share/jupyter/nbextensions/mathjax
> lrwxrwxrwx 1 eric eric 120 déc. 14 03:28
> local/share/jupyter/nbextensions/m
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
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
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
> 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
Two optional tests fails (perhaps this is already known):
$ ./sage --version
SageMath Version 6.10.rc1, Release Date: 2015-12-13
sage -t src/sage/groups/generic.py
**
File "src/sage/groups/generic.py", line 1388, in
sage.groups
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
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
On 2015-12-13 14:46, Volker Braun wrote:
> 0a59435 Updated Sage version to 6.10.rc1
All tests passed with "make ptestlong" and cloned freshly on Linux Mint
17.2.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and
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
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
14 matches
Mail list logo