[tahoe-lafs-trac-stream] [tahoe-lafs] #1717: 'sudo make install' doesn't work

[tahoe-lafs]

#1717: 'sudo make install' doesn't work
----------------------------+--------------------------------
     Reporter:  davidsarah  |      Owner:  warner
         Type:  defect      |     Status:  new
     Priority:  major       |  Milestone:  undecided
    Component:  packaging   |    Version:  1.9.1
   Resolution:              |   Keywords:  setuptools install
Launchpad Bug:              |
----------------------------+--------------------------------

Comment (by davidsarah):

 I asked:
 > Does this workaround [{{{sudo python setup.py install}}}] work on your
 system?

 erpo41 replied:
 > Thanks for the suggestion! That command did install the {{{tahoe}}}
 executable in {{{/usr/local/bin/tahoe}}}, but when I try to run it I get
 this:
 {{{
 eric at io:/srv/volunteergrid2$ tahoe
 Traceback (most recent call last):
   File "/usr/local/bin/tahoe", line 6, in <module>
     from pkg_resources import load_entry_point
   File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 2655,
 in <module>
     working_set.require(__requires__)
   File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 648, in
 require
     needed = self.resolve(parse_requirements(requirements))
   File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 546, in
 resolve
     raise DistributionNotFound(req)
 pkg_resources.DistributionNotFound: pycryptopp>=0.5.20
 }}}

 > I'm guessing that tahoe depends on a lot of external libraries that
 weren't installed along with the executable when I ran that command.

 That's correct.

 > As a workaround, I copied the {{{/home/volunteergrid2/allmydata-1.9.1}}}
 directory to {{{/home/eric}}}, reset the directory ownership, and
 symlinked the executable into {{{/home/eric/bin}}}. Now I have tahoe for
 my user account, which is all I really needed anyway.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1717#comment:3>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage