Bug 702060

Summary:	decouple rampart dependency from wso2-wsf-cpp
Product:	Red Hat Enterprise MRG	Reporter:	Pete MacKinnon <pmackinn>
Component:	condor-aviary	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	Martin Kudlej <mkudlej>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0	CC:	matt, mkudlej
Target Milestone:	2.1
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	wso2-wsf-cpp-2.1.0-4	Doc Type:	Bug Fix
Doc Text:	The wso2-wsf-cpp package unnecessarily depended on the wso2-rampart package. This update removes this dependency so that the wso2-rampart package is no longer needed for Aviary functionality. Note that the wso2-rampart package can be safely removed from the system.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-23 17:26:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	743350

Description Pete MacKinnon 2011-05-04 16:44:21 UTC

Currently there is a non-obvious dependency between wso2-wsf-cpp and wso2-rampart packages.

$ rpm -qR wso2-wsf-cpp
<snip>
wso2-axis2 = 2.1.0-2.el6
wso2-rampart = 2.1.0-2.el6

This traces back to:

$ ldd /usr/lib/libwso2_wsf_security.so
<snip>
	librampart.so.0 => /usr/lib/librampart.so.0 (0x00110000)

We need to investigate the nature of this lib dependency.

Comment 1 Robert Rati 2011-08-16 16:54:42 UTC

Created a new package which is only built on fedora by default:
wso2-wsf-cpp-security

This package contains the libwso2_wsf_security.so library, and depends on rampart.

Comment 2 Robert Rati 2011-10-04 17:16:30 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
C: The wso2-wsf-cpp package had a dependency on the wso2-rampart package even though that functionality was not needed by aviary.
C: The wso2-rampart package would be installed if wso2-wsf-cpp was installed.
F: Moved the functionality needing the rampart package to a sub-package.
R: The wso2-rampart packages are no longer needed for aviary functionality.

Comment 3 Robert Rati 2011-10-04 18:10:01 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1,4 @@
 C: The wso2-wsf-cpp package had a dependency on the wso2-rampart package even though that functionality was not needed by aviary.
 C: The wso2-rampart package would be installed if wso2-wsf-cpp was installed.
 F: Moved the functionality needing the rampart package to a sub-package.
-R: The wso2-rampart packages are no longer needed for aviary functionality.+R: The wso2-rampart packages are no longer needed for aviary functionality.  The wso2-rampart package can safely be removed.

Comment 5 Martin Kudlej 2011-10-18 12:44:53 UTC

Tested on RHEL5.8/RHEL6.1 with 

wso2-wsf-cpp-debuginfo-2.1.0-5
wso2-wsf-cpp-2.1.0-5
wso2-wsf-cpp-devel-2.1.0-5
wso2-axis2-2.1.0-5
wso2-axis2-devel-2.1.0-5

and there is no dependency on rampart. -> VERIFIED

Comment 6 Douglas Silas 2011-11-17 12:46:50 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1,3 @@
-C: The wso2-wsf-cpp package had a dependency on the wso2-rampart package even though that functionality was not needed by aviary.
+The wso2-wsf-cpp package unnecessarily depended on the wso2-rampart package. This update removes this dependency so that the wso2-rampart package is no longer needed for Aviary functionality.
-C: The wso2-rampart package would be installed if wso2-wsf-cpp was installed.
+
-F: Moved the functionality needing the rampart package to a sub-package.
+Note that the wso2-rampart package can be safely removed from the system.-R: The wso2-rampart packages are no longer needed for aviary functionality.  The wso2-rampart package can safely be removed.

Comment 7 errata-xmlrpc 2012-01-23 17:26:34 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0045.html