Mike Hansen and I have finished sage-4.2.1:
http://sage.math.washington.edu/home/wstein/farm/src/sage-4.2.1.tar
Release notes, binaries, the above being posted online, etc., will
follow in due course.
William
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
Yes Sage-4.3 will be the next release, and I hope it has some major
features (e.g., lots of the combinatorics codebase gets merged back
into mainline sage).
> I'll start work on doing a maintenance release for Sage 4.2.x up until
> April 2010. Incidentally, my proposal to do a maintenance release for
> up to 6 months coincide with the release schedule of Ubuntu, and I
> personally think that's a good way to do it.
What does this mean? Are you going to make binaries and source tarballs
that contain only bug fixes, and make it so people can "sage -upgrade"
to get them? I'm curious.
> Thinking about this task of doing maintenance releases a bit more,
> perhaps it's a good idea to do the same thing for the Debian port of
> Sage. I have thought about volunteering my time to work on both the
> maintenance releases as well as on updating the Debian port. But while
> I have some experience with release management within the Sage
> project, I have absolutely no experience at all with maintaining Sage
> or any other project for Debian or Ubuntu. I think that if one is to
> become a maintainer of a Debian package, then one needs to have the
> endorsement of an existing Debian maintainer. In the past, Tim Abbott
> has expressed an interest in helping anyone who would like to help
> maintain the Debian port of Sage. But I'm not sure how much time he
> has to devote to this, considering that I'm a complete newbie with
> respect to maintaining Debian packages.
Please, please, whoever does this, I implore you to first cut your
teeth by making a monolithic unofficial Sage deb that installs into
/opt (say)! This is a a billion times easier than doing what Tim
Abbott did, and yet will be incredibly useful to a lot of people at
the same time. And it definitely does add significant value over the
Sage tarballs we currently distribute, since the Debian build and
dependency system is quite sophisticated.
>
>
>> Release notes, binaries, the above being posted online, etc., will
>> follow in due course.
>
> I think I can resume the task of writing release tours, at least for
> Sage 4.2.1. I'll start on it today.
Thanks!
William
Is this intel? What happens if you do a clean build? If that works,
can you post a binary, since we have binaries for most everything
*except intel 10.5*, and Nick Alexander really wants such a binary.
William
I had exactly the same problem on my laptop. A workaround is to rebuild Maxima:
sage -f maxima-5.19.1.p0
Then it works:
flat:standard wstein$ sage -maxima
;;; Loading #P"/Users/wstein/s/local/lib/ecl/DEFSYSTEM.fas"
;;; Loading #P"/Users/wstein/s/local/lib/ecl/cmp.fas"
;;; Loading #P"/Users/wstein/s/local/lib/ecl/sysfun.lsp"
Maxima 5.19.1 http://maxima.sourceforge.net
Using Lisp ECL 9.10.2
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
...
sage: solve(x^3+17==0,x)
[x == 1/2*I*(-1)^(1/3)*sqrt(3)*17^(1/3) - 1/2*(-1)^(1/3)*17^(1/3), x
== -1/2*I*(-1)^(1/3)*sqrt(3)*17^(1/3) - 1/2*(-1)^(1/3)*17^(1/3), x ==
(-1)^(1/3)*17^(1/3)]
---
Since the upgrade *does* rebuild Maxima, there's nothing I can think
of to do about this... It's probably some weird 10.6 bug.
William