[tahoe-dev] [tahoe-lafs] #804: Cannot Install,

[tahoe-lafs]

#804: Cannot Install,
-------------------------------+--------------------------------------------
     Reporter:  arch_o_median  |       Owner:  zooko             
         Type:  defect         |      Status:  assigned          
     Priority:  minor          |   Milestone:  undecided         
    Component:  packaging      |     Version:  1.5.0             
   Resolution:                 |    Keywords:  install dependency
Launchpad_bug:                 |  
-------------------------------+--------------------------------------------
Changes (by zooko):

  * owner:  arch_o_median => zooko
  * status:  new => assigned


Comment:

 Okay I'm changing this ticket to say that we should take strategy (a) from
 comment:5 -- make binary .egg's of pycryptopp be installed for supported
 systems. arc's and imhavoc's systems are both amd64 with UCS4, and we have
 a pycryptopp buildbot that fits that description: http://allmydata.org
 /buildbot-pycryptopp/builders/linux-amd64-ubuntu-karmic-yukyuk . So to
 close this ticket, configure that buildbot to generate binary eggs and
 upload them to the tahoe-deps repository.  (Then check if the builds start
 working for arc and imhavoc.)  Oh, but arc was using Python 2.5 and
 imhavoc was using Python 2.6.  Actually I think arc has subsequently
 upgraded his Ubuntu to Karmic so he has 2.6 as well.  At least for now I'm
 defining this ticket as "provide binary .egg's for pycryptopp for linux-
 amd64-py2.6-ucs4".

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