Bug 500610

Summary: mktemp-debuginfo is empty
Product: Red Hat Enterprise Linux 5 Reporter: Alexander Todorov <atodorov>
Component: mktempAssignee: Than Ngo <than>
Status: CLOSED ERRATA QA Contact: Iveta Wiedermann <isenfeld>
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: isenfeld, pknirsch, pkovar, twoerner, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: mktemp-1.5-24.el5 Doc Type: Bug Fix
Doc Text:
Prior to this update, the mktemp-debuginfo package contained no debugging information. With this update, the mktemp-debuginfo package now contains debugging information, as expected.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-09 09:19:16 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:

Description Alexander Todorov 2009-05-13 12:52:35 UTC 
Description of problem:
mktemp-debuginfo is empty although mktemp package contains ELF objects.

Version-Release number of selected component (if applicable):
mktemp-debuginfo-1.5-23.2.2.i386.rpm

How reproducible:
always

Steps to Reproduce:
1. rpm -qpl mktemp-debuginfo-1.5-23.2.2.i386.rpm
2.
3.
  
Actual results:
empty package

Expected results:
package contains debugging information

Additional info:
Comment 8 Than Ngo 2011-08-31 16:05:51 UTC 
it's fixed in mktemp-1.5-24.el5.
Comment 10 Petr Kovar 2011-09-06 14:38:19 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Prior to this update, the mktemp-debuginfo package contained no debugging information. With this update, the mktemp-debuginfo package now contains debugging information, as expected.
Comment 12 errata-xmlrpc 2011-11-09 09:19:16 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-1443.html