'crypto for PB is not available' error from bin/tahoe on Fedora due to failure to find libcrypto.so.1.0.0; goes away after 'make clean' and second build

[davidsarah]

(16:00:04) tcatm: hey. I have some trouble running tahoe-lafs on fedora: exceptions.RuntimeError?: crypto for PB is not available, try importing foolscap.crypto and see what happens

(16:10:19) davidsarah: tcatm: is that error from running 'setup.py build', or 'bin/tahoe', or using an operating system package of tahoe?

(16:11:11) tcatm: bin/tahoe start ... using the latest tarball from the download page

(16:12:48) davidsarah: which version of python?

(16:12:56) tcatm: 2.7

(16:14:59) davidsarah: please tell me the output from: PYTHONPATH=pwd/support/lib/python2.7/site-packages python -c "import foolscap.crypto; print foolscap.crypto"

(16:16:16) tcatm: <module 'foolscap.crypto' from '/usr/lib/python2.7/site-packages/foolscap/crypto.pyc'>

(16:16:56) davidsarah: what about: bin/tahoe --version-and-path

see paste.txt​

(16:20:11) davidsarah: thanks

(16:21:23) davidsarah: this is the problem:

(16:21:23) davidsarah: pyOpenSSL: None [(<type 'exceptions.ImportError?'>, 'libcrypto.so.1.0.0: cannot open shared object file: No such file or directory', ('/home/tahoe/allmydata-tahoe-1.9.0/support/lib/python2.7/site-packages/pyOpenSSL-0.13-py2.7-linux-x86_64.egg/OpenSSL/init.py', 36, '<module>', 'from OpenSSL import crypto'))] (None),

(16:22:22) davidsarah: it appears that pyOpenSSL can't find the OpenSSL shared lib it is linked against

(16:22:33) davidsarah: I've seen that problem before recently. zooko?

(16:24:09) davidsarah: if there is an operating system package of pyOpenSSL for fedora, installing that (and doing 'python setup.py build' again) would probably fix it

(16:24:42) davidsarah: but we should try to understand why the pyOpenSSL egg it found by default didn't work

(16:25:30) davidsarah: can you do 'make clean' and then paste the full output of 'python setup.py build'?

(16:25:52) tcatm: pyOpenSSL is installed, but I only got a libcrypto.so

(16:26:01) davidsarah: ah

(16:26:54) davidsarah: if you symlink 'libcrypto.so.1.0.0' in the same directory to 'libcrypto.so', does it work then?

(16:27:36) tcatm: sounds like that could break easily on the next upgrade

(16:27:59) davidsarah: it could, but I'm just trying to verify a hypothesis for the cause of the error

(16:28:40) tcatm: hrm, make clean and running setup.py build seemed to have fixed the problem. strange :)

(16:28:47) davidsarah: sigh

(16:28:52) davidsarah: that is annoying

(16:29:23) tcatm: yep. thanks for helping, though :)

(16:29:35) davidsarah: I will file a ticket anyway. thanks for reporting the problem

(16:31:12) davidsarah: mind if I include your paste above? I don't think it has any sensitive paths

(16:32:19) tcatm: no problem. I've already checked it for sensitive information

(16:34:52) davidsarah: which version of Fedora?

(16:40:25) tcatm: 14

[davidsarah]

output of bin/tahoe --version-and-path

[davidsarah]

reformat description

[zooko]

This is not a critical problem, but if there is an easy way to fix it for Tahoe-LAFS v1.9.1, I would be willing to do a little work on that.

[davidsarah]

This seems like a bug in pyOpenSSL's and/or OpenSSL's packaging or build process, not Tahoe-LAFS. Zooko, will you look-for-or-file a pyOpenSSL ticket?

[davidsarah]

Well, I suppose Tahoe-LAFS could work around it by building pyOpenSSL twice, but yuck (and I don't know how to force setuptools to do that).

[zooko]

Okay I opened a bug report at ​https://bugs.launchpad.net/pyopenssl/+bug/909608 . I'm going to close this ticket as wontfix.