Bug 1130161

Summary: collectd-nut dependency error
Product: [Fedora] Fedora Reporter: Szombathelyi György <gyurco>
Component: collectdAssignee: Ruben Kerkhof <ruben>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: mail, mhlavink, ruben
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-14 13:12:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Szombathelyi György 2014-08-14 13:07:37 UTC
Description of problem:

collectd-nut-5.4.1-2.fc20 depends on libupsclient.so.1, but the current nut-client package ships libupsclient.so.2

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

How reproducible:

Steps to Reproduce:
1. yum update

Actual results:
Error: Package: collectd-nut-5.4.1-2.fc20.x86_64 (updates)
           Requires: libupsclient.so.1()(64bit)
           Removing: nut-client-2.6.5-15.fc20.x86_64 (@fedora)
           Updated By: nut-client-2.7.2-1.fc20.x86_64 (updates)

Expected results:
The update succeeds

Additional info:

Comment 1 Szombathelyi György 2014-08-14 13:08:33 UTC
Sorry, in the description: "but the current nut-client package ships libupsclient.so.4"

Comment 2 Michal Hlavinka 2014-08-14 13:12:58 UTC
This should be already fixed. The fix is in updates-testing repository now. Should get to (stable) updates repository soon.

Package collectd-5.4.1-3.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing collectd-5.4.1-3.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

*** This bug has been marked as a duplicate of bug 1123593 ***