Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #2333
Closed
Open
Issue created Apr 22, 2013 by bmortier@bmortierMaintainer

fd-insert-schema should use schema2ldif

schema2ldif handle more schema files than fusiondirectory-schema2ldif. So fusiondirectory-insert-schema should use schema2ldif.

fusiondirectory-schema2ldif might still be useful for special needs (replace and modify modes)

(from redmine: issue id 2333, created on 2013-04-22, closed on 2013-04-23)

  • Changesets:
    • Revision 875b9f31 by Côme Chilliet on 2013-04-22T09:21:06.000Z:
Fixes: #2333 fd-insert-schema should use schema2ldif
  • Revision e307b837 by Benoit MORTIER on 2013-04-22T09:41:54.000Z:
Fixes: #2333 fd-insert-schema should use schema2ldif
  • Revision e9918f55 by Benoit MORTIER on 2013-04-22T16:15:54.000Z:
Fixes: #2333 fd-insert-schema should use schema2ldif
  • Custom Fields:
    • Bug in version: 1.0.5
  • Uploads:
    • 0001-Fixes-2333-fd-insert-schema-should-use-schema2ldif.patch
Assignee
Assign to
Time tracking