Bug 623062

Summary: [RFE] Log dependency versions too
Product: [Fedora] Fedora Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: anton, dfediuck, dvlasenk, iprikryl, jmoskovc, kklic, mads, mtoman, npajkovs, nphilipp
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-27 16:54:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 538278    

Description Nicolas Mailhot 2010-08-11 08:33:21 UTC
Description of problem:

Abrt currently logs the version of the package that crashed. However, it does not log the versions of all the packages the crasher depended on (even though they are used via debuginfos to create backtraces, and the bug can actually be in one of the libs used).

On systems that sync with repositories whith a high churn (rawhide, pre-alpha/beta repositories/tags), or on systems that cherry-pick updates (Fedora systems manually updated from koji, RHEL systems used by conservative customers that filter heavily Red Hat-provided updates) it is far from trivial to deduce the exact dependency versions from the version of the crashing package. (Sometimes people even selectively downgrade components to help third-party software installation)

Abrt should collect this info when a crash is detected (it's just a rpm -q --whaprovides library-listed-in-backtrace) and add it to the collected info by default (not do a full sosreport).


Version-Release number of selected component (if applicable):
abrt-1.1.10-4.fc14

Comment 1 Jiri Moskovcak 2011-03-27 16:54:17 UTC

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