Bug 701492 - upstream qpid does not package its SSL headers
Summary: upstream qpid does not package its SSL headers
Keywords:
Status: CLOSED DUPLICATE of bug 703563
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qpid-cpp
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Ted Ross
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks: 701495
TreeView+ depends on / blocked
 
Reported: 2011-05-03 01:28 UTC by Adam Stokes
Modified: 2016-04-26 15:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 701495 (view as bug list)
Environment:
Last Closed: 2011-10-18 13:57:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Adam Stokes 2011-05-03 01:28:50 UTC 
Description of problem:
Building RPM's should pull in qpid's ssl implementation, however, since its not packaged upstream it doesn't make it into our packages.

Version-Release number of selected component (if applicable):
qpid 0.x

How reproducible:
100%

Steps to Reproduce:
1. Install qpid-cpp-devel
2. Attempt to make use of qpid/sys/ssl/util.h
3. Realize there is no SSL headers for further development
  
Actual results:
no header files

Expected results:
upstream package all header files for future development against its product

Additional info:
Spoke with Ted Ross on this (who tracked down the missing headers upstream) and will get this pushed upstream for further review.
Comment 1 Ted Ross 2011-05-03 01:34:38 UTC 
Upstream issue: https://issues.apache.org/jira/browse/QPID-3240
Comment 2 Ted Ross 2011-08-15 17:35:20 UTC 
The fix for this will not arrive in time for the 8/15 deadline.  I've set the exception flag to '?' to consider this fix for inclusion in a later update.
Comment 3 Ted Ross 2011-10-18 13:57:14 UTC 
The fix for bz 703563 will make this fix unnecessary.

*** This bug has been marked as a duplicate of bug 703563 ***
Note You need to log in before you can comment on or make changes to this bug.