[issue17962] Broken OpenSSL version in Windows builds

2013-05-15 Thread Martin v . Löwis
Martin v. Löwis added the comment: I have now updated the code. Yogesh: It is somewhat more that just committing the source; the assembler files need to be generated. The objective is to not require Perl on the build machines. -- status: open -> closed ___

[issue17962] Broken OpenSSL version in Windows builds

2013-05-13 Thread Yogesh Chaudhari
Yogesh Chaudhari added the comment: @Antoine and @Georg: You are right. There is nothing much to be done. The only difference is those of auto-generated files like Makefile and other config files created after running ./config script. This just needs a simple add/commit from the openssl site

[issue17962] Broken OpenSSL version in Windows builds

2013-05-13 Thread Georg Brandl
Georg Brandl added the comment: I don't know what there is to do, so I can give no instructions. It's best to let Martin handle it. -- ___ Python tracker ___ __

[issue17962] Broken OpenSSL version in Windows builds

2013-05-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: I don't know how much work there is. Perhaps you want to produce a diff between the current "external" 1.0.1d and the upstream version. Otherwise just let Georg or Martin handle it ;) -- ___ Python tracker

[issue17962] Broken OpenSSL version in Windows builds

2013-05-13 Thread Yogesh Chaudhari
Yogesh Chaudhari added the comment: I would like to take a crack at it. Would it be possible(I mean permission wise)? How can I proceed? -- ___ Python tracker ___ __

[issue17962] Broken OpenSSL version in Windows builds

2013-05-12 Thread Georg Brandl
Georg Brandl added the comment: I could, but the checked-in 1.0.1d is different from the tarball in some respects, so it's better for Martin to do this. -- assignee: -> loewis ___ Python tracker _

[issue17962] Broken OpenSSL version in Windows builds

2013-05-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: Yes, someone with SVN write access (Georg?) will have to do it. -- ___ Python tracker ___ ___ Python

[issue17962] Broken OpenSSL version in Windows builds

2013-05-12 Thread Yogesh Chaudhari
Yogesh Chaudhari added the comment: I am not sure how http://www.openssl.org/source/openssl-1.0.1e.tar.gz can be provided to python svn. Doesn't that require svn credentials to check-out/add/check-in? -- ___ Python tracker

[issue17962] Broken OpenSSL version in Windows builds

2013-05-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: Apparently it lacks the required SVN addition: The system cannot find the file specified. svn: E17: URL 'http://svn.python.org/projects/external/openssl-1.0.1e' doesn't exist -- status: closed -> open ___ Python

[issue17962] Broken OpenSSL version in Windows builds

2013-05-12 Thread Roundup Robot
Roundup Robot added the comment: New changeset d047928ae3f6 by Georg Brandl in branch '3.3': Closes #17962: Build with OpenSSL 1.0.1e on Windows. http://hg.python.org/cpython/rev/d047928ae3f6 -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected status: open -> closed

[issue17962] Broken OpenSSL version in Windows builds

2013-05-12 Thread Yogesh Chaudhari
Yogesh Chaudhari added the comment: The following patch will make use of 1.0.1e version of OpenSSL -- keywords: +patch nosy: +Yogesh.Chaudhari Added file: http://bugs.python.org/file30232/issue17962.patch ___ Python tracker

[issue17962] Broken OpenSSL version in Windows builds

2013-05-12 Thread Stefan Drees
Changes by Stefan Drees : -- nosy: +sdrees ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue17962] Broken OpenSSL version in Windows builds

2013-05-12 Thread Antoine Pitrou
New submission from Antoine Pitrou: 3.3 and default are currently fetching OpenSSL 1.0.1d for the Windows builds. It seems OpenSSL 1.0.1d was a kind of "brown paper bag" release, they've released 1.0.1e since (some of test_ssl can fail on 1.0.1d and succeed on 1.0.1e, as experienced on my Linu