Am Freitag, 13. Juni 2008 16:30:18 schrieb Erik Rossen:
> Package: gosa-schema
> Version: 2.5.16.1-1
> Severity: important
>
>
> Somewhere between version 2.4beta2-1 and 2.5.16, the definition of the
> objectClass "goServer" underwent a regression where it got changed from
> a STRUCTURAL to an AUXILLARY objectClass (line 230 of the current
> version).
>
> This causes LDAP trees exported from older systems containing GOsa
> configurations to fail importation into newer (and stricter) OpenLDAP
> servers since the objects lack a valid structural object class. The
> failure looks like
>
> [EMAIL PROTECTED]:~# slapadd -c -l oldldap.ldif
> slapadd: dn="cn=mail,ou=servers,ou=systems,dc=example,dc=com"
> (line=248): (65) no structural object class provided
>
> even though "cn=mail,ou=servers,ou=systems,dc=example,dc=com" is
> perfectly well-defined:
>
> dn: cn=mail,ou=servers,ou=systems,dc=example,dc=com
> structuralObjectClass: goServer
> entryUUID: a279e56e-bd5d-1029-8625-9ebaa3928079
> creatorsName: cn=admin,dc=example,dc=com
> createTimestamp: 20050919133257Z
> cn: mail
> goImapSievePort: 2000
> goImapPassword: NONEOFYOURBUSINESS
> goImapAdmin: cyrus
> objectClass: top
> objectClass: goImapServer
> objectClass: goServer
> goImapName: imap://mail.example.com
> goImapSieveServer: mail.example.com
> goImapConnect: {mail.example.com:143/imap/notls}
> entryCSN: 20060220124346Z#000001#00#000000
> modifiersName: cn=admin,dc=example,dc=com
> modifyTimestamp: 20060220124346Z
>
> A temporary workaround is just to change line 230 from AUXILLARY back to
> STRUCTURAL.
>
> It would also be nice if the version number at the head of the file
>
> ## Version 030403
>
> got incremented when there were changes. ;-)
>
> -- System Information:
> Debian Release: 4.0
> APT prefers oldstable
> APT policy: (991, 'oldstable'), (991, 'stable'), (66, 'oldstable'), (33,
> 'unstable') Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/dash
> Kernel: Linux 2.6.18-6-vserver-686
> Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Add the GOhard objectClass to your server entries and you're fine. The GOsa
package cannot modify your ldap content to do a smooth update in this case.
I cannot fix your issue - except writing a note inside of the README.
Cheers,
Cajus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
