This bug was fixed in the package openldap2.3 - 2.4.9-1ubuntu1
---
openldap2.3 (2.4.9-1ubuntu1) intrepid; urgency=low
* Merge from debian unstable, remaining changes:
- debian/apparmor-profile: add AppArmor profile
- debian/slapd.postinst: Reload AA profile on configuration
** Changed in: openldap2.3 (Debian)
Status: Confirmed = Fix Committed
--
[SRU] Assertion error in schema_init.c:366: octetStringIndexer
https://bugs.launchpad.net/bugs/220724
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Copied to hardy-updates.
** Changed in: openldap2.3 (Ubuntu Hardy)
Status: Fix Committed = Fix Released
--
[SRU] Assertion error in schema_init.c:366: octetStringIndexer
https://bugs.launchpad.net/bugs/220724
You received this bug notification because you are a member of Ubuntu
Server
I was able to recreate the bug using the steps and attachment from
comment #5 using slapd package version 2.4.7-6ubuntu3 and ldap-utils
2.4.7-6ubuntu3. I then installed package version 2.4.7-6ubuntu4.1 from
-proposed and was unable to recreate the bug. Additionally, I ran test-
openldap.py from
My server does not crash now. :-)
--
[SRU] Assertion error in schema_init.c:366: octetStringIndexer
https://bugs.launchpad.net/bugs/220724
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap2.3 in ubuntu.
--
Ubuntu-server-bugs
** Changed in: openldap2.3 (Debian)
Status: Unknown = Confirmed
--
[SRU] Assertion error in schema_init.c:366: octetStringIndexer
https://bugs.launchpad.net/bugs/220724
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap2.3 in
Accepted into hardy-proposed, please test.
** Changed in: openldap2.3 (Ubuntu Hardy)
Status: Confirmed = Fix Committed
** Tags added: verification-needed
--
[SRU] Assertion error in schema_init.c:366: octetStringIndexer
https://bugs.launchpad.net/bugs/220724
You received this bug
Statement of Impact:
Slapd crashes when doing a time stamp modification. I was able to
reproduce this readily in hardy.
how this bug has been addressed:
I have attached the patch that fixes this issue for hardy. It is
basically a 2 line patch that has been already commited upstream. It is
Chuck, thanks for reproducing and the patch. Please provide a detailled
changelog entry which accompanies the patch and upload to hardy-proposed
when you are ready.
BTW, the regression part of the SRU policy is to estimate the worst
possilble regression, not the actual set of regressions this
