Opened at 2010-04-03T17:34:46Z
Closed at 2011-01-17T07:43:19Z
#1014 closed defect (fixed)
provide binary .egg's for pyOpenSSL for all supported platforms and versions of Python
Reported by: | nejucomo | Owned by: | nejucomo |
---|---|---|---|
Priority: | major | Milestone: | soon (release n/a) |
Component: | packaging | Version: | 1.6.1 |
Keywords: | binaries openssl debian install docs | Cc: | |
Launchpad Bug: |
Description
When following the instructions http://allmydata.org/trac/tahoe-lafs/attachment/ticket/1013/ on a minimal debian lenny (5.04) system, python ./setup.py build fails to build pycryptopp with many symbol resolution errors:
src/crypto/crypto.c:806: error: `crypto_NetscapeSPKI_New' undeclared (first use in this function) src/crypto/crypto.c:817: error: `X509_FILETYPE_PEM' undeclared (first use in this function)
Installing libssl with development headers solves that problem, so this is another undocumented dependency.
Attachments (2)
Change History (10)
Changed at 2010-04-03T17:35:10Z by nejucomo
comment:1 Changed at 2010-04-03T20:19:55Z by zooko
- Summary changed from libssl install dependency not documented. to provide binary .egg's for pyOpenSSL for linux-{i386,amd64}-py2.{5,6}-ucs4
The part of this ticket that is about documenting the build of pyOpenSSL from source is now #1015. The remainder of this ticket is about the fact that there was not a binary egg of pyOpenSSL for your platform. What CPU architecture are you using?
comment:2 Changed at 2010-04-03T20:20:05Z by zooko
- Owner changed from somebody to nejucomo
comment:3 Changed at 2010-04-04T22:39:38Z by davidsarah
- Component changed from documentation to packaging
- Keywords openssl debian install docs added
comment:4 Changed at 2010-10-31T06:14:14Z by zooko
- Keywords binaries added
- Milestone changed from undecided to 1.8.1
Since the newest version of pyOpenSSL listed on http://launchpad.net/pyopenssl at the moment is 0.11a2, then we need to build bdist_egg's of pyOpenSSL 0.11a2 for all platforms which we intend for people to be able to install Tahoe-LAFS v1.8.1 without having a C compiler and Python headers installed. (Note that the upstream maintainers of pyOpenSSL might be willing to provide binaries if we ask nicely: https://bugs.launchpad.net/pyopenssl/+bug/238658 .)
Sadly, if we do all the work to build and host such binary eggs, and then a new version of pyOpenSSL gets uploaded to !PyPI or launchpad or in source form only, then our build scripts will immediately start refusing to use the pyOpenSSL 0.11a2 binaries that we built. Fixing this so that our build scripts would continue to use the pyOpenSSL 0.11a2 binaries (or even good old pyOpenSSL 0.10 binaries) even if a newer version of pyOpenSSL is known to them is the subject of #1233.
comment:5 Changed at 2010-10-31T06:14:36Z by zooko
- Summary changed from provide binary .egg's for pyOpenSSL for linux-{i386,amd64}-py2.{5,6}-ucs4 to provide binary .egg's for pyOpenSSL for all supported platforms and versions of Python
comment:6 Changed at 2010-10-31T06:19:46Z by zooko
comment:7 Changed at 2011-01-06T21:21:44Z by warner
- Milestone changed from 1.8.1 to soon (release n/a)
comment:8 Changed at 2011-01-17T07:43:19Z by zooko
- Resolution set to fixed
- Status changed from new to closed
We now host binary eggs of pyOpenSSL for many fine platforms. See http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html for details.
Build output showing the errors when libssl is not installed.