Bug 500414 - RFE: produce a list of empty debuginfo rpms
Summary: RFE: produce a list of empty debuginfo rpms
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: releng
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Dennis Gregorovic
QA Contact: Alexander Todorov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-12 15:42 UTC by Alexander Todorov
Modified: 2009-09-02 12:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-02 12:02:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2009:1400 0 normal SHIPPED_LIVE redhat-release bug fix and enhancement update 2009-09-01 12:04:54 UTC

Description Alexander Todorov 2009-05-12 15:42:11 UTC 
Description of problem:
A simple rpm -qpl *.rpm shows 30 empty debuginfo packages in the latest RHEL nightly build. 

Can you add a simple check to distill that will identify the empty debuginfo packages. It can also check binary and source rpms as well. 

The list will be passed on to QA to identify incorrectly built packages.
Comment 1 Alexander Todorov 2009-05-12 15:43:47 UTC 
FYI: there's the same request for rpmdiff, see bug #249746 but some packages may never be on the approved list (or update every few years) and the problems may go unnoticed for quite long time.
Comment 2 Dennis Gregorovic 2009-05-13 12:13:40 UTC 
Sanity check added.
Comment 7 errata-xmlrpc 2009-09-02 12:02:07 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1400.html
Note You need to log in before you can comment on or make changes to this bug.