Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 88379 - No glibc-debuginfo package
Summary: No glibc-debuginfo package
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: distribution
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-09 16:19 UTC by Patrick J. LoPresti
Modified: 2014-03-17 02:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-03-02 18:45:56 UTC

Attachments (Terms of Use)

Description Patrick J. LoPresti 2003-04-09 16:19:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
When I run "rpm -qip glibc-debug-2.3.2-11.9.i386.rpm", the description includes
this sentence:

  "If you want to see glibc source files during debugging, you should
install glibc-debuginfo package."

But as far as I can see, there is no glibc-debuginfo package anywhere on any
RedHat 9 media.  (Nothing I can download, anyway.)

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

How reproducible:

Steps to Reproduce:
1. Run "rpm -i" on glibc-debug package.
2. Read description carefully.
3. Look for glibc-debuginfo package in vain.

Actual Results:  I couldn't find glibc-debuginfo.

Expected Results:  I should be able to find glibc-debuginfo.  Or the Description
in glibc-debug should be different...

Additional info:

Comment 1 Ulrich Drepper 2003-10-03 21:00:58 UTC
That's not a glibc problem.  It a general decision to be made for the distribution.

Comment 2 Bill Nottingham 2005-03-02 18:45:56 UTC
Debuginfo is shipped in Fedora Core, albeit not on the CDs/DVDs.

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