Univention Bugzilla – Bug 35697
OpenLDAP in UCS 4.0
Last modified: 2014-11-26 06:54:27 CET
OpenLDAP fixed a couple of things in the MDB backend code, so maybe we want to import the new package. Acutually it's already in jessie (currently):
looks like 2.4.40 is about to be released in the next couple of days:
will be the first update since january with a couple of fixes:
There is our 31_avoid_OID_changes.patch, which patches the OpenLDAP internal OIDs back so the OpenLDAP 2.3 conventions. We might consider to drop that patch at some point. If we don't, then we need to adjust replication.py to cover additional OIDs:
> There are additional builtin OIDs to be considered in replication.py for MDB:
> 220.127.116.11.4.1.4203.618.104.22.168.2.12.1 # olcDbMaxReaders
> 22.214.171.124.4.1.4203.6126.96.36.199.2.12.2 # olcDbMaxSize
> 188.8.131.52.4.1.4203.6184.108.40.206.2.12.3 # olcDbEnvFlags
See Bug 35144 Comment 12.
imported openldap 2.4.39-1.1 from debian jessie
-> debian patches have been fixed with 2.4.39-1
-> debian patch debian/patches/heimdal-fix is identical
no need to disable this debian patch and add a patch
that does the same thing
-> this is already upstream
-> use db5.1 (instead of 5.3)
2.4.40 has been released, maybe we can simply run uupdate on the debian package: http://www.openldap.org/software/download/
"uupdated" the 2.4.39 package to version 2.4.40.
Removed doc/drafts, doc/rfcs and servers/slapd/schema/core.schema from the source tarball (debian can not ship these files).
Also removed debian/patches/CVE-2013-4449.patch, this is already upstream
Build package openldap_2.4.40-1 for UCS 4.0
Maybe we should wait for the official debian package and check, if they there are additional changes.
(In reply to Felix Botner from comment #5)
> Maybe we should wait for the official debian package and check, if they
> there are additional changes.
Debian package is ok and the Univention patches have been applied for the built.
> Also removed debian/patches/CVE-2013-4449.patch, this is already upstream
Verified. Changelog is ok too.
UCS 4.0-0 has been released:
If this error occurs again, please use "Clone This Bug".