sage-5.0.rc1 released

[Jeroen Demeyer]

Dear Sage lovers,

We're releasing Sage 5.0.rc1.

Source archive:

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

Upgrade path:

http://boxen.math.washington.edu/home/release/sage-5.0.rc1/sage-5.0.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 506 tickets in this release. For details, see

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

Closed tickets:

#10810: singular-3-1-1-4.p3 doesn't build on ARM [Reviewed by Julien Puydt]
#11881: Metaticket: build Sage on OS X 10.7 Lion [Reviewed by John Palmieri]
#12459: Interrupt test failures on OS X 10.7 [Reviewed by Jeroen Demeyer]

Merged in sage-5.0.rc1:

#12898: Jeroen Demeyer: Update top-level README.txt [Reviewed by William
Stein, Karl-Dieter Crisman, David Kirkby, Martin Raum]
#12899: Jeroen Demeyer: Update the "Install from Source Code" docs for
sage-5.0 [Reviewed by Nathann Cohen]
#12909: Robert Bradshaw, Jeroen Demeyer: gdmodule: don't use /sw and
/usr/local paths [Reviewed by Volker Braun]

[Keshav Kini]

MPIR still fails to build on virtualbox / sandy bridge (see rc0 thread for details). I'll make a ticket for this since I guess nobody else did.

-Keshav

----
Join us in #sagemath on irc.freenode.net !

[Keshav Kini]

Or we could just treat this as an unsupported architecture or something. A workaround seems to be to run `CFLAGS="-O2 -march=native" make` instead of just `make` when building Sage. What do you think?

-Keshav

----
Join us in #sagemath on irc.freenode.net !

[Florent Hivert]

Dear Jeroen,

> We're releasing Sage 5.0.rc1.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-5.0.rc1/sage-5.0.rc1.tar
>

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

I'm on OpenSuSE 12.1 x84_64 on a Core I7

Build without any problem. However make ptestlong reported

sage -t --long -force_lib devel/sage/sage/rings/arith.py # 1 doctests failed

**********************************************************************
File "/home/data/Sage-Install/sage-5.0.rc1/devel/sage-main/sage/rings/arith.py", line 296:
sage: union([len(union(x))==1 for x in vals]) # long time (depends on previous
line)
Expected:
[True]
Got:
[False, True]
**********************************************************************
1 items had failures:
1 of 18 in __main__.example_2
***Test Failed*** 1 failures.
For whitespace errors, see the file /home/florent/.sage/tmp/popcorn.rouba.net-13330/arith_30331.py
[227.7 s]

I'm not able to reproduce the failure by relaunching the single test. There
are however large variation of the time spent in the test on an otherwise idle
machine:

popcorn-*age/sage-5.0.rc1 $ ./sage -t --long -force_lib devel/sage/sage/rings/arith.py
sage -t --long -force_lib "devel/sage/sage/rings/arith.py"
Total time for all tests: 101.8 seconds
Total time for all tests: 60.7 seconds
Total time for all tests: 83.7 seconds
Total time for all tests: 64.5 seconds
Total time for all tests: 72.0 seconds
Total time for all tests: 75.5 seconds
Total time for all tests: 72.6 seconds

I'm not sure if its relevant.

Cheers,

Florent

[Anthony David]

On Fri, May 11, 2012 at 1:52 AM, Jeroen Demeyer <jdem...@cage.ugent.be> wrote:

Dear Sage lovers,

We're releasing Sage 5.0.rc1.

Source archive:

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

Upgrade path:

http://boxen.math.washington.edu/home/release/sage-5.0.rc1/sage-5.0.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.

Successful parallel build (SAGE_CHECK=yes)

LSB Version:    :core-4.0-amd64:core-4.0-noarch

Distributor ID: Fedora

Description:    Fedora release 16 (Verne)

Release:        16

Codename:       Verne

 

== Tickets ==

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

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

Closed tickets:

#10810: singular-3-1-1-4.p3 doesn't build on ARM [Reviewed by Julien Puydt]
#11881: Metaticket: build Sage on OS X 10.7 Lion [Reviewed by John Palmieri]
#12459: Interrupt test failures on OS X 10.7 [Reviewed by Jeroen Demeyer]

Merged in sage-5.0.rc1:

#12898: Jeroen Demeyer: Update top-level README.txt [Reviewed by William
Stein, Karl-Dieter Crisman, David Kirkby, Martin Raum]
#12899: Jeroen Demeyer: Update the "Install from Source Code" docs for
sage-5.0 [Reviewed by Nathann Cohen]
#12909: Robert Bradshaw, Jeroen Demeyer: gdmodule: don't use /sw and
/usr/local paths [Reviewed by Volker Braun]

--
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.

[Jeroen Demeyer]

On 2012-05-10 21:49, Keshav Kini wrote:
> Or we could just treat this as an unsupported architecture or something.
> A workaround seems to be to run `CFLAGS="-O2 -march=native" make`
> instead of just `make` when building Sage. What do you think?

Better would be to restrict the architecture to something that
VirtualBox supports, like -march=core2 or something.

[Harald Schilly]

hi, just as with the rc0, this one fails on Ubuntu 10.04.4 LTS, 32bit.

sage -t --long -force_lib "devel/sage/sage/tests/cmdline.py"

**********************************************************************

File "/scratch/scratch/schilly/sage/sage-5.0.rc1/devel/sage/sage/tests/cmdline.py", line 270:

    sage: ret

Expected:

    0

Got:

    128

**********************************************************************

File "/scratch/scratch/schilly/sage/sage-5.0.rc1/devel/sage/sage/tests/cmdline.py", line 272:

    sage: out.find("All tests passed!") >= 0

Expected:

    True

Got:

    False

**********************************************************************

File "/scratch/scratch/schilly/sage/sage-5.0.rc1/devel/sage/sage/tests/cmdline.py", line 275:

    sage: ret

Expected:

    0

Got:

    128

**********************************************************************

File "/scratch/scratch/schilly/sage/sage-5.0.rc1/devel/sage/sage/tests/cmdline.py", line 277:

    sage: out.find("All tests passed!") >= 0

Expected:

    True

Got:

    False

**********************************************************************

1 items had failures:

   4 of 186 in __main__.example_1

***Test Failed*** 4 failures.

For whitespace errors, see the file /users/schilly/.sage//tmp/cmdline_16243.py

         [48.9 s]

[Franco Saliola]

> We're releasing Sage 5.0.rc1.

...

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

Same doctest errors with 'make ptest' as for beta14 and rc0:

$ uname -a
Darwin lacim-macpro-02 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7
16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64

For details:
https://groups.google.com/d/msg/sage-release/_wQyG4AHkB0/18l-HeIUGp0J

If you need more information, just tell me what I need to provide.

Franco

--

[Marshall Hampton]

I haven't had any problems building any of the sage-5.0 betas, but I
am now getting an error building R on my i7-3930k linux machine:

configure: error: --with-readline=yes (default) and headers/libs are
not available
Error configuring R.

As recent as the sage-5.0-beta15 this was building fine and passing
all tests.

I am happy to provide any additional information that might be
helpful.

-Marshall

On May 10, 10:52 am, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> Dear Sage lovers,
>
> We're releasing Sage 5.0.rc1.
>
> Source archive:
>

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

[Jeroen Demeyer]

On 2012-05-11 16:11, Marshall Hampton wrote:
> I haven't had any problems building any of the sage-5.0 betas, but I
> am now getting an error building R on my i7-3930k linux machine:
>
> configure: error: --with-readline=yes (default) and headers/libs are
> not available
> Error configuring R.
>
> As recent as the sage-5.0-beta15 this was building fine and passing
> all tests.

Since beta15 doesn't exist, I assume you mean beta14?

You could provide the build log for readline and R (in spkg/logs) and
the config.log of R (in spkg/build/r-*/src).

[leif]

Marshall Hampton wrote:
> I haven't had any problems building any of the sage-5.0 betas, but I
> am now getting an error building R on my i7-3930k linux machine:
>
> configure: error: --with-readline=yes (default) and headers/libs are
> not available
> Error configuring R.
>
> As recent as the sage-5.0-beta15 this was building fine and passing
> all tests.
>
> I am happy to provide any additional information that might be
> helpful.

What Linux distro is that, and did you make any changes to it recently,
i.e., before building rc1?

(I assume your successful 5.0.beta* builds were on the same machine.)


-leif

--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail

[Marshall Hampton]

I just realized that I was using the sage-5.0 from
http://sage.math.washington.edu/home/release, which I had thought was
the same as sage-5.0-rc1, but maybe not. Sorry about the noise, I'll
try again with the rc1.

(I did download a beta15 at one point from /home/release; I guess its
not there anymore.)

-Marshall

[Anthony David]

On Fri, May 11, 2012 at 1:52 AM, Jeroen Demeyer <jdem...@cage.ugent.be> wrote:

Dear Sage lovers,

We're releasing Sage 5.0.rc1.

Source archive:

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

Upgrade path:

http://boxen.math.washington.edu/home/release/sage-5.0.rc1/sage-5.0.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.

Ubuntu 11.10 (GNU/Linux 3.0.0-17-generic-pae i686)

Built successfully (as with rc0)

./sage -testall -long as successful as rc0. Only failures were timeouts.

        sage -t  -long -force_lib "devel/sage/sage/misc/randstate.pyx" # Time out

        sage -t  -long -force_lib "devel/sage/sage/interacts/debugger.py" # Time out

        sage -t  -long -force_lib "devel/sage/sage/interfaces/expect.py" # Time out

        sage -t  -long -force_lib "devel/sage/sage/interfaces/sage0.py" # Time out

        sage -t  -long -force_lib "devel/sage/sage/interfaces/psage.py" # Time out

        sage -t  -long -force_lib "devel/sage/sage/tests/startup.py" # Time out

Regards

Anthony

 

== Tickets ==

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

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

Closed tickets:

#10810: singular-3-1-1-4.p3 doesn't build on ARM [Reviewed by Julien Puydt]
#11881: Metaticket: build Sage on OS X 10.7 Lion [Reviewed by John Palmieri]
#12459: Interrupt test failures on OS X 10.7 [Reviewed by Jeroen Demeyer]

Merged in sage-5.0.rc1:

#12898: Jeroen Demeyer: Update top-level README.txt [Reviewed by William
Stein, Karl-Dieter Crisman, David Kirkby, Martin Raum]
#12899: Jeroen Demeyer: Update the "Install from Source Code" docs for
sage-5.0 [Reviewed by Nathann Cohen]
#12909: Robert Bradshaw, Jeroen Demeyer: gdmodule: don't use /sw and
/usr/local paths [Reviewed by Volker Braun]

[Justin C. Walker]

On May 10, 2012, at 08:52 , Jeroen Demeyer wrote:

> Dear Sage lovers,
>
> We're releasing Sage 5.0.rc1.
>
> Source archive:
>
> http://boxen.math.washington.edu/home/release/sage-5.0.rc1/sage-5.0.rc1.tar

Built on two platforms:

Mac OS X, 10.6.8 (Dual 6-core Xeons): built w/o problems, all tests passed!

Mac OS X, 10.7.1 (4 core Core i7): built w/o problems, all tests passed!

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
I want to die, peacefully in my sleep, like my grandfather;
not screaming in terror, like his passengers.

[ThanhVu Nguyen]

Make ptestlong fails on Debian Squeeze.  Let me know if you need more details.


...

The temporary doctesting directory
   /home/tnguyen/.sage/tmp/GiaoChi-2592
was not removed: it is not empty, presumably because doctests
failed or doctesting was interrupted.

----------------------------------------------------------------------

The following tests failed:

        sage -t  --long -force_lib devel/sagenb-main/sagenb/misc/sageinspect.py # 8 doctests failed
        sage -t  --long -force_lib devel/sagenb-main/sagenb/misc/sphinxify.py # 5 doctests failed
        sage -t  --long -force_lib devel/sagenb-main/sagenb/misc/support.py # 1 doctests failed
        sage -t  --long -force_lib devel/sage/sage/interfaces/tachyon.py # 1 doctests failed
        sage -t  --long -force_lib devel/sage/sage/misc/sageinspect.py # 10 doctests failed
        sage -t  --long -force_lib devel/sage/sage/misc/cachefunc.pyx # 4 doctests failed
        sage -t  --long -force_lib devel/sage/sage/misc/sagedoc.py # 14 doctests failed
        sage -t  --long -force_lib devel/sage/sage/parallel/decorate.py # 1 doctests failed
        sage -t  --long -force_lib devel/sage/sage/structure/dynamic_class.py # 1 doctests failed
        sage -t  --long -force_lib devel/sage/sage/structure/element.pyx # 1 doctests failed
----------------------------------------------------------------------
Total time for all tests: 2070.6 seconds
make: *** [ptestlong] Error 128
GiaoChi Sun May 13:00:56:52 (5385) ~/Src/Devel/SAGE/sage-5.0.rc1

[ThanhVu Nguyen]

I think many of these errors are due to

from common.conf import *
ImportError: No module named conf

[Dr. David Kirkby]

On 05/13/12 08:24 AM, ThanhVu Nguyen wrote:
> I think many of these errors are due to
>
> from common.conf import *
> ImportError: No module named conf

If the build of python has failed to build a module we need, perhaps we should
test for that module, like we do for some other modules.

Perhaps I have mis-understood the problem - if so send my comments to /dev/null.

dave

[John H Palmieri]

On Sunday, May 13, 2012 12:24:07 AM UTC-7, ThanhVu Nguyen wrote:

I think many of these errors are due to

from common.conf import *
ImportError: No module named conf

This looks like an issue with the documentation. Is there a file

  SAGE_ROOT/devel/sage/doc/common/conf.py
 
or is it missing? Did the documentation build? What are the contents of SAGE_ROOT/devel/sage/doc/output/ ?

--
John

[ThanhVu Nguyen]

First, the variable $SAGE_ROOT is not set  in my computer (would this cause the problem ?).  The variable $SAGE is set to my Sage 4.8. 

The file ~/Src/Devel/SAGE/sage-5.0.rc1/devel/sage/doc/common/conf.py exists.  The output of ~/Src/Devel/SAGE/sage-5.0.rc1/devel/sage/doc/output is   doctrees/ and html/


Also these exact problems happen on my Mac OS 10.6.4

----------------------------------------------------------------------
The temporary doctesting directory
   /Users/tnguyen/.sage/tmp/Godel.local-33429

was not removed: it is not empty, presumably because doctests
failed or doctesting was interrupted.

----------------------------------------------------------------------

The following tests failed:

    sage -t  --long -force_lib devel/sagenb-main/sagenb/misc/sphinxify.py # 5 doctests failed
    sage -t  --long -force_lib devel/sagenb-main/sagenb/misc/sageinspect.py # 8 doctests failed
    sage -t  --long -force_lib devel/sagenb-main/sagenb/misc/support.py # 1 doctests failed
    sage -t  --long -force_lib devel/sage/sage/interfaces/tachyon.py # 1 doctests failed

    sage -t  --long -force_lib devel/sage/sage/misc/cachefunc.pyx # 4 doctests failed
    sage -t  --long -force_lib devel/sage/sage/misc/sageinspect.py # 10 doctests failed
    sage -t  --long -force_lib devel/sage/sage/misc/sagedoc.py # 14 doctests failed
    sage -t  --long -force_lib devel/sage/sage/parallel/decorate.py # 1 doctests failed
    sage -t  --long -force_lib devel/sage/sage/structure/dynamic_class.py # 1 doctests failed
    sage -t  --long -force_lib devel/sage/sage/structure/element.pyx # 1 doctests failed
----------------------------------------------------------------------

Total time for all tests: 3696.3 seconds

make: *** [ptestlong] Error 128

[Keshav Kini]

On Mon, May 14, 2012 at 1:42 AM, ThanhVu Nguyen
<nguyent...@gmail.com> wrote:
> First, the variable $SAGE_ROOT is not set  in my computer (would this cause
> the problem ?).  The variable $SAGE is set to my Sage 4.8.

No, in fact you shouldn't set $SAGE_ROOT. I don't know about $SAGE, though.

[ThanhVu Nguyen]

 

No, in fact you shouldn't set $SAGE_ROOT. I don't know about $SAGE, though.

I think I set $SAGE manually.  

But anyway,  those are ones that fail to build on both of my Debian Squeeze and OS X Snow Leopard. 

[Dima Pasechnik]

to me this looks like you have something fishy installed in /usr/local/, and it gets picked up by mistake, either during the Sage installation, or during the testing...

[ThanhVu Nguyen]

to me this looks like you have something fishy installed in /usr/local/, and it gets picked up by mistake, either during the Sage installation, or during the testing...

 I have no idea,  but these errors occur on both my Mac and Linux systems.

[Dima Pasechnik]

On Sunday, 13 May 2012 09:24:07 UTC+2, ThanhVu Nguyen wrote:

I think many of these errors are due to

from common.conf import *
ImportError: No module named conf

what are the contents of SAGE_ROOT/devel/sage/doc/common ?

(which should be the same as SAGE_DOC/common )

What is the value of SAGE_DOC when you start Sage?

The following should give no error:

sage: import sys, os

sage: sys.path.append(os.environ['SAGE_DOC'])

sage: from common.conf import *

[ThanhVu Nguyen]

On Monday, May 14, 2012 10:05:08 AM UTC-6, Dima Pasechnik wrote:

On Sunday, 13 May 2012 09:24:07 UTC+2, ThanhVu Nguyen wrote:

I think many of these errors are due to

from common.conf import *
ImportError: No module named conf

what are the contents of SAGE_ROOT/devel/sage/doc/common ?

(which should be the same as SAGE_DOC/common )

$ cd /Users/tnguyen/Src/Devel/SAGE/sage-5.0.rc1
godel Mon May 14:10:58:42 (2615) ~/Src/Devel/SAGE/sage-5.0.rc1
$ ls devel/sage/doc/common/
__init__.py           builder.py            python.inv            themes/
build_options.py      builder.pyc           sage_autodoc.py       update-python-inv.sh*
build_options.pyc     conf.py 

 

What is the value of SAGE_DOC when you start Sage?

The following should give no error:

sage: import sys, os

sage: sys.path.append(os.environ['SAGE_DOC'])

sage: from common.conf import *

It gives error for me
 

godel Mon May 14:10:59:18 (2616) ~/Src/Devel/SAGE/sage-5.0.rc1
$ ./sage
----------------------------------------------------------------------
| Sage Version 5.0.rc1, Release Date: 2012-05-09                     |
| Type notebook() for the GUI, and license() for information.        |
----------------------------------------------------------------------
**********************************************************************
*                                                                    *
* Warning: this is a prerelease version, and it may be unstable.     *
*                                                                    *
**********************************************************************
sage: import sys,os
sage: print os.environ['SAGE_DOC']
/Users/tnguyen/Src/Devel/SAGE/sage-5.0.rc1/devel/sage/doc

sage: sys.path.append(os.environ['SAGE_DOC'])
sage: from common.conf import *

---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)

/Users/tnguyen/Src/Devel/SAGE/sage-5.0.rc1/<ipython console> in <module>()

ImportError: No module named conf

I also notice I have the following  variables in my bash_profile , would these cause problem ?  for example, the SAGE_PATH variable.  


export SAGE=$DEVEL/SAGE/sage
export PATH=$SAGE:$PATH
export SAGE_PATH=$DROPBOX/code/invgen/current
export SAGE64="yes"
export SAGE_PARALLEL_SPKG_BUILD="yes"