#9338: upgrade PyCrypto to upstream 2.1.0
-------------------------------+--------------------------------------------
   Reporter:  mvngu            |       Owner:  tbd         
       Type:  enhancement      |      Status:  needs_review
   Priority:  major            |   Milestone:  sage-4.5    
  Component:  packages         |    Keywords:              
     Author:  Minh Van Nguyen  |    Upstream:  N/A         
   Reviewer:                   |      Merged:              
Work_issues:                   |  
-------------------------------+--------------------------------------------
Changes (by mvngu):

  * status:  new => needs_review


Comment:

 The test results are summarized below. I only ran the spkg-check script of
 the !PyCrypto spkg. This was tested with Sage 4.4.4. With the exception of
 cicero.skynet, all machines reported here are 64-bit.

  1. bsd.math: Mac OS X 10.6.4, GCC 4.2.1, Dual-Core Intel Xeon @ 2.66 GHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. cicero.skynet: 32-bit Fedora 12, GCC 4.5.0, Intel(R) Pentium(R) 4 CPU
 @ 2.66GHz
     * build: yes
     * doctest: one failure in `libs/mwrank/mwrank.pyx`, as reported
 [https://groups.google.com/group/sage-
 release/browse_thread/thread/20dcc2ac0c5b978c here]
     * spkg-check: pass
  1. cleo.skynet: Red Hat Enterprise Linux Server 5.3, GCC 4.5.0, IA-64
 Itanium 2 @ 1594.000726 MHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. eno.skynet: Fedora 12, GCC 4.5.0, Intel(R) Xeon(R) CPU E5345 @ 2.33GHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. flavius.skynet: Fedora 12, GCC 4.5.0, AMD Opteron(tm) Processor 248 @
 2193.570 MHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. gcc11.fsffrance: Debian 5.0, GCC 4.3.2, Dual-Core AMD Opteron(tm)
 Processor 2212 @ 2000.085 MHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. gcc16.fsffrance: Debian 5.0, GCC 4.3.2, Quad-Core AMD Opteron(tm)
 Processor 8354 @ 2194.496 MHz
     * build: yes
     * doctest: [https://groups.google.com/group/sage-
 release/browse_thread/thread/7a8a2e2af0eafde7 2 failures] in
 `schemes/elliptic_curves/lseries_ell.py`
     * spkg-check: pass
  1. gcc100.fsffrance: Debian 5.0, GCC 4.3.2, AMD Opteron(tm) Processor 252
 @ 2600.011 MHz
     * build: yes
     * doctest: failures in `modules/free_module.py`
     * spkg-check: pass
  1. iras.skynet: SUSE Linux Enterprise Server 10 SP1, GCC 4.5.0, IA-64 @
 1594.000683 MHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. lena.skynet: Fedora 12, GCC 4.5.0, AMD Phenom(tm) II X4 940 Processor
 @ 3000.000 MHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. menas.skynet: openSUSE 11.1, GCC 4.5.0, Intel(R) Core(TM)2 Quad CPU
 Q6600 @ 2.40GHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. rh.math: Ubuntu 10.04 LTS, GCC 4.4.3, Six-Core AMD Opteron(tm)
 Processor 8439 SE @ 800.000 MHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. sage.math: Ubuntu 8.04.4 LTS, GCC 4.2.4, Intel(R) Xeon(R) CPU X7460 @
 2.66GHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. sextus.skynet: Fedora 12, GCC 4.5.0, Intel(R) Xeon(TM) CPU @ 3.60GHz
     * build: yes
     * doctest: pass
     * spkg-check: pass
  1. taurus.skynet: Fedora 12, GCC 4.5.0, Intel(R) Xeon(R) CPU X5570 @
 2.93GHz
     * build: no, due to Linbox failing to build on taurus. This is a known
 issue. But forcing an installation of the !PyCrypto spkg with "./sage -f
 <...>", and then running spkg-check, worked fine.
     * doctest: N/A since Sage 4.4.4 fails to build on taurus
     * spkg-check: pass

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