This bug was fixed in the package openldap - 2.4.40+dfsg-1ubuntu1
---
openldap (2.4.40+dfsg-1ubuntu1) wily; urgency=low
* Merge from Debian testing (LP: #1395098, LP: #1316124). Remaining changes:
- Enable AppArmor support:
- d/apparmor-profile: add AppArmor profile
** Branch linked: lp:ubuntu/wily-proposed/openldap
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1316124
Title:
Actual Ubuntu Slapd totaly useless for serious use
To manage
Please add Debian backport bug
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1316124
Title:
Actual Ubuntu Slapd totaly useless for serious use
To manage notifications about this
Once Utopic syncs with the new Debian version I think the best option is
to make a request via the Ubuntu Backports Project (-backports).
** Changed in: openldap (Ubuntu)
Importance: Undecided = Medium
** Changed in: openldap (Ubuntu)
Status: New = Confirmed
--
You received this bug
Le 05/05/2014 16:06, Peter Matulis a écrit :
Please add Debian backport bug
Sorry, I misspoke. There is no backport in Debian now.
Debian finally switch to 2.4.39 in Sid and Jessie after a maintainer change.
A backport for Ubuntu 14.04 LTS is highly desirable as for Debian stable.
Should I open
There's an open request (for a long time) for a backport in Debian:
http://bugs.debian.org/685748
A backport should address the question of DB format upgrades when going
from release to release. The technique currently used, checking the
version of the package being upgraded, will fail if a newer
