#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: sage-4.6.rc0
Work_issues: |
------------------------------+---------------------------------------------
Comment(by leif):
Replying to [comment:137 mpatel]:
> Replying to [comment:133 mpatel]:
> > Following Jeroen's [http://groups.google.com/group/sage-
devel/browse_thread/thread/2253505ea7ae98ae suggestion on sage-devel], I'm
planning to merge this ticket into 4.6.rc0.
>
> I'll merge all of the patches and files in the description's current
"How to merge this ticket" section.
Thanks!
Upgrading from Sage 4.4.4 in a renamed directory (with the official rc0
upgrade path) fully worked for me on Ubuntu 9.04 x86_64 (Core2, gcc 4.3.3;
parallel build with 16 jobs).
Quite surprisingly, even {{{ptestlong}}} passed without any doctest
errors. ;-) (Cf. sage-release.)
Despite that, I guess there are still missing dependencies in
{{{module_list.py}}} that will come into play when e.g. updating MPIR
(#8664). (I primarily addressed upgrading to the new PARI on this ticket;
more changes should IMHO be made on other / the respective spkg tickets.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9896#comment:138>
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.
