Bug 186947 - Backported glibc fixes for RHEL4 glibc
Backported glibc fixes for RHEL4 glibc
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: glibc (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
Blocks: 181409
  Show dependency treegraph
Reported: 2006-03-27 11:58 EST by Jakub Jelinek
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2006-0510
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-10 17:35:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0510 normal SHIPPED_LIVE glibc bug fix update 2006-08-09 00:00:00 EDT

  None (edit)
Description Jakub Jelinek 2006-03-27 11:58:12 EST
Similarly to what we have done in #171238 for RHEL4 U3, we want to go again
through the safe self-contained bugfixes from glibc trunk and what is easily
and safely backportable add into RHEL4 U3 glibc.
We have already identified some fixes that were added to the FC4 glibc errata
released today and there are others that have been added since the time FC4
glibc errata was prepared.
Comment 4 Bob Johnson 2006-04-11 13:08:38 EDT
This issue is on Red Hat Engineering's list of planned work items 
for the upcoming Red Hat Enterprise Linux 4.4 release.  Engineering 
resources have been assigned and barring unforeseen circumstances, Red 
Hat intends to include this item in the 4.4 release.
Comment 9 Red Hat Bugzilla 2006-08-10 17:35:09 EDT
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 the 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.