New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade PyCrypto to upstream 2.1.0 #9338
Comments
comment:1
I'm still testing this spkg, so it's not ready for review. |
Author: Minh Van Nguyen |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:3
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.
|
comment:4
I'm still waiting for build/test results on t2.math. |
comment:5
Build fine on t2.math and |
comment:6
Also build fine on Cygwin ( |
Reviewer: David Kirkby |
comment:7
You have clearly tested this thoroughly Minh - I wish all Sage developers were like you. I just tested it on two systems:
shows no problems, so positive review. Dave |
Merged: sage-4.5.3.alpha0 |
As the subject says. The latest version also fixes the issue with ARC2 reported at http://www.securityfocus.com/bid/33674/info. Currently, the PyCrypto spkg maintains patches for this issue. Upgrading to the latest upstream version would mean we no longer need to maintain those patches in the spkg itself.
Apply:
http://sage.math.washington.edu/home/mvngu/spkg/standard/pycrypto/pycrypto-2.1.0.spkg
Changes in this upgraded spkg include:
Make sure to update #9281 when spkg-check runs the test suite fine.
Component: packages: standard
Author: Minh Van Nguyen
Reviewer: David Kirkby
Merged: sage-4.5.3.alpha0
Issue created by migration from https://trac.sagemath.org/ticket/9338
The text was updated successfully, but these errors were encountered: