sage-4.3.1 release
William Stein
I've released sage-4.3.1.
Get the source here:
http://sage.math.washington.edu/sage/src/
Upgrade (in a day or so you can omit the http:// for faster upgrade):
sage -upgrade http://sagemath.org/packages/
The release managers were Mike Hansen and Robert Miller. There were
billions of tickets closed and bugs fixed. Binaries will appear in
the next few days, first here
http://sage.math.washington.edu/home/wstein/binaries/, then in their
proper place.
William
William
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
Gonzalo Tornaria
> Hi,
>
> I've released sage-4.3.1.
>
WTF:
**********************************************************************
Error installing Fortran: You must install gfortran or set
SAGE_FORTRAN (and possibly SAGE_FORTRAN_LIB).
**********************************************************************
I guess you probably know about this. However, rc1 worked fine without
gfortran --- and prereq didn't mention anything about gfortran!
----
BTW, I've got a failed doctest in rc1, but I didn't get time to report
before the final release:
sage -t devel/sage/sage/misc/sagedoc.py
**********************************************************************
File "/scratch/tornaria/sage-4.3.1.rc1/devel/sage-main/sage/misc/sagedoc.py",
line 365:
sage: 'abvar/homology' in _search_src_or_doc('doc', 'homology',
'variety', interact=False)
Expected:
True
Got:
False
**********************************************************************
1 items had failures:
1 of 6 in __main__.example_5
***Test Failed*** 1 failures.
For whitespace errors, see the file
/home/tornaria/.sage//tmp/.doctest_sagedoc.py
[10.0 s]
Gonzalo
William Stein
> On Wed, Jan 20, 2010 at 9:37 PM, William Stein <wst...@gmail.com> wrote:
>> Hi,
>>
>> I've released sage-4.3.1.
>>
>
> WTF:
>
> **********************************************************************
>
>
> Error installing Fortran: You must install gfortran or set
> SAGE_FORTRAN (and possibly SAGE_FORTRAN_LIB).
>
>
> **********************************************************************
>
> I guess you probably know about this. However, rc1 worked fine without
> gfortran --- and prereq didn't mention anything about gfortran!
I've created a ticket requesting prereq to include a test for gfortran
when not on OS X:
http://trac.sagemath.org/sage_trac/ticket/8026
>
> ----
>
> BTW, I've got a failed doctest in rc1, but I didn't get time to report
> before the final release:
>
> sage -t devel/sage/sage/misc/sagedoc.py
> **********************************************************************
> File "/scratch/tornaria/sage-4.3.1.rc1/devel/sage-main/sage/misc/sagedoc.py",
> line 365:
> sage: 'abvar/homology' in _search_src_or_doc('doc', 'homology',
> 'variety', interact=False)
> Expected:
> True
> Got:
> False
> **********************************************************************
> 1 items had failures:
> 1 of 6 in __main__.example_5
> ***Test Failed*** 1 failures.
> For whitespace errors, see the file
> /home/tornaria/.sage//tmp/.doctest_sagedoc.py
> [10.0 s]
>
I can't replicate the above anywhere.
William
Gonzalo Tornaria
>> BTW, I've got a failed doctest in rc1, but I didn't get time to report
>> before the final release:
>>
>> sage -t devel/sage/sage/misc/sagedoc.py
>> **********************************************************************
>> File "/scratch/tornaria/sage-4.3.1.rc1/devel/sage-main/sage/misc/sagedoc.py",
>> line 365:
>> sage: 'abvar/homology' in _search_src_or_doc('doc', 'homology',
>> 'variety', interact=False)
>> Expected:
>> True
>> Got:
>> False
>> **********************************************************************
>> 1 items had failures:
>> 1 of 6 in __main__.example_5
>> ***Test Failed*** 1 failures.
>> For whitespace errors, see the file
>> /home/tornaria/.sage//tmp/.doctest_sagedoc.py
>> [10.0 s]
>>
>
> I can't replicate the above anywhere.
It no longer happens in sage-4.3.1 (it was 100% reproducible with rc1).
Gonzalo
kcrisman
built. Is that the case for you?
- kcrisman
Alex Ghitza
> I've released sage-4.3.1.
[...]
> The release managers were Mike Hansen and Robert Miller. There were
> billions of tickets closed and bugs fixed. Binaries will appear in
> the next few days, first here
> http://sage.math.washington.edu/home/wstein/binaries/, then in their
> proper place.
I built a binary for 32-bit archlinux, which is now up at:
http://sage.math.washington.edu/home/ghitza/sage-4.3.1-archlinux-i686-Linux.tar.lzma
(a 64-bit binary was already built by William.)
Harald, can you push this to the mirrors?
Best,
Alex
--
Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne
-- Australia -- http://www.ms.unimelb.edu.au/~aghitza/
Alex Ghitza
> Hi Alex,
>
> > I built a binary for 32-bit archlinux, which is now up at:
> >
> > http://sage.math.washington.edu/home/ghitza/sage-4.3.1-archlinux-i686-Linux.tar.lzma
>
> with your Arch Linux build?
>
> [1] http://wiki.sagemath.org/devel/BuildFarm/sage-4.3.1
>
So I just tried to do this, and gave up. Here's why: I had to go
chasing the various info (cpu type, gcc version, etc) on the two
machines I run Arch Linux on. Then I had to put this in the table
format on the wiki. Then I made a stupid mistake (forgot to divide by 2
:) in the new-and-improved textcha when I tried to submit the changes,
which meant that I had to go back. Once I was back, my changes were
gone from the input field and I would have had to start over.
This was 10-15 minutes of my time; it's not the end of the world, but
Sage doesn't pay me by the hour and I can spend this time more
productively.
I'm not saying that this wiki page is not a useful resource, but I don't
have the time or patience to go through this at each release.
William Stein
>
> <SNIP>
>
>> I'm not saying that this wiki page is not a useful resource, but I don't
>> have the time or patience to go through this at each release.
>
> me to save edits containing some strings, because it deemed those
> strings to be a sign of spam content or something. I would then spend
> minutes figuring out how to get the wiki to accept the edits or
> rewrite my edits.
>
> Anyway, if you want, you could send information according to the
> template below to sage-release and I'd update the wiki with the
> information you supply.
>
> OS version:
> Machine name:
> Architecture:
> 32/64 bit:
> RAM:
> Compiler:
> Build:
> Doctest:
>
Maybe you should add a command to sage, e.g.,
sage: _build_report()
or
sage -buildreport
that runs a script, gathers relevant information, then submits it
somewhere. The resulting submission could then be summarized on a web
page. This is a perfect example of where it would be far, far better
to spend time writing some code than doing something manually.
William
Alex Ghitza
Hi Minh,
Here is my build data:
>
> OS version: Arch Linux
> Machine name: artin
> Architecture: Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz
> 32/64 bit: 32
> RAM: 4 GB
> Compiler: gcc 4.4.2
> Build: yes
> Doctest: pass (long)
> OS version: Arch Linux
> Machine name: cartan
> Architecture: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz
> 32/64 bit: 64
> RAM: 4 GB
> Compiler: gcc 4.4.2
> Build: yes
> Doctest: pass (long)
> OS version: Arch Linux
> Machine name: frobenius
> Architecture: Mobile Intel(R) Pentium(R) 4 - M CPU 2.20GHz
> 32/64 bit: 32
> RAM: 1 GB
> Compiler: gcc 4.4.2
> Build: yes
> Doctest: pass (long)
Pat LeSmithe
> On Sun, 24 Jan 2010 12:18:19 +1100, Minh Nguyen <nguye...@gmail.com> wrote:
> machines I run Arch Linux on. Then I had to put this in the table
> format on the wiki. Then I made a stupid mistake (forgot to divide by 2
Ticket #3693
http://trac.sagemath.org/sage_trac/ticket/3693
should re-enable the wiki's GUI mode --- editing pages with (F)CKEditor
--- which may make it easier to update some pages.
Note: Math delimiters ($) may be stripped.