[Bug 319544] Re: gosa-schema contains schema with bad char in filename

2011-09-28 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gosa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/319544 Title:

[Bug 319544] Re: gosa-schema contains schema with bad char in filename

2010-09-13 Thread Anders Wallenquist
This is still a problem in lucid -- gosa-schema contains schema with bad char in filename https://bugs.launchpad.net/bugs/319544 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 319544] Re: gosa-schema contains schema with bad char in filename

2009-09-16 Thread Dave Vree
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. --

[Bug 319544] Re: gosa-schema contains schema with bad char in filename

2009-09-16 Thread Dave Vree
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. ** Attachment added:

[Bug 319544] Re: gosa-schema contains schema with bad char in filename

2009-08-26 Thread Tim Bates
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. -- gosa-schema contains schema with bad char in