[tahoe-dev] [tahoe-lafs] #802: MacOS X Test Failures

[tahoe-lafs]

#802: MacOS X Test Failures
---------------------+------------------------------------------------------
 Reporter:  bewst    |           Owner:  bewst   
     Type:  defect   |          Status:  assigned
 Priority:  major    |       Milestone:  0.3.0   
Component:  unknown  |         Version:  1.5.0   
 Keywords:           |   Launchpad_bug:          
---------------------+------------------------------------------------------
Changes (by zooko):

  * milestone:  undecided => 0.3.0


Comment:

 Hm.  I hate to impose that constraint on platforms where they don't need
 the newer pycryptopp.  pycryptopp-0.5.17 is necessary for Mac OS 10.6 and
 for Fedora amd64, and it may or may not be needed for other Linux amd64.
 pycryptopp-0.5.15 is necessary for AthlonXP and old-style Celeron.

 Also note that the latest pycryptopp-0.5.17 won't build properly with the
 brand new Ubuntu Karmic: https://bugs.launchpad.net/ubuntu/+bug/461303 .

 Anyway, maybe we should increase that requirement, or do so on the known-
 to-be-affected platforms.  I'd like to put it off and think about it for a
 bit first, though.  For one thing, we have a recurring problem with people
 being unable to install Tahoe-LAFS because they can't install pycryptopp.
 One of the main ways that I intend to address that problem is for
 buildslaves to build binary libraries ("eggs") of pycryptopp and upload
 them to here: http://allmydata.org/source/tahoe/deps/tahoe-dep-eggs .  The
 idea is that the Tahoe-LAFS build system (using {{{setuptools}}}) will
 automatically download the appropriate binary egg from that list for the
 platform on which it is building.

 That mechanism basically works, but we haven't set up buildslaves for all
 the right platforms and all of the dependencies and tested it out.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/802#comment:7>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid