#9960: require SAGE_CHECK to be "yes"
---------------------------------------------------------+------------------
   Reporter:  jhpalmieri                                 |       Owner:  was    
   
       Type:  defect                                     |      Status:  
needs_work
   Priority:  major                                      |   Milestone:  
sage-4.7  
  Component:  user interface                             |    Keywords:         
   
     Author:  John Palmieri, Leif Leonhardy              |    Upstream:  N/A    
   
   Reviewer:  Leif Leonhardy, Ivan Andrus, David Kirkby  |      Merged:         
   
Work_issues:                                             |  
---------------------------------------------------------+------------------

Comment(by jhpalmieri):

 Jeroen: The line cited by the error
 {{{
 /scratch/jdemeyer/merger/sage-4.7.alpha3/local/bin/sage-spkg: line 436:
 syntax error near unexpected token `('
 /scratch/jdemeyer/merger/sage-4.7.alpha3/local/bin/sage-spkg: line 436: `
 echo "(cd '`pwd`' && '$SAGE_ROOT/sage' -sh)"'
 }}}
 is not touched by this patch.  Did you run "sage -sdist ..." or just apply
 the patch to the scripts repo?  If you just applied it to the scripts
 repo, then the version of sage-spkg in the repo will not match with the
 version in spkg/base/, and I think that could cause an error like the one
 you saw.

 I ran "sage -sdist ..." and then started building from the new tar file,
 and it's going fine: it's built around 50 of the spkgs, including
 sage_scripts, with no problems.

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