Changes between Initial Version and Version 1 of Ticket #2570


Ignore:
Timestamp:
2015-11-16T05:35:58Z (9 years ago)
Author:
nejucomo
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2570 – Description

    initial v1  
    1 On a debian system I'm unable to successfully run {{{pip install allmydata-tahoe}}} due to a compilation error while installing ``pyOpenSSL``. However, if I first run {{{pip install PyOpenSSL}}} and *then* {{{pip install allmydata-tahoe}}} then this succeeds.
     1On a debian system I'm unable to successfully run {{{pip install allmydata-tahoe}}} due to a compilation error while installing `pyOpenSSL`. However, if I first run {{{pip install PyOpenSSL}}} and *then* {{{pip install allmydata-tahoe}}} then this succeeds.
    22
    3 Notice how in the first case the package which fails to install is called ``pyOpenSSL`` but in the second sequence of commands, the package requested is ``PyOpenSSL`` with an initial capital ``P``. Is this the difference? Can we change the dependencies of tahoe-lafs to refer to the successfully installing pacakage?
     3Notice how in the first case the package which fails to install is called `pyOpenSSL` but in the second sequence of commands, the package requested is `PyOpenSSL` with an initial capital `P`. Is this the difference? Can we change the dependencies of tahoe-lafs to refer to the successfully installing pacakage?
    44
    5 Here's the first attempt to install ``allmydata-tahoe``:
     5Here's the first attempt to install `allmydata-tahoe`:
    66
    77{{{
    … …  
    8585}}}
    8686
    87 If I install ``PyOpenSSL`` (with a capital ``P``) directly first, then I *can* install ``allmydata-tahoe``, as seen here:
     87If I install `PyOpenSSL` (with a capital `P`) directly first, then I *can* install `allmydata-tahoe`, as seen here:
    8888
    8989{{{