#9896: Upgrading from 4.5.3 to 4.6.alpha* can fail (not limited to MacOS X)
------------------------------+---------------------------------------------
Reporter: jhpalmieri | Owner: GeorgSWeber
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-4.6
Component: build | Keywords: upgrade update dependencies PARI
NewPARI
Author: Leif Leonhardy | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by leif):
From {{{sage-sage}}}:
{{{
#!sh
if [ "$1" = '-upgrade' -o "$1" = "--upgrade" ]; then
# People often move the Sage install right before doing the upgrade,
so it's
# important to fix any path hardcoding issues first, or certain
library
# links will fail.
"$SAGE_ROOT/local/bin/"sage-location
# Do it twice since when installing sage-scripts and a running
# script changes, it gets confused and exits with an error.
# Running again (with the script replaced) then fixes the problem.
# Run from a temporary copy of sage-sage
shift
sage-upgrade "$@"
if [ $? = 2 ]; then # this exit codes means the user elected not to
do the upgrade at all.
exit $?
fi
echo "Double checking that all packages have been installed."
sage-upgrade "$@"
exit $?
fi
}}}
But {{{sage-update}}} won't download {{{spkg/install}}} twice if ''"No new
spkgs"'' are available, which should be the case after a successful
(first) upgrade.
So it must get overwritten from somewhere else...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9896#comment:80>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
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-trac?hl=en.
