Opened at 2009-05-12T01:56:52Z

Closed at 2011-08-16T04:24:05Z

#702 closed defect (invalid)

Installation documentation incomplete for Ubuntu Jaunty 9.04 SE.

Reported by: nejucomo Owned by: nejucomo
Priority: minor Milestone: undecided
Component: packaging Version: 1.4.1
Keywords: debian ubuntu docs zfec openssl Cc:
Launchpad Bug:

Description

Initially running "python ./setup.py build" failed on this system because I neglected to install build-essential as mentioned in the DownloadDebianPackages page.

However, after installing build-essential, "python ./setup.py build" failed due to missing SSL headers. [Log forthcoming.]

I attempted to install all of the named debian packages in the list mentioned in DownloadDebianPackages but python-zfec failed.

Finally, I searched for the required SSL package, which was unexpectedly tricky, because the package does not include "openssl" in its name. Eventually used apt-file to search for a specific header file mentioned in the build process as missing to discover the dependency is called "libssl-dev".

Include the "libssl-dev" dependency on the DownloadDebianPackages page.

Attachments (3)

tahoe_build_failure_when_libssl-dev_missing.log​ (32.1 KB) - added by nejucomo at 2009-05-12T01:57:39Z.
What a build failure looks like when SSL headers are missing (not completely obvious).
tahoe_debian_dependencies_not_found_on_jaunty.log​ (284 bytes) - added by nejucomo at 2009-05-12T01:58:05Z.
python-zfec is not found on Ubuntu Jaunty 9.04 SE
tahoe_openssl_dependency_hard_to_find.log​ (75 bytes) - added by nejucomo at 2009-05-12T01:58:30Z.
The command which finally discovered the correct dependency (non-obvious).

Download all attachments as: .zip

Change History (8)

Changed at 2009-05-12T01:57:39Z by nejucomo

What a build failure looks like when SSL headers are missing (not completely obvious).

Changed at 2009-05-12T01:58:05Z by nejucomo

python-zfec is not found on Ubuntu Jaunty 9.04 SE

Changed at 2009-05-12T01:58:30Z by nejucomo

The command which finally discovered the correct dependency (non-obvious).

comment:1 Changed at 2009-05-12T02:13:42Z by zooko

  • Owner changed from somebody to nejucomo

So, let's see. What does it take to close this ticket? Did you already edit the DownloadDebianPackages wiki page to include libssl-dev? Well, actually if you are installing Debian packages, then why not install python-openssl instead -- then it won't try to build anything that requires ssl headers.

As I mentioned in #701, the original error here is that python ./setup.py build didn't install all the dependencies from binary eggs, as intended. But it would also be good for people who don't, for whatever, reason, get a binary egg to also have an easy time building pyopenssl from source. Should this ticket be retargeted to something like "When pyopenssl binary eggs can't be installed for the build platform, building pyopenssl from source is unnecessarily hard"?

I would like to know what would be necessary to close this ticket as "fixed".

comment:2 Changed at 2009-06-25T15:59:56Z by zooko

  • Keywords packaging debian added

comment:3 Changed at 2009-12-04T05:17:43Z by davidsarah

  • Keywords ubuntu docs zfec openssl added

comment:4 Changed at 2009-12-04T05:18:00Z by davidsarah

  • Component changed from documentation to packaging
  • Keywords packaging removed

comment:5 Changed at 2011-08-16T04:24:05Z by davidsarah

  • Resolution set to invalid
  • Status changed from new to closed

The python-pyopenssl dependency should be sufficient; if not then reopen.

Note: See TracTickets for help on using tickets.