gosa-schema contains schema with bad char in filename

[stephen mulcahy]

Binary package hint: gosa-schema

In order to use gosa with OpenLDAP 2.4 which uses an in memory directory information tree (cn=config) for storing
configuration information and schema, the schema from the gosa schema package need to be converted to ldif format
using the following procedure (for example, adapted from https://help.ubuntu.com/8.10/serverguide/C/openldap-server.html),

1. Put the filenames of schema to be converted into a file (schema_convert.conf)

include /etc/ldap/schema/core.schema
include /etc/ldap/schema/cosine.schema
include /etc/ldap/schema/inetorgperson.schema
include /etc/ldap/schema/nis.schema
include /etc/ldap/schema/samba3.schema
include /etc/ldap/schema/trust.schema
include /etc/ldap/schema/gosystem.schema
include /etc/ldap/schema/gofon.schema
include /etc/ldap/schema/goto.schema
include /etc/ldap/schema/gofax.schema
include /etc/ldap/schema/goserver.schema
include /etc/ldap/schema/goto-mime.schema
include /etc/ldap/schema/gosa+samba3.schema

2. Create a temporary directory for the output

mkdir /tmp/ldif_output

3. Use slaptest to convert the schema to ldif

slaptest -f schema_convert.conf -F /tmp/ldif_output

If you follow steps 1-3 using the files from gosa-schema as is, you get the following error after running slaptest.

backend_startup_one: bi_db_open failed! (-1)
slap_startup failed (test would succeed using the -u switch)

Some testing and googling reveals that the problem comes from the filename gosa+samba3.schema
Renaming this to /etc/ldap/schema/gosa-samba3.schema allows the LDIF conversion to proceed without issue.

Can this file be renamed in future releases of the package?

thanks,

[Tim Bates (tin)]

A better idea than renaming that file might be to actually include the correctly formatted files! Seems a bit stupid to include packages that can't actually be used until you convert a pile of files when they could be supplied in the first place.

[Dave Vree (hdave)]

I can confirm this was fixed upstream in 2.6.5 of Gosa. And yes, providing the actual LDIF files and automatically inserting them into the OpenLDAP schema would be great. As you can see, it is a major hassle to add new schemas to OpenLDAP since they got rid of the slapd.conf file.

[Dave Vree (hdave)]

Just in case somebody else runs into this problem, I have attached a file that holds the gosa ldifs you need to merge into your slapd.d for Gosa 2.6.5. You may need to renumber them. I have numbered them 4 through 12 as openldap ships with 0 through 3 already installed.

[Anders Wallenquist (aw)]

This is still a problem in lucid

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.