[tahoe-dev] [tahoe-lafs] #1065: provide binary eggs of PyCrypto for our supported platforms

[tahoe-lafs]

#1065: provide binary eggs of PyCrypto for our supported platforms
---------------------------+------------------------------------------------
     Reporter:  zooko      |       Owner:  somebody                       
         Type:  defect     |      Status:  new                            
     Priority:  major      |   Milestone:  soon (release n/a)             
    Component:  packaging  |     Version:  1.6.1                          
   Resolution:             |    Keywords:  windows setuptools pycrypto-lib
Launchpad Bug:             |  
---------------------------+------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:7 davidsarah]:
 > This was actually committed to trunk, in [4703]. It doesn't seem to have
 caused any new buildbot failures.

 Sigh, spoke too soon ([http://tahoe-
 lafs.org/buildbot/builders/Ruben%20Fedora/builds/610/steps/test/logs/stdio
 log for the test step on 'Ruben Fedora']):

 {{{
 Searching for pycrypto==2.1.0
 Best match: pycrypto 2.1.0
 Processing pycrypto-2.1.0-py2.7-linux-x86_64.egg
 pycrypto 2.1.0 is already the active version in easy-install.pth

 Using /home/buildbot/tahoe/Ruben Fedora/build/support/lib/python2.7/
 site-packages/pycrypto-2.1.0-py2.7-linux-x86_64.egg
 [...]
 running trial
 [...]
 pkg_resources.VersionConflict: (pycrypto 2.2 (/usr/lib64/python2.7/
 site-packages), Requirement.parse('pycrypto==2.0.1,==2.1,>=2.3'))
 }}}

 I believe this is due to the same underlying issue as #1137, that is, the
 handling of {{{sys.path}}} by the setuptools-installed {{{site.py}}} and
 {{{.pth}}} files being broken. If the path handling were working
 correctly, it should not have been possible that "pycrypto 2.1.0 is
 already the active version in easy-install.pth", but we end up importing
 pycrypto 2.2 when running trial.

 Note that we have the same problem with foolscap [http://tahoe-
 lafs.org/buildbot/builders/Shawn%20jaunty%20amd64/builds/563/steps/test/logs/stdio
 on 'Shawn jaunty']:

 {{{
 Searching for foolscap==0.5.1
 Best match: foolscap 0.5.1
 Processing foolscap-0.5.1-py2.6.egg
 foolscap 0.5.1 is already the active version in easy-install.pth
 Installing flappclient script to support/bin
 Installing flogtool script to support/bin
 Installing flappserver script to support/bin

 Using /var/lib/buildbot/tahoe/mordsith/build/support/lib/python2.6/
 site-packages/foolscap-0.5.1-py2.6.egg
 [...]
 running trial
 [...]
 pkg_resources.VersionConflict: (foolscap 0.4.2 (/usr/local/lib/python2.6/
 dist-packages/foolscap-0.4.2-py2.6.egg),
 Requirement.parse('foolscap[secure_connections]>=0.5.1'))
 }}}

 So this is not specific to pycrypto or due to the use of a disjunctive
 requirement. I think that we should keep the pycrypto requirement as
 "pycrypto == 2.0.1, == 2.1, >= 2.3" for 1.8.0c3, since it at least fails
 with a message that could give the user a hint that they need to delete
 the pycrypto 2.2 installation.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1065#comment:8>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage