Bug 134952

Summary: update the nss_ldap version
Product: Red Hat Enterprise Linux 3 Reporter: Levente Farkas <lfarkas>
Component: nss_ldapAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED WONTFIX QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: shillman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 19:16:42 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:
Attachments:
Description Flags
the updated spec file
none
and the updated dnsconfig patch none

Description Levente Farkas 2004-10-07 14:37:46 UTC
Description of problem:
it'd be useful to update the nss_ldap to the latest version which do
NOT depend on db4

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Levente Farkas 2004-10-07 14:39:48 UTC
Created attachment 104894 [details]
the updated spec file

Comment 2 Levente Farkas 2004-10-07 14:41:04 UTC
Created attachment 104895 [details]
and the updated dnsconfig patch

at the same time it'd be useful to include some kind of doc about this feature
(dnsconfig) somewhere in nss_ldap!

Comment 4 RHEL Program Management 2007-10-19 19:16:42 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.