his is the first testing call for OpenLDAP 2.4.59. Depending on the results, this may be the only testing call.
Generally, get the code for RE24:
Extract, configure, and build.
Execute the test suite (via make test) after it is built. Optionally, cd tests && make its to run through the regression suite.
Thanks!
OpenLDAP 2.4.59 Engineering Fixed libldap TLSv1.3 cipher suites with OpenSSL 1.1.1 (ITS#9521) Fixed libldap double free of LDAP_OPT_DEFBASE (ITS#9530) Fixed slapd syncrepl handling of add+delete on single value attr (ITS#9295) Fixed slapd-mdb cursor init check (ITS#9526) Fixed slapd-mdb deletion of context entry (ITS#9531) Fixed slapo-pcache locking during expiration (ITS#9529) Contrib Fixed slapo-autogroup to not thrash thead context (ITS#9494) Documentation ldap_modify(3) - Delete non-existent mod_next parameter (ITS#9559)
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Am 28.05.21 um 23:36 schrieb Quanah Gibson-Mount:
his is the first testing call for OpenLDAP 2.4.59. Depending on the results, this may be the only testing call.
build & make test run without problems on Debian 10
I noticed some suggestions from Debian lintian (but they do not seem to be new)
- spelling-error-in-binary: databse database - spelling-error-in-binary: everytime every time - spelling-error-in-manpage: allow to allow one to
Andreas
A. Schulze wrote:
Am 28.05.21 um 23:36 schrieb Quanah Gibson-Mount:
his is the first testing call for OpenLDAP 2.4.59. Depending on the results, this may be the only testing call.
build & make test run without problems on Debian 10
I noticed some suggestions from Debian lintian (but they do not seem to be new)
- spelling-error-in-binary: databse database
in back-ldap/monitor.c; this has already been fixed in 2.5.
- spelling-error-in-binary: everytime every time
in librewrite, this is a keyword and not an error
- spelling-error-in-manpage: allow to allow one to
these occur in RFC texts as well, not an error.
Andreas
Geert Hendrickx wrote:
On Fri, May 28, 2021 at 14:36:33 -0700, Quanah Gibson-Mount wrote:
his is the first testing call for OpenLDAP 2.4.59. Depending on the results, this may be the only testing call.
Hi
For how long do you plan to continue maintaining OpenLDAP 2.4.x ?
It has had about a 14 year span, it's well past time to retire it.
We're currently targeting 2.6 to be released this autumn. 2.5 should be quite stable already, so there will be no more backporting of fixes to 2.4 then.
On Mon, May 31, 2021 at 13:36:56 +0100, Howard Chu wrote:
Geert Hendrickx wrote:
For how long do you plan to continue maintaining OpenLDAP 2.4.x ?
It has had about a 14 year span, it's well past time to retire it.
We're currently targeting 2.6 to be released this autumn. 2.5 should be quite stable already, so there will be no more backporting of fixes to 2.4 then.
Ok. I actually assumed 2.4 was already EOL since 2.5 was marked stable.
Thanks for the additional info.
Geert
Geert Hendrickx wrote:
On Mon, May 31, 2021 at 13:36:56 +0100, Howard Chu wrote:
Geert Hendrickx wrote:
For how long do you plan to continue maintaining OpenLDAP 2.4.x ?
It has had about a 14 year span, it's well past time to retire it.
We're currently targeting 2.6 to be released this autumn. 2.5 should be quite stable already, so there will be no more backporting of fixes to 2.4 then.
Ok. I actually assumed 2.4 was already EOL since 2.5 was marked stable.
Yes, it has been closed to new features for quite a while already. But if any CVEs or such come up in the next few months we will probably still patch it.
Thanks for the additional info.
Geert
openldap-technical@openldap.org
-
A. Schulze -
Geert Hendrickx -
Howard Chu -
Michael Ströder -
Quanah Gibson-Mount