Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1446479

Summary: Build riemann-c-client for RHV 4.1
Product: Red Hat Enterprise Virtualization Manager Reporter: Sandro Bonazzola <sbonazzo>
Component: riemann-c-clientAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED ERRATA QA Contact: Pavol Brilla <pbrilla>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: lsurette, lsvaty, mrunge, rbalakri, Rhev-m-bugs, rmeggins, sbonazzo, srevivo, ykaul
Target Milestone: ovirt-4.1.2Keywords: Rebase, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: riemann-c-client-1.6.1-4.el7 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-24 11:26:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1446472    

Description Sandro Bonazzola 2017-04-28 07:38:52 UTC
Description of problem:
riemann-c-client is a dependency for collectd 5.7.1.
CBS build: http://cbs.centos.org/koji/buildinfo?buildID=15251

Comment 3 Yaniv Kaul 2017-05-10 14:33:21 UTC
I wonder if we can improve the dependencies and remove some of the bloat by working on better packaging...

Comment 4 Sandro Bonazzola 2017-05-10 14:42:56 UTC
(In reply to Yaniv Kaul from comment #3)
> I wonder if we can improve the dependencies and remove some of the bloat by
> working on better packaging...

Not sure about what's the needed info.
riemann-c-client is needed for Riemann output plugin for collectd which is included in 5.7.1 so it's needed as build requirement and at runtime.
The package is shared with RDO project and the packaging adhere to fedora packaging guidleines as far as I can tell.

Comment 7 errata-xmlrpc 2017-05-24 11:26:35 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.

https://access.redhat.com/errata/RHEA-2017:1286