Bug 9794 - drakconf is unable to setup a LDAP authentication
Summary: drakconf is unable to setup a LDAP authentication
Status: RESOLVED DUPLICATE of bug 9769
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-04-19 01:58 CEST by Bruno Cornec
Modified: 2013-04-19 18:43 CEST (History)
2 users (show)

See Also:
Source RPM: drakxtools
CVE:
Status comment:


Attachments

Description Bruno Cornec 2013-04-19 01:58:32 CEST
Description of problem:

drakconf is unable to setup a LDAP authentication. When trying to do so, it tries to install some packages for ldap support. Among them it tries to install pam-ldap which is replaced by nss-pam-ldapd as it seems. So this install fails, and then nothing is performed with regards to the installation of the other needed packages, nor the conf. Even installing nss-pam-ldapd manually doesn't help as it doesn't provide pam_ldap.

Version-Release number of selected component (if applicable):
drakconf-12.37-1.mga3

How reproducible:
Each time

Steps to Reproduce:
1. launch drakconf
2. Go inteo System/Authentication
3. Select LDAP, give the 2 params asked
4. drakconf tries to install the missing packages and fails.


Reproducible: 

Steps to Reproduce:
Sander Lepik 2013-04-19 09:05:52 CEST

CC: (none) => guillomovitch, sander.lepik

Guillaume Rousse 2013-04-19 11:39:41 CEST

CC: guillomovitch => (none)

Comment 1 Manuel Hiebel 2013-04-19 18:28:50 CEST
rpm -q drakxtools ? it should be fixed with the last one

Keywords: (none) => NEEDINFO
Source RPM: drakconf-12.37-1.mga3.src.rpm => drakxtools

Comment 2 Thierry Vignaud 2013-04-19 18:43:46 CEST
I just need to release a new drakxtools

*** This bug has been marked as a duplicate of bug 9769 ***

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => DUPLICATE


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