#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):

 Replying to [comment:65 jhpalmieri]:
 > As is often the case with upgrading, I'm puzzled by the logic here.  How
 can any patches help an upgrade from 4.5.3 (for example) to 4.6?
 >
 >  - Upgrading won't affect files like {{{spkg/standard/deps}}} or
 {{{spkg/install}}} as long as those files aren't tracked anywhere -- see
 #9433.

 {{{sage-upgrade.py}}} also copies these two files (cf. the
 {{{pipestatus}}} issue with upgrading to 4.5[.1]).

 >  - Upgrading will change scripts like {{{sage-upgrade}}}, but of course
 it has to be running the old versions during the upgrade process.

 The new {{{spkg/install}}} is aware of that, i.e. deals with an old
 {{{sage-upgrade}}}, too. (See comments in the patch to the former.)

 > I can understand that patches to these files might help in future
 versions, but is there any way to deal with 4.5.3 to 4.6?

 The patches are intended to especially deal with this (and should ease
 future upgrades as well).

 > (Meanwhile, I'm building a vanilla 4.5.3 to test the new upgrade path.)

 Fine. I've copied a 4.5.3 installation (''of course''^TM^ first running
 out of disk space) on Ubuntu 9.04 x86 and am currently running the
 upgrade.

 Note that when teeing the output it appears to hang, since the user is
 prompted, but the output isn't flushed. (One has to type "y" and hit
 return to start upgrading.) I'll open a ticket for that.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9896#comment:66>
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.

Reply via email to