Bug 490106 - no ldapmail support compiled in
no ldapmail support compiled in
Product: Fedora
Classification: Fedora
Component: quota (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Ondrej Vasik
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-03-13 05:54 EDT by Johannes Russek
Modified: 2009-03-16 15:43 EDT (History)
2 users (show)

See Also:
Fixed In Version: 3.16-7.fc10
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-13 08:20:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Johannes Russek 2009-03-13 05:54:01 EDT
Description of problem:

quota has the option --enable-ldapmail to enable LDAP_MAIL options in the /etc/warnquota.conf to search for email adresses of users in ldap.
This option is set to --enable-ldapmail=try, but since openldap-devel is missing in the buildrequire option, configure will fail to find ldap toolkit and not compile ldap support in.
The --enable-ldapmail seems to have been added in FC4, but when packages got compiled with mock, ldap support silently disappeared..

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

How reproducible:

Steps to Reproduce:
put LDAP_MAIL = true in /etc/warnquota.conf and run warnquota
Actual results:
you'll see the following messages:
warnquota: Error in config file (line 70), ignoring
where the line numbers is the line with any LDAP_* option 

Additional info:
configure also supports --enable-ldapmail=yes and if openldap-devel is not available, will fail. this is probably the better option.
also simply adding openldap-devel to BuildRequire will fix this :)

regards, Johannes
Comment 1 Johannes Russek 2009-03-13 06:38:07 EDT
So, after patching and recompiling the spec myself, i can add the following information:

openldap and openssl are both needed (-devel for BuildRequire of course), also the openldap lib that comes with fedora will generate the following output:

warnquota: LDAP library version >= 2.3 detected. Please use LDAP_URI instead of hostname and port.

so the example in /etc/warnquota.conf would have to be adjusted accordingly.
Comment 2 Ondrej Vasik 2009-03-13 06:58:07 EDT
Thanks for report, however, it was not added in FC4 (actually I added --enable-ldapmail=try in F-9) - that bug report was just accidently closed with no change in spec file. You are right with the missing buildrequires, will fix that...
Comment 3 Ondrej Vasik 2009-03-13 07:22:41 EDT
Built in rawhide as quota-3.17-3.fc11 with openldap-devel (and temporarily openssl-devel - as openldap maintainer said nss patch review is in progress - in quota we tried to move from openssl to nss and now ldapmail support introduces openssl-devel dependency again ). Are you ok to close that bugzilla as RAWHIDE? (as I don't want to make F-10 update just to enable ldap support properly - it will of course be included in next bugfix F-10 update)
Comment 4 Johannes Russek 2009-03-13 07:53:04 EDT
Alright, that's fine with me.
Removing LDAP_HOST and LDAP_PORT and using LDAP_URI in the example warnquota.conf would be nice too.
Thx a bunch,
Comment 5 Ondrej Vasik 2009-03-13 08:20:22 EDT
Ok, closing RAWHIDE...

At the moment in warnquota.conf example is:
# If you have at least LDAP 2.3 installed, you can use LDAP_URI
# LDAP_URI = ldaps://my.server:389
# Otherwise you can specify LDAP_HOST and LDAP_PORT
# LDAP_HOST = ldap
# LDAP_PORT = 389

Which seems ok to me (as someone could still have LDAP 2.2 - where you have to use LDAP_HOST and LDAP_PORT)- maybe s/you can/you should/ would be more appropriate. Will probably do that and propose one change to that example anyway - as "# LDAP_MAIL = false # or false if you don't want to use it" is very strange comment...
Comment 6 Fedora Update System 2009-03-16 15:43:05 EDT
quota-3.16-7.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.

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