On Nov 26, 2007 1:42 AM, Simon King <[EMAIL PROTECTED]> wrote:
>
> Dear Sage team,
>
> i just upgraded sage on two machines. One has gcc 4.1.2 on it, the
> other has gcc 4.2.1.
> On the machine with 4.1.2, starting sage still looks like this:
> > sage
> ----------------------------------------------------------------------
> | SAGE Version 2.8.10, Release Date: 2007-10-28 |
> | Type notebook() for the GUI, and license() for information. |
> ----------------------------------------------------------------------
>
> although the update was essentially successful:
>
> sage: version()
> 'SAGE Version 2.8.14, Release Date: 2007-11-24'
>
> On the machine with 4.2.1, the 2.8.14 banner on starting sage looks as
> it should.
>
> Certainly this is no serious bug, but i was a bit surprised when i
> started sage.
This was discussed on sage-devel. I've forwarded the conversation to you.
Basically you have to do something manual to merge in the new
verison of the sage_scripts package. See below.
Forwarded conversation
Subject: [sage-devel] Banner not updated
------------------------
From: *Nathan Dunfield* <[EMAIL PROTECTED]>
Date: Nov 22, 2007 7:17 AM
To: [EMAIL PROTECTED]
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:
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
----------
From: *William Stein* <[EMAIL PROTECTED]>
Date: Nov 22, 2007 3:37 PM
To: [EMAIL PROTECTED]
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
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
----------
From: *Nathan Dunfield* <[EMAIL PROTECTED]>
Date: Nov 22, 2007 7:59 PM
To: sage-devel <[EMAIL PROTECTED]>
This doesn't seem to do anything:
sage: hg_scripts.merge()
cd "/pkgs/sage-2.7.1/local/bin" && hg merge
abort: there is nothing to merge - use "hg update" instead
sage: hg_scripts.commit()
cd "/pkgs/sage-2.7.1/local/bin" && hg diff | less
cd "/pkgs/sage-2.7.1/local/bin" && hg commit
nothing changed
If I follow the suggestion of .merge() I get
sage: hg_scripts.update()
cd "/pkgs/sage-2.7.1/local/bin" && hg update
abort: untracked local file 'sage-wiki' differs from remote version
More to the point, I do recall being asked some questions by "hg"
during the upgrade process ("(k)eep or (d)iscard" or similar). I
didn't pay much attention to them, but I guess I should have ;-).
----------
From: *mabshoff* <[EMAIL PROTECTED]>
Date: Nov 23, 2007 2:20 AM
To: sage-devel <[EMAIL PROTECTED]>
Hello Nathan,
It might have been captured in the log. Could you check there? It has
come up at least twice with 2.8.13 and we should really get this issue
resolved.
> Nathan
Cheers,
Micheal
----------
From: *William Stein* <[EMAIL PROTECTED]>
Date: Nov 23, 2007 9:18 AM
To: [EMAIL PROTECTED]
...
See where it says "abort: <a reason>". It's aborting at that point.
If you do
rm SAGE_ROOT/local/bin/sage-wiki
then do hg_scripts.update() again, it won't abort for that reason
and you'll get the new hg repo for scripts merged in.
-- William
----------
From: *Nathan Dunfield* <[EMAIL PROTECTED]>
Date: Nov 25, 2007 9:33 AM
To: sage-devel <[EMAIL PROTECTED]>
> > during the upgrade process ("(k)eep or (d)iscard" or similar). ...
I didn't see anything relevant in SAGE_ROOT/install.log. I've put
the file at
http://dunfield.info/temp/install.log
if anyone wants to have a look.
Thanks, that fixed the problem. Having done the above, the upgrade to
2.8.14 went smoothly, with the correct updated banner.
Best,
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@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-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
