I'm about to unmask openldap 2.4 series. It has been out long enough, other distros switched long ago, so it should be safe for us to do the same. To avoid the mess we had from 2.2 to 2.3, we need this: - Ebuild checking for 2.3 databases and warn user to export first - News item on frontpage to warn about rebuilding (failing pam may be a result for desktop profile users as ldap is a default flag there) - GLEP42 news item to warn about the same thing - Update OpenLDAP Guide if required Done so far is the ebuild internal check
Kerberos: knowing people mainly use ldap and kerberos together, please check for incompatibilites and required upgrade path infos
I've bee using 2.4 for few months, either as client or as server on many boxes and I had no problems (at least not with current in tree version 2.4.11)
Maybe this bug should be blocked by bug #233633?
Is there any work being done on this? I have unmasked 2.4 for myself, but still, it would be really good to have this.
Note that ruby-ldap-0.9.9 is needed since older versions don't compile against openldap 2.4.
I'm now using openldap 2.4.16 for few weeks and everythig is fine. I'm interested to see when this package will be unmasked. Btw, the procedure described in the ebuild is fine and comprehensive enough for admin sys. Cheers
Unmasked now. Have fun.
