Bug 500598 - gpart-debuginfo is empty
gpart-debuginfo is empty
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gpart (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: David Cantrell
Alexander Todorov
Depends On:
  Show dependency treegraph
Reported: 2009-05-13 08:11 EDT by Alexander Todorov
Modified: 2013-04-12 16:14 EDT (History)
0 users

See Also:
Fixed In Version: gpart-0.1h-5.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-11-26 02:52:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gpart.spec (1.88 KB, text/plain)
2009-05-29 20:02 EDT, David Cantrell
no flags Details
gpart-0.1h-cflags.patch (317 bytes, patch)
2009-05-29 20:03 EDT, David Cantrell
no flags Details | Diff

  None (edit)
Description Alexander Todorov 2009-05-13 08:11:01 EDT
Description of problem:
gpart-debuginfo is empty although gpart package contains ELF object

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpm -qpl gpart-debuginfo-0.1h-3.1.i386.rpm
Actual results:
empty package

Expected results:
package with useful debugging information

Additional info:
Comment 3 David Cantrell 2009-05-29 20:02:06 EDT
This is an easy fix.  Update the Makefile patch and fix up the spec file.  Attached to this bug are updated versions of those (for my own record keeping).

Here's my test build:


You can see the debuginfo package now contains things.
Comment 4 David Cantrell 2009-05-29 20:02:45 EDT
Created attachment 345967 [details]
Comment 5 David Cantrell 2009-05-29 20:03:07 EDT
Created attachment 345968 [details]
Comment 7 Alexander Todorov 2009-11-10 04:03:50 EST
Moving to VERIFIED

$ rpm -qpl gpart-debuginfo-0.1h-5.el5.i386.rpm 
Comment 9 errata-xmlrpc 2009-11-26 02:52:39 EST
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.


Note You need to log in before you can comment on or make changes to this bug.