Bug 714045

Summary:	New package: libreport
Product:	Red Hat Enterprise Linux 6	Reporter:	Jiri Moskovcak <jmoskovc>
Component:	libreport	Assignee:	Jiri Moskovcak <jmoskovc>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2	CC:	astokes, atodorov, dcantrell, dfediuck, dkutalek, dwalsh, mmalik, mnowak, notting, rbiba, syeghiay
Target Milestone:	rc
Target Release:	6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libreport-2.0.5-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 12:14:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	697494

Description Jiri Moskovcak 2011-06-17 08:38:49 UTC

Please consider accepting a new package libreport into RHEL 6.2. libreport is a generic library for reporting various problems to a different bug tracking systems (including our RH Support Portal).

It is required by ABRT 2 (rebase to ABRT2: bug 697494).

It is a part of Fedora:
https://admin.fedoraproject.org/pkgdb/acls/name/libreport

Comment 1 Bill Nottingham 2011-06-17 14:44:34 UTC

Are we intending to port sosreport, anaconda, setroubleshoot, etc. to it in 6.2?

Comment 3 David Cantrell 2011-06-17 15:00:31 UTC

(In reply to comment #1)
> Are we intending to port sosreport, anaconda, setroubleshoot, etc. to it in
> 6.2?

Based on the Tech Talk that I went to, there's no porting that we have to be concerned with.  libreport is API-compatible with what we were doing.  So long as the libreport RPM does a provide Obsoletes and Provides and is API-compatible with the previous report, then no report using software will need to change.

Comment 4 Jiri Moskovcak 2011-06-22 13:22:27 UTC

(In reply to comment #3)
> (In reply to comment #1)
> > Are we intending to port sosreport, anaconda, setroubleshoot, etc. to it in
> > 6.2?
> 
> Based on the Tech Talk that I went to, there's no porting that we have to be
> concerned with.  libreport is API-compatible with what we were doing.  So long
> as the libreport RPM does a provide Obsoletes and Provides and is
> API-compatible with the previous report, then no report using software will
> need to change.

Yes, libreport is API compatible with report. It will just need testing to make sure everything works as with the old report.

Comment 13 errata-xmlrpc 2011-12-06 12:14:07 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/RHBA-2011-1598.html