#6645: make sure bdist of sage-4.1.1 works before release
---------------------+------------------------------------------------------
 Reporter:  was      |       Owner:  tbd       
     Type:  defect   |      Status:  new       
 Priority:  blocker  |   Milestone:  sage-4.1.1
Component:  build    |    Keywords:            
 Reviewer:           |      Author:            
   Merged:           |  
---------------------+------------------------------------------------------
 {{{
 Hi,

 I took the sage-4.1.1.alpha1 release build I had, then did "./sage
 -bdist", took the result, extracted it, and did "make test".

  1) It sits there and builds the documentation again, which takes a *long*
 time.  It shouldn't do this for a binary.

  2) Worse, every single test failed, with errors like this:

 sage -t
 
"/home/wstein/build/sage-4.1.1.alpha1/dist/sage-4.1.1.alpha1-x86_64-Linux/devel/sage/doc/common/buil
 der.py"
   File "./builder.py", line 18
     from
 
/home/wstein/build/sage-4.1.1.alpha1/dist/sage-4.1.1.alpha1-x86_64-Linux/devel/sage/doc/common/build
 er import *
          ^

   3) I tried do "./sage" to run Sage, then typed "make test" again about
 10 minutes ago.  For some reason, the docs are building again... and I
 expect the same behavior as above after that finally finishes.

 Buiding Sage, doing "./sage -bdist", then extracting the result and having
 "make test" 100% is a blocker for making the sage-4.1.1 release.

 William
 }}}

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6645>
Sage <http://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