[tahoe-dev] [tahoe-lafs] #668: easy_install allmydata-tahoe is broken

tahoe-lafs trac at tahoe-lafs.org
Sun Jan 16 10:20:12 UTC 2011


#668: easy_install allmydata-tahoe is broken
---------------------------+------------------------------------------------
     Reporter:  francois   |       Owner:  zooko                           
         Type:  defect     |      Status:  assigned                        
     Priority:  major      |   Milestone:  soon                            
    Component:  packaging  |     Version:  1.3.0                           
   Resolution:             |    Keywords:  setuptools install ubuntu debian
Launchpad Bug:             |  
---------------------------+------------------------------------------------

Comment (by zooko):

 I'm very happy to report that since I updated {{{pycryptopp}}} to
 {{{v0.5.28}}}, that now {{{sudo easy_install allmydata-tahoe}}} works on
 my Mac OS X laptop even if I have none of the dependencies pre-installed
 [*].

 Now if only we had an automated test which would go red if {{{sudo
 easy_install allmydata-tahoe}}} were to ever ''stop'' working...

 (Probably it already worked before I updated {{{pycryptopp}}} ''if'' you
 were using {{{easy_install}}} as provided by {{{setuptools}}}, but if your
 {{{easy_install}}} is provided by {{{distribute}}} then you need [http
 ://tahoe-lafs.org/trac/pycryptopp/changeset/20110116042437-92b7f-
 da672fdb8119caea967d4f3270b4a36ecccfea59/trunk the workaround] in
 {{{pycryptopp-0.5.28}}} for
 [http://bitbucket.org/tarek/distribute/issue/55/revision-control-plugin-
 automatically-installed-as-a-build-dependency-is-not-present-when-another-
 build-dependency-is-being this distribute bug].)

 ([*] Except the {{{pycrypto}}} dependency doesn't work because
 http://pycrypto.org is unreachable (as it has been for days) but the PyPI
 record at http://pypi.python.org/pypi/pycrypto/2.3 shows
 http://www.pycrypto.org/files/pycrypto-2.3.tar.gz as the "Download URL" so
 {{{easy_install}}} always tries to download that file if it needs
 {{{pycrypto}}} and then aborts the Tahoe-LAFS build when it can't connect
 to pycrypto.org. The only work-around I can come up with for this at the
 moment is to add {{{--find-links=http://tahoe-lafs.org/source/tahoe-
 lafs/deps/tahoe-lafs-dep-sdists/}}} to your {{{easy_install}}} command-
 line.)

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


More information about the tahoe-dev mailing list