sage-4.7.rc2 released
Jeroen Demeyer
We're releasing Sage 4.7.rc2.
Source archive:
http://boxen.math.washington.edu/home/release/sage-4.7.rc2/sage-4.7.rc2.tar
Upgrade path:
http://boxen.math.washington.edu/home/release/sage-4.7.rc2/sage-4.7.rc2/
Please build, test, and report! We'd love to hear about your
experiences with this release.
== Known issues ==
* Some doctests fail on bsd.math (OS X 10.6 i386), when compiling in
64-bit mode due to SAGE64 verbosity. This is #10303.
* PolyBoRi fails to build on some old OS X systems because of a bug
in gcc.
== Tickets ==
* We closed 212 tickets in this release. For details, see
http://boxen.math.washington.edu/home/release/sage-4.7.rc2/tickets.html
Closed tickets:
#7702: Handle interrupts better in the notebook [Reviewed by Jeroen Demeyer]
#8566: Upate prereq to 0.8, removing 'm' option from 'tar' [Reviewed by
David Kirkby]
#9564: libsingular exponentiation can not be interrupted [Reviewed by
Nathann Cohen]
Merged in sage-4.7.rc2:
#11168: David Kirkby, Jeroen Demeyer: rubiks fails doctest with gcc
4.6.0 and -O2 optimisation. [Reviewed by John Palmieri, David Kirkby]
#11226: Jeroen Demeyer: Sympow spkg fails with gcc 4.6.0 [Reviewed by
David Kirkby]
#11227: Jeroen Demeyer: gcc-4.6.0 optimization bug with
cliquer-1.2.p7.spkg [Reviewed by Mariah Lenox]
#11278: Jeroen Demeyer: singular 3-1-1-4.p8 fails on Mac OS X 10.4
[Reviewed by Karl-Dieter Crisman]
#11280: Dmitrii Pasechnik: check XCode version on MacOSX, and bail out
if it is 4 [Reviewed by David Kirkby]
#11297: Dmitrii Pasechnik: altivec must be disabled for ECL on PPC OSX
10.5 [Reviewed by François Bissey]
kcrisman
> in gcc.
>
Singular upgrade did not fix this issue.
Volker Braun
tvn
Alexander Dreyer
> Singular upgrade did not fix this issue.
http://trac.sagemath.org/sage_trac/ticket/11331
which hopefully fixed that issue.
My best,
Alexander
Dan Drake
> We're releasing Sage 4.7.rc2.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.rc2/sage-4.7.rc2.tar
>
> Upgrade path:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.rc2/sage-4.7.rc2/
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
Built and passes (almost all) doctests on a 32-bit Ubuntu 11.04 virtual
machine. The only failure is in sandpile.py, which is known and due to
the kernel used on Debian/Ubuntu.
Also passed 10 "ptestlong" runs on 64-bit Ubuntu 10.04.
Dan
--
--- Dan Drake
----- http://mathsci.kaist.ac.kr/~drake
-------
Adam Webb
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
>
Adam
gsw
On 13 Mai, 13:36, Alexander Dreyer
<alexander.dre...@itwm.fraunhofer.de> wrote:
> > This is nowhttp://trac.sagemath.org/sage_trac/ticket/11331, since the
attempts to work around the internal compiler bug in the "Apple gcc
v4.0.1" from e.g. XCode 2.5), did build fine on both my MacIntel and
MacPPC systems (both have the latest OS X 10.4.11 and XCode 2.5). On
the MacIntel, "make testlong" had only one failure (the well known and
rather "accepted" maxima.py one --- seemingly due to the doctest for
the "_synchronize" function in lines 807ff; and maxima to be killed
too early, or the wrong instance of it, or whatever goes awry on OS X
10.4 here, maybe simply enlarging the 0.5s timeouts might help. But I
don't really care ...).
In short: I gave trac ticket #11331 a positive review (thank you
Alexander!).
Cheers,
Georg
Justin C. Walker
On May 12, 2011, at 05:49 , Jeroen Demeyer wrote:
> Dear Sage lovers,
>
> We're releasing Sage 4.7.rc2.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.rc2/sage-4.7.rc2.tar
Full build of rc2, Mac OS X, 10.6.7 (Dual 6-core Xeon). No problems in build, all tests passed.
Justin
--
Justin C. Walker
Curmudgeon at Large
Director
Institute for the Enhancement of the Director's Income
--
Build a man a fire and he'll be warm
for a night.
Set a man on fire and he'll be warm
for the rest of his life.
Dr. David Kirkby
> Dear Sage lovers,
>
> We're releasing Sage 4.7.rc2.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.rc2/sage-4.7.rc2.tar
>
> Upgrade path:
>
> http://boxen.math.washington.edu/home/release/sage-4.7.rc2/sage-4.7.rc2/
>
> Please build, test, and report! We'd love to hear about your
> experiences with this release.
All tests pass on OpenSolaris 06/2009. Both build and testing were done in
parallel - obviously the build first!!!
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Robert Bradshaw
/home/release/sage-4.7.rc2/sage-4.7.rc2-sage.math.washington.edu-x86_64-Linux.tar.gz
and am getting
robertwb@sage:/levi/scratch/robertwb/buildbot/sage-4.7.rc2$ ./sage -t
devel/sage-main/sage/interfaces/maxima.py
sage -t "devel/sage-main/sage/interfaces/maxima.py"
**********************************************************************
File "/levi/scratch/robertwb/buildbot/sage-4.7.rc2/devel/sage-main/sage/interfaces/maxima.py",
line 899:
sage: maxima._command_runner('describe', 'gcd')
Expected:
-- Function: gcd (<p_1>, <p_2>, <x_1>, ...)
...
Got:
Maxima encountered a Lisp error:
<BLANKLINE>
Filesystem error with pathname
#P"/levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-index.lisp".
Either
1) the file does not exist, or
2) we are not allow to access the file, or
3) the pathname points to a broken symbolic link.
<BLANKLINE>
Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.
<BLANKLINE>
**********************************************************************
File "/levi/scratch/robertwb/buildbot/sage-4.7.rc2/devel/sage-main/sage/interfaces/maxima.py",
line 927:
sage: maxima.help('gcd')
Expected:
-- Function: gcd (<p_1>, <p_2>, <x_1>, ...)
...
Got:
Maxima encountered a Lisp error:
<BLANKLINE>
Filesystem error with pathname
#P"/levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-index.lisp".
Either
1) the file does not exist, or
2) we are not allow to access the file, or
3) the pathname points to a broken symbolic link.
<BLANKLINE>
Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.
<BLANKLINE>
**********************************************************************
File "/levi/scratch/robertwb/buildbot/sage-4.7.rc2/devel/sage-main/sage/interfaces/maxima.py",
line 2419:
sage: m.gcd._sage_doc_()
Expected:
-- Function: gcd (<p_1>, <p_2>, <x_1>, ...)
...
Got:
Maxima encountered a Lisp error:
<BLANKLINE>
Filesystem error with pathname
#P"/levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-index.lisp".
Either
1) the file does not exist, or
2) we are not allow to access the file, or
3) the pathname points to a broken symbolic link.
<BLANKLINE>
Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.
<BLANKLINE>
**********************************************************************
File "/levi/scratch/robertwb/buildbot/sage-4.7.rc2/devel/sage-main/sage/interfaces/maxima.py",
line 2430:
sage: maxima.gcd._sage_doc_()
Expected:
-- Function: gcd (<p_1>, <p_2>, <x_1>, ...)
...
Got:
Maxima encountered a Lisp error:
<BLANKLINE>
Filesystem error with pathname
#P"/levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-index.lisp".
Either
1) the file does not exist, or
2) we are not allow to access the file, or
3) the pathname points to a broken symbolic link.
<BLANKLINE>
Automatically continuing.
To enable the Lisp debugger set *debugger-hook* to nil.
<BLANKLINE>
**********************************************************************
4 items had failures:
1 of 4 in __main__.example_13
1 of 4 in __main__.example_14
1 of 5 in __main__.example_75
1 of 4 in __main__.example_76
***Test Failed*** 4 failures.
For whitespace errors, see the file /home/robertwb/.sage//tmp/.doctest_maxima.py
[12.2 s]
----------------------------------------------------------------------
The following tests failed:
sage -t "devel/sage-main/sage/interfaces/maxima.py"
Total time for all tests: 12.2 seconds
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To post to this group, send email to sage-r...@googlegroups.com.
> To unsubscribe from this group, send email to sage-release...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.
>
>
Francois Bissey
> I unpacked
> /home/release/sage-4.7.rc2/sage-4.7.rc2-sage.math.washington.edu-x86_64-Li
> nux.tar.gz
> /home/release/sage-4.7.rc2/sage-4.7.rc2-sage.math.washington.edu-x86_64-Li
> nux.tar.gz and am getting
>
>
> robertwb@sage:/levi/scratch/robertwb/buildbot/sage-4.7.rc2$ ./sage -t
> devel/sage-main/sage/interfaces/maxima.py
> sage -t "devel/sage-main/sage/interfaces/maxima.py"
> **********************************************************************
> File
> "/levi/scratch/robertwb/buildbot/sage-4.7.rc2/devel/sage-main/sage/interfa
> ces/maxima.py", line 899:
> sage: maxima._command_runner('describe', 'gcd')
> Expected:
> -- Function: gcd (<p_1>, <p_2>, <x_1>, ...)
> ...
> Got:
> Maxima encountered a Lisp error:
> <BLANKLINE>
> Filesystem error with pathname
> #P"/levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-index.lis
> p". Either
Hi Robert,
What does:
ls -la /levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-
index.lisp
reports?
Francois
This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information.
Robert Bradshaw
That file doesn't exist.
- Robert
leif
leif@portland:~/Sage/sage-4.7.rc2$ ls -la local/info/
total 8
drwxr-xr-x 2 leif64 leif64 4096 May 16 02:00 .
drwxr-xr-x 12 leif64 leif64 4096 May 16 03:09 ..
leif@portland:~/Sage/sage-4.7.rc2$ ./sage -t
"devel/sage-main/sage/interfaces/maxima.py"
sage -t "devel/sage-main/sage/interfaces/maxima.py"
[31.4 s]
----------------------------------------------------------------------
All tests passed!
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML Email
Francois Bissey
> On Tue, May 17, 2011 at 3:59 PM, Francois Bissey
>
> <francoi...@canterbury.ac.nz> wrote:
> >> I unpacked
> >> /home/release/sage-4.7.rc2/sage-4.7.rc2-sage.math.washington.edu-x86_64-
> >> Li nux.tar.gz
> >> /home/release/sage-4.7.rc2/sage-4.7.rc2-sage.math.washington.edu-x86_64-
> >> Li nux.tar.gz and am getting
> >>
> >>
> >> robertwb@sage:/levi/scratch/robertwb/buildbot/sage-4.7.rc2$ ./sage -t
> >> devel/sage-main/sage/interfaces/maxima.py
> >> sage -t "devel/sage-main/sage/interfaces/maxima.py"
> >> **********************************************************************
> >> File
> >> "/levi/scratch/robertwb/buildbot/sage-4.7.rc2/devel/sage-main/sage/inter
> >> fa
> >>
> >> ces/maxima.py", line 899:
> >> sage: maxima._command_runner('describe', 'gcd')
> >>
> >> Expected:
> >> -- Function: gcd (<p_1>, <p_2>, <x_1>, ...)
> >> ...
> >>
> >> Got:
> >> Maxima encountered a Lisp error:
> >> <BLANKLINE>
> >> Filesystem error with pathname
> >>
> >> #P"/levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-index.
> >> lis p". Either
> >
> > Hi Robert,
> >
> > What does:
> > ls -la /levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-
> > index.lisp
> > reports?
>
> That file doesn't exist.
>
Right, so it probably wasn't shipped with the tarball for some reason, does
the folder local/info even exists?
Francois
Francois Bissey
> Robert Bradshaw schrieb:
> > On Tue, May 17, 2011 at 3:59 PM, Francois Bissey
> >
> > <francoi...@canterbury.ac.nz> wrote:
> >>> I unpacked
> >>> /home/release/sage-4.7.rc2/sage-4.7.rc2-sage.math.washington.edu-x86_64
> >>> -Li nux.tar.gz
> >>> /home/release/sage-4.7.rc2/sage-4.7.rc2-sage.math.washington.edu-x86_64
> >>> -Li nux.tar.gz and am getting
> >>>
> >>>
> >>> robertwb@sage:/levi/scratch/robertwb/buildbot/sage-4.7.rc2$ ./sage -t
> >>> devel/sage-main/sage/interfaces/maxima.py
> >>> sage -t "devel/sage-main/sage/interfaces/maxima.py"
> >>> **********************************************************************
> >>> File
> >>> "/levi/scratch/robertwb/buildbot/sage-4.7.rc2/devel/sage-main/sage/inte
> >>> rfa
> >>>
> >>> ces/maxima.py", line 899:
> >>> sage: maxima._command_runner('describe', 'gcd')
> >>>
> >>> Expected:
> >>> -- Function: gcd (<p_1>, <p_2>, <x_1>, ...)
> >>> ...
> >>>
> >>> Got:
> >>> Maxima encountered a Lisp error:
> >>> <BLANKLINE>
> >>>
> >>> Filesystem error with pathname
> >>>
> >>> #P"/levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-index
> >>> .lis p". Either
> >>
> >> Hi Robert,
> >>
> >> What does:
> >> ls -la /levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/maxima-
> >> index.lisp
> >> reports?
> >
> > That file doesn't exist.
>
> leif@portland:~/Sage/sage-4.7.rc2$ ls -la local/info/
> total 8
> drwxr-xr-x 2 leif64 leif64 4096 May 16 02:00 .
> drwxr-xr-x 12 leif64 leif64 4096 May 16 03:09 ..
Indeed there is nothing in that folder in a standard install.
Robert Bradshaw
The folder exists, it's just empty.
robertwb@sage:/levi/scratch/robertwb/buildbot/sage-4.7.rc2$ ls -la
/levi/scratch/robertwb/buildbot/sage-4.7.rc2/local/info/
total 8
drwxr-xr-x 2 robertwb robertwb 4096 2011-05-11 12:25 .
drwxr-xr-x 12 robertwb robertwb 4096 2011-05-11 15:09 ..
- Robert
John H Palmieri
I've seen this before, but I don't know what causes it. That file is supposed to be installed (and probably is installed) in local/share/info/ rather than local/info/. Is an old version of maxima somehow being used, and it's looking in the wrong place? (Perhaps this file used to be installed in local/info/, in a previous version of maxima?)
--
John
Mariah
a blocker for the 4.7 release.
Mariah
Robert Bradshaw
FWIW, I built from source, and the problem goes away. Feel free to use
/levi/scratch/robertwb/buildbot/sage-4.7.rc to try and diagnose this
issue (or unpack the sage-math binary tarball yourself and see if you
can reproduce it).
- Robert