#4321: [with spkg, with positive review] wrong Unix permissions in some PolyBoRi
files
--------------------------+-------------------------------------------------
 Reporter:  zimmerma      |        Owner:  mabshoff  
     Type:  defect        |       Status:  closed    
 Priority:  blocker       |    Milestone:  sage-3.2.1
Component:  distribution  |   Resolution:  fixed     
 Keywords:                |  
--------------------------+-------------------------------------------------
Comment (by mabshoff):

 Replying to [comment:12 was]:
 > It seems to me Michael that you reviewed the patch, and I think putting
 it in the spkg is just sort of applying it.  So I think all that has to be
 done is somebody else to check that the spkg looks good.

 There were two issues: one is the headers, the other one was the man page.
 Craig reviewed the header issue as well as Alexander's fix once I told him
 what it did.

 > I have looked in the spkg and it looks good.  I also tried building it
 and it built fine.  After building, I looked at the permissions and they
 are now right.  so... another positive review in addition to Craig's. :-)

 I did a cp of the whole Sage tree after fixing this and the Singular
 header permission issue and for now there are no more problems, so Paul
 can be assured that issue is gone for now. I will keep testing that no
 other permission issues return since Sage should never be released with
 such a permission problem.

 Cheers,

 Michael

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4321#comment:13>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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