Dear Sage lovers,

We're releasing Sage 5.3.rc1.

Source archive:

http://boxen.math.washington.edu/home/release/sage-5.3.rc1/sage-5.3.r...

Upgrade path:

http://boxen.math.washington.edu/home/release/sage-5.3.rc1/sage-5.3.rc1/

The source and upgrade path can also be found on the mirror network
(you might need to wait a while before the mirrors are synchronized):

http://www.sagemath.org/download-latest.html

Please build, test, and report!  We'd love to hear about your
experiences with this release.

== Tickets ==

* We closed 108 tickets in this release. For details, see

  http://boxen.math.washington.edu/home/release/sage-5.3.rc1/tickets.html

Closed tickets:

#13405: Jeroen Demeyer, Keshav Kini: Remove old docs when upgrading
sagenb [Reviewed by John Palmieri]

Merged in sage-5.3.rc1:

#12324: Jeroen Demeyer: Fix upgrading of root repository [Reviewed by
John Palmieri]
#12486: Robert Bradshaw, Dan Drake: Make the Sage patchbot an optional
spkg [Reviewed by Volker Braun]
#13341: Jean-Pierre Flori, Leif Leonhardy: GAP's spkg-install fails on
recent Cygwin [Reviewed by Dmitrii Pasechnik]
#13392: Keshav Kini: Remove GNUTLS-related packages [Reviewed by John
Palmieri]
#13402: Dmitrii Pasechnik: a bug in matching() [Reviewed by David Coudert]
#13421: Jeroen Demeyer: polynomial_real_mpfr_dense.pyx: remove signal
handling around list(x) [Reviewed by Volker Braun]

On Sep 3, 2012, at 07:05 , Jeroen Demeyer wrote:

Built from scratch on Mac OS X, 10.6.8 (Dual 6-core Xeons), no problems.  Testing ('ptestlong') had one failure:
 sage -t  --long -force_lib devel/sage/sage/rings/polynomial/toy_buchberger.py

The failure occurred because, according to the printout, Singular crashed; it was automatically restarted, and testing continued, with, I think, the correct results, but the output was cluttered with unexpected printouts because of the crash, causing two apparent failures.

I reran the full test, and all tests passed.  I can provide crash log and syslog events, if needed.

On Mac OS X, 10.7.4 (Quad core Core i7), the build completed w/o problems.  Testing ('ptestlong') ran into the dreaded "timeout in interrupt.py" problem:

 sage -t  --long -force_lib devel/sage/sage/tests/interrupt.pyx

failed.  I noticed that while this "failure" was underway, the python process was chewing up 100% of one core.  Not sure what that means, but it might point to something.

Then I reran full tests twice.  In each case I got ~6 failures.  Since this seemed bizarre to me, I trashed $SAGE_ROOT and reinstalled and rebuilt.  This time, the build and the testing ran w/o any problems.

Something evil is lurking in the underbrush, at least according to the pricking in my thumbs...

Justin

--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's income
-----------
Question 43:
What if the hokey pokey
really *is* what it’s all about?
--