RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 714045 - New package: libreport
Summary: New package: libreport
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libreport
Version: 6.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 6.2
Assignee: Jiri Moskovcak
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 697494
TreeView+ depends on / blocked
 
Reported: 2011-06-17 08:38 UTC by Jiri Moskovcak
Modified: 2015-02-01 22:54 UTC (History)
11 users (show)

Fixed In Version: libreport-2.0.5-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 12:14:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1598 0 normal SHIPPED_LIVE abrt and libreport bug fix and enhancement update 2011-12-06 00:51:16 UTC

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
Note You need to log in before you can comment on or make changes to this bug.