On Nov 22, 2007 7:17 AM, Nathan Dunfield <[EMAIL PROTECTED]> wrote:
> I encountered the following minor bug while upgrading to 2.8.13,
> namely the file
>
> $SAGEROOT/local/bin/sage-banner
>
> was not updated.   So when I started sage after doing "sage -upgrade"
> it claimed that I was still on 2.8.8.1:

Try doing

sage: hg_scripts.merge()
sage: hg_scripts.commit()

and answer any interactive questions.   We recently switched to "sage -upgrade"
*merging* in the scripts and several other hg repo's included in sage,
instead of
just overwriting them -- this is great, because it means people won't accidently
loose work when upgrading; however, it requires some slight manual intervention
when upgrading older installs.

William

> PBook ~ (12) sage
> ----------------------------------------------------------------------
> | SAGE Version 2.8.8.1, Release Date: 2007-10-21                     |
> | Type notebook() for the GUI, and license() for information.        |
> ----------------------------------------------------------------------
>
> even though within the interpreter the function "version()" correctly
> returns 2.8.13.
>
> sage: version()
> 'SAGE Version 2.8.13, Release Date: 2007-11-21'
>
> Details: OS X, version 10.4.10/Core Duo 2/original version of sage
> 2.7.1, upgraded several times.
>
>         Best,
>
>         Nathan
>
>
>
> >
>



-- 
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to