Re: [sage-devel] Sage 4.3.2.alpha1 released

[Alex Ghitza]

Just a quick note: on two different systems, upgrading from alpha0 has
mercurial put me in commit mode with something like:

HG: changed sage-banner
HG: changed sage-gdb-commands
HG: changed sage-maxima.lisp
HG: changed sage-verify-pyc

Could it be that one of the repositories had uncommited changes?

Best,
Alex

On Mon, 1 Feb 2010 19:03:44 +1100, Minh Nguyen <nguye...@gmail.com> wrote:
> This is a rather quick release since Sage 4.3.2.alpha0. The original
> plan was for Sage 4.3.2 to be out a few days before Sage Days 20.
> However, the schedule for the final release has been shifted [1] to
> Saturday 06th February 2010, Pacific time. The upcoming rc0 release is
> strictly for bug fixes. A major new feature in this release is having
> Dan Drake's SageTeX package in the standard spkg repository.
>

--
Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne
-- Australia -- http://www.ms.unimelb.edu.au/~aghitza/

[Dima Pasechnik]

about upgrading (a newbie question)

Against what release this upgrade is made?
Can I do
./sage -upgrade http://...
where ./sage is the stable 4.3.1?

Thanks,
Dima

On Feb 1, 5:44 pm, Minh Nguyen <nguyenmi...@gmail.com> wrote:
> Hi Alex,
>
> On Mon, Feb 1, 2010 at 8:23 PM, Alex Ghitza <aghi...@gmail.com> wrote:
>
> <SNIP>

>
> > Could it be that one of the repositories had uncommited changes?
>

> There is no uncommitted changes for the following files:
>
> * sage-banner
> * sage-gdb-commands
> * sage-maxima.lisp
> * sage-verify-pyc
>
> Before packaging up the Sage 4.3.2.alpha1 source tarball, I committed
> changes using Mercurial so that these files have their executable bits
> turned off, as they should be. What you reported above is harmless.
> Mercurial notices that the executable bits of these files are now off,
> whereas previously they were turned on for your Sage installation. To
> proceed with the upgrade, you could check in the changes that
> Mercurial reports. But in actual fact, there's not any changes to the
> content of these files.
>
> --
> Regards
> Minh Van Nguyen

[Alex Ghitza]

See below for 2 build/test reports.

(I had also tried upgrading on Mac OS 10.5.8, but that gave me a
bunch of doctest failures. I will double-check before reporting.)

Best,
Alex

------------- ONE ------------------

OS version: Arch Linux
Machine name: artin
Architecture: Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz
32/64 bit: 32 bit
RAM: 4 GB
Compiler: gcc 4.4.3
Build: yes (upgrade from 4.3.2.alpha0)
Doctest: all long tests pass

------------- TWO ------------------

OS version: RHEL 5.3
Machine name: skadi
Architecture: SunFire X4600M2, 8x 2.3GHz Quad-Core AMD CPUs
32/64 bit: 64 bit
RAM: 64 GB
Compiler: gcc 4.1.2
Build: yes (upgrade from 4.3.2.alpha0)
Doctest: 1 long doctest failure

The following tests failed:
sage -t -long devel/sage/sage/parallel/decorate.py # Segfault

This only seems to happen when I run the whole testsuite. If I try to
run this test on its own, it always passes. (I had the same issue in
alpha0.) It could just be something that only comes up under stress --
I was testing things in parallel with 16 threads. Anyway, I don't
think we can do much about it right now.

[Dan Drake]

I built and tested alpha0 on two machines. No doctest errors, but
SageTeX doesn't seem to get installed, even though it's in
spkg/standard. Everything in spkg/install and so on seems fine, but
the spkg isn't installed.

Dan

--
--- Dan Drake
----- http://mathsci.kaist.ac.kr/~drake
-------

[Alex Ghitza]

On Mon, 1 Feb 2010 04:26:59 -0800 (PST), Dima Pasechnik <dim...@gmail.com> wrote:
>
> Against what release this upgrade is made?
> Can I do
> ./sage -upgrade http://...
> where ./sage is the stable 4.3.1?
>

Hi Dima,

Yes, you should be able to do this (the upgrade script automagically
figures out what to do). Sometimes there are changes that make an
upgrade impossible, but it's pretty rare.

Best,
Alex

[John Cremona]

I built 4.3.2.alpha1 successfully on 64-bit ubuntu and has no test
failures with a 10-processor parallel test of everything.

John

On 1 February 2010 18:16, Minh Nguyen <nguye...@gmail.com> wrote:
> Hi Dan,
>
> On Mon, Feb 1, 2010 at 11:55 PM, Dan Drake <dr...@kaist.edu> wrote:
>
> <SNIP>

>
>> Everything in spkg/install and so on seems fine, but
>> the spkg isn't installed.
>

> Searching the entire Sage 4.3.2.alpha1 installation doesn't reveal
> that SageTeX is installed under SAGE_LOCAL/share as it should:
>
> [mvngu@mod sage-4.3.2.alpha1-sage.math]$ find ./ | grep 'sagetex'
> ./examples/.hg/data/latex_embed/sagetex.sty.i
> ./examples/.hg/data/latex_embed/sagetex.pyc.i
> ./examples/.hg/data/latex_embed/sagetexpackage.dtx.i
> ./examples/.hg/data/latex_embed/sagetexpackage.pdf.d
> ./examples/.hg/data/latex_embed/sagetex.py.i
> ./examples/.hg/data/latex_embed/sagetexpackage.pdf.i
> ./examples/.hg/data/latex_embed/sagetexpackage.ins.i
> ./examples/.hg/data/latex_embed/auto/sagetex.el.i
> ./local/lib/python2.6/site-packages/sagenb-0.6-py2.6.egg/sagenb/notebook/sagetex.py
> ./devel/sage-main/build/lib.linux-x86_64-2.6/sage/server/notebook/sagetex.py
> ./devel/sage-main/build/sage/server/notebook/sagetex.pyc
> ./devel/sage-main/build/sage/server/notebook/sagetex.py
> ./devel/sage-main/.hg/store/data/sage/server/notebook/sagetex.py.i
> ./devel/sage-main/.hg/store/data/doc/en/tutorial/sagetex.rst.i
> ./devel/sage-main/.hg/store/data/doc/en/reference/other/sagetex.rst.i
> ./devel/sage-main/.hg/store/data/doc/en/installation/sagetex.rst.i
> ./devel/sage-main/sage/server/notebook/sagetex.py
> ./devel/sage-main/doc/output/doctrees/en/tutorial/sagetex.doctree
> ./devel/sage-main/doc/output/doctrees/en/installation/sagetex.doctree
> ./devel/sage-main/doc/output/doctrees/en/reference/other/sagetex.doctree
> ./devel/sage-main/doc/output/html/en/tutorial/sagetex.html
> ./devel/sage-main/doc/output/html/en/tutorial/_sources/sagetex.txt
> ./devel/sage-main/doc/output/html/en/reference/other/sagetex.html
> ./devel/sage-main/doc/output/html/en/reference/_sources/other/sagetex.txt
> ./devel/sage-main/doc/output/html/en/installation/sagetex.html
> ./devel/sage-main/doc/output/html/en/installation/_sources/sagetex.txt
> ./devel/sage-main/doc/en/reference/other/sagetex.rst
> ./devel/sage-main/doc/en/installation/sagetex.rst
> ./devel/sage-main/doc/en/tutorial/sagetex.rst
> ./spkg/standard/sagetex-2.2.3.spkg
>
> But when I forced a re-installation, SageTeX would be installed under
> SAGE_LOCAL:
>
> [mvngu@mod sage-4.3.2.alpha1-sage.math]$ find ./ | grep 'sagetex'
> ./examples/.hg/data/latex_embed/sagetex.sty.i
> ./examples/.hg/data/latex_embed/sagetex.pyc.i
> ./examples/.hg/data/latex_embed/sagetexpackage.dtx.i
> ./examples/.hg/data/latex_embed/sagetexpackage.pdf.d
> ./examples/.hg/data/latex_embed/sagetex.py.i
> ./examples/.hg/data/latex_embed/sagetexpackage.pdf.i
> ./examples/.hg/data/latex_embed/sagetexpackage.ins.i
> ./examples/.hg/data/latex_embed/auto/sagetex.el.i
> ./local/share/texmf/tex/generic/sagetex
> ./local/share/texmf/tex/generic/sagetex/sagetex.sty
> ./local/share/texmf/tex/generic/sagetex/sagetexparse.py
> ./local/share/texmf/tex/generic/sagetex/sagetexpackage.pdf
> ./local/share/texmf/tex/generic/sagetex/sagetexpackage.ins
> ./local/share/texmf/tex/generic/sagetex/sagetexpackage.dtx
> ./local/share/texmf/tex/generic/sagetex/py-and-sty.dtx
> ./local/share/texmf/tex/generic/sagetex/remote-sagetex.py
> ./local/share/texmf/tex/generic/sagetex/remote-sagetex.dtx
> ./local/share/texmf/tex/generic/sagetex/scripts.dtx
> ./local/share/texmf/tex/generic/sagetex/makestatic.py
> ./local/share/texmf/tex/generic/sagetex/extractsagecode.py
> ./local/share/texmf/tex/generic/sagetex/example.tex
> ./local/share/texmf/tex/generic/sagetex/example.pdf
> ./local/lib/python2.6/site-packages/sagetex-2.2.3-py2.6.egg-info
> ./local/lib/python2.6/site-packages/sagetex.pyc
> ./local/lib/python2.6/site-packages/sagetex.py
> ./local/lib/python2.6/site-packages/sagenb-0.6-py2.6.egg/sagenb/notebook/sagetex.py
> ./devel/sage-main/build/lib.linux-x86_64-2.6/sage/server/notebook/sagetex.py
> ./devel/sage-main/build/sage/server/notebook/sagetex.pyc
> ./devel/sage-main/build/sage/server/notebook/sagetex.py
> ./devel/sage-main/.hg/store/data/sage/server/notebook/sagetex.py.i
> ./devel/sage-main/.hg/store/data/doc/en/tutorial/sagetex.rst.i
> ./devel/sage-main/.hg/store/data/doc/en/reference/other/sagetex.rst.i
> ./devel/sage-main/.hg/store/data/doc/en/installation/sagetex.rst.i
> ./devel/sage-main/sage/server/notebook/sagetex.py
> ./devel/sage-main/doc/output/doctrees/en/tutorial/sagetex.doctree
> ./devel/sage-main/doc/output/doctrees/en/installation/sagetex.doctree
> ./devel/sage-main/doc/output/doctrees/en/reference/other/sagetex.doctree
> ./devel/sage-main/doc/output/html/en/tutorial/sagetex.html
> ./devel/sage-main/doc/output/html/en/tutorial/_sources/sagetex.txt
> ./devel/sage-main/doc/output/html/en/reference/other/sagetex.html
> ./devel/sage-main/doc/output/html/en/reference/_sources/other/sagetex.txt
> ./devel/sage-main/doc/output/html/en/installation/sagetex.html
> ./devel/sage-main/doc/output/html/en/installation/_sources/sagetex.txt
> ./devel/sage-main/doc/en/reference/other/sagetex.rst
> ./devel/sage-main/doc/en/installation/sagetex.rst
> ./devel/sage-main/doc/en/tutorial/sagetex.rst
> ./spkg/installed/sagetex-2.2.3
> ./spkg/standard/sagetex-2.2.3.spkg
>
> Looks like the spkg dependency rules in SAGE_ROOT/spkg/install and/or
> SAGE_ROOT/spkg/standard/deps need to be modified somehow. This is now
> ticket #8144:
>
> http://trac.sagemath.org/sage_trac/ticket/8144

>
> --
> Regards
> Minh Van Nguyen
>

> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>

[mhampton]

All tests passed on my OS X 10.4.11 intel mac when running serially.
With a parallel test run, I got one failure on parallel/decorate.py.

-Marshall

[David Joyner]

On Mon, Feb 1, 2010 at 3:03 AM, Minh Nguyen <nguye...@gmail.com> wrote:
> Hi folks,

>
> This is a rather quick release since Sage 4.3.2.alpha0. The original
> plan was for Sage 4.3.2 to be out a few days before Sage Days 20.
> However, the schedule for the final release has been shifted [1] to
> Saturday 06th February 2010, Pacific time. The upcoming rc0 release is
> strictly for bug fixes. A major new feature in this release is having
> Dan Drake's SageTeX package in the standard spkg repository.
>

> The source tarball is available at
>
> http://boxen.math.washington.edu/home/mvngu/sage-src/sage-4.3.2.alpha1.tar
>
> The upgrade path is
>
> http://boxen.math.washington.edu/home/mvngu/release/upgrade/sage-4.3.2.alpha1/
>
> and the sage.math binary is
>
> http://boxen.math.washington.edu/home/mvngu/sage.math-bin/sage-4.3.2.alpha1-sage.math.washington.edu-x86_64-Linux.tar.gz
>
> Please test and report all problems. The following tickets were merged
> in Sage 4.3.2.alpha1:
>

built fine on mac 10.6.2 but one failure for sage -testall :

The following tests failed:

sage -t "devel/sage/sage/structure/element_wrapper.py" # Segfault

...