On Thu, Nov 27, 2008 at 1:34 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello, > > let's forget 3.2.1.alpha1 ever happened :) > > 3.2.1.alpha2 fixes the build issues from its predecessor (I did a full > build cycle before announcing here, so no need to do an alpha3 in the > next 24 hours) and adds a couple additional patches. One very > interesting patch set is #463 by William which will allow > > ./sage -upgrade foo.org/home/bar/sage-3.4.5.alpha2 > > in the future, i.e. you can upgrade to any install either via > webserver or even by directory on a local disk. (pulling from a local disk isn't implemented yet)
> But nothing like that > is bug free and since the infrastructure to do the in place upgrade to > other versions isn't in anything but 3.2.1.alpha2 yet the upgrade is You can try it out with any 3.2.1.*alpha* build in pretty much any broken or whatever state. Since you're probably going to throw away such builds anyways, why not try this out. Just do: ./sage -i http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.alpha2/spkg/standard/sage_scripts-3.2.1.alpha2 ./sage -upgrade http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.alpha2 The first line installs the upgraded scripts spkg, which has the new upgrade command. The second line upgrades from Michael's tree. Note that this may be surprisingly fast, since we no longer do "sage -ba" to upgrade the core library. On the other hand it might just not work at all -- this is a totally new feature and it definitely has problems: > still a little rough - see http://trac.sagemath.org/sage_trac/ticket/4638 > for details and a story on how to get from 3.2 to 3.2.1.alpha2 - it > isn't for the faint of heart. Once we have 3.2.1.alpha3 it will be > interesting to see how the upgrade from 3.2.1.alpha2 works. The > sources are in the usual place at > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/ > > Please build, test and report issues as usual. This release stands a > chance to actually compile on Fedora Core 10, but we will see. No > binary for sage.math until someone fixes #4317 :) > > To our American Brethren: Happy Turkey day. > > Cheers, > > Michael > > Merged in Sage 3.2.1.alpha2: > > #463: William Stein: sage -upgrade: "sage -upgrade URL" will install > all *newer* spkg's from the given URL, which can also be a local > directory [Reviewed by Michael Abshoff] > #4176: William Stein: matplotlib build failure due to broken tcl/tk > detection [Reviewed by Jaap Spies, Michael Abshoff] > #4613: Robert Bradshaw: doctests for big-o [Reviewed by Craig Citro] > #4624: William Stein: Sage 3.2.1.a1: add ipy_profile_sage.py to list > of files copied when sdisting [Reviewed by Michael Abshoff] > #4627: Nick Alexander: CRT_list in HNF dominates computation [Reviewed > by Craig Citro] > #4628: William Stein: sage-3.2.1.alpha1 -- setup.py build system is > foobar'd [Reviewed by Craig Citro] > #4634: Michael Abshoff: Sage 3.2.1.a1: numerical noise in sage/ > schemes/ elliptic_curves/ell_rational_field.py [Reviewed by Nick > Alexander] > #4635: Michael Abshoff, John Palmieri: Sage 3.2.1.a1: numerical noise > in sage/plot/plot.py [Reviewed by Nick Alexander] > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
