Bug 1089090 - Nodejs010-c-ares provides libcares.so.2
Summary: Nodejs010-c-ares provides libcares.so.2
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: nodejs010
Version: nodejs010
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Tomas Hrcka
QA Contact: Miroslav Hradílek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-17 22:13 UTC by Timothy Williams
Modified: 2019-05-20 11:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-31 15:02:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Timothy Williams 2014-04-17 22:13:35 UTC
Description of problem:
The nodejs010-c-ares rpm provides libcares.so.2. SSSD also requires libcares.so.2. When SSSD is installed through yum, nodejs010-c-ares is also installed as a dependency because it provides libcares.so.2. However, SSSD will then be unable to start because it cannot use the libcares.so.2 file from RHSCL.

Version-Release number of selected component (if applicable):
-

How reproducible:
Always

Steps to Reproduce:
1. Add to a system the RHSCL repository and the standard rhel-server-rpms respository
2. Install SSSD
3. Attempt to start SSSD

Actual results:
nodejs010-c-ares is installed for its libcares.so.2. SSSD is unable to start because it cannot access RHSCL libcares.so.2

Expected results:
SSSD uses a different rpm (such as c-ares) as a dependency.

Additional info:

Comment 4 Chris Everest 2015-08-10 17:59:37 UTC
I'm experiencing this same issue.  Seem like the package should 'Require: c-ares' as this is clearly a hard runtime dependency.  I'm happy to provide any more information to get this resolved.  In the meantime, is it OK to ensure that c-ares is manually installed to prevent this problem?

Comment 7 Joe Orton 2017-03-31 15:02:02 UTC
In accordance with the Red Hat Software Collections Product Life Cycle, the support period for this collection has ended.

New bug fix, enhancement, and security errata updates, as well as technical support services will no longer be made available for this collection.

Customers are encouraged to upgrade to a later release.

Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/


Note You need to log in before you can comment on or make changes to this bug.