New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Certain schema files are not replaced during upgrade #1192
Comments
Comment from lkrispen (@elkris) at 2014-07-21 17:12:46 when fixing this we should also check if there are other schema changes which could be missed during upgrade |
Comment from mreynolds (@mreynolds389) at 2014-07-21 21:38:14 The following schema files need to be added to the upgrade script: 10dna-plugin.ldif |
Comment from lkrispen (@elkris) at 2014-07-21 21:48:29 ack. just wondering if it wouldn't be better if the schema files would be listed in order 00xx .. 02xx 10xx .... |
Comment from mreynolds (@mreynolds389) at 2014-07-21 22:02:11 Replying to [comment:6 elkris]:
I was under the impression the numbering was only used for startup purposes, but just in case I redid the patch. New patch attached. |
Comment from mreynolds (@mreynolds389) at 2014-07-21 22:02:27 revision |
Comment from lkrispen (@elkris) at 2014-07-21 22:10:20 I think functionally the order is irrelevant, just easier to check if the file is already present in the list if you change a schema file |
Comment from mreynolds (@mreynolds389) at 2014-07-21 22:26:10 git merge ticket47861 65216ab..fe59338 master -> master da318fa..daffe97 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 722117e..ba60488 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 7dc69db..f1551fe 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 |
Comment from mreynolds (@mreynolds389) at 2017-02-11 22:48:16 Metadata Update from @mreynolds389:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47861
The schema for the dna plugin was changed with the fix for 47379. But the ldif was not added to the schema update script.
The text was updated successfully, but these errors were encountered: