#287014 evolutionPerson schema incompatible with other MUAs

#287014#5
Date:
2004-12-23 17:14:32 UTC
From:
To:
In my slapd.conf I have the following:

include /etc/ldap/schema/core.schema
include /etc/ldap/schema/cosine.schema
include /etc/ldap/schema/nis.schema
include /etc/ldap/schema/inetorgperson.schema
include /usr/share/evolution-data-server-1.0/evolutionperson.schema

My existing LDAP records seem to all be using inetOrgPerson.  When
updating them from Evolution, the update fails with the following error:

(evolution-data-server:21033): libebookbackend-WARNING **: modify_contact_handler: 45 (Cannot modify object class), additional info: structural object class modification from 'inetOrgPerson' to 'evolutionPerson' not allowed

Adding a new LDAP record from Evolution and then editing that record
does not show a problem, probably since the record uses evolutionPerson
from the start.

Removing...

   include /usr/share/evolution-data-server-1.0/evolutionperson.schema

... from slapd.conf appears to be a work-around, assuming that all the
LDAP records are using inetOrgPerson, but probably doesn't support all
the fields that one might want.

Evolution should be able to detect the object class of the entry and
should try to save with same info.

#287014#10
Date:
2010-06-21 19:03:30 UTC
From:
To:
Hey,

this bug is quite old, and Evolution has changed quite a bit since them.
Is the bug still present?

Cheers,

#287014#15
Date:
2015-09-19 18:37:22 UTC
From:
To:
This bug is still present in jessie. It is due to the definition of the
evolutionPerson objectclass. It should not be STRUCTURAL, but AUXILIARY:

/usr/share/evolution-data-server/evolutionperson.schema contains:
# evolutionPerson
objectclass     ( 1.3.6.1.4.1.8506.1.3.1
    NAME 'evolutionPerson'
        DESC 'Objectclass geared to Evolution Usage'
    SUP inetOrgPerson
    STRUCTURAL