#47861 Certain schema files are not replaced during upgrade
Closed: Fixed None Opened 4 years ago by lkrispen.

The schema for the dna plugin was changed with the fix for 47379. But the ldif was not added to the schema update script.


when fixing this we should also check if there are other schema changes which could be missed during upgrade

The following schema files need to be added to the upgrade script:

10dna-plugin.ldif
50ns-mail.ldif
60qmail.ldif
60radius.ldif
60samba3.ldif
60posix-winsync-plugin.ldif
60sabayon.ldif
60nis.ldif
60sendmail.ldif

ack. just wondering if it wouldn't be better if the schema files would be listed in order 00xx .. 02xx 10xx ....

Replying to [comment:6 lkrispen]:

ack. just wondering if it wouldn't be better if the schema files would be listed in order 00xx .. 02xx 10xx ....

I was under the impression the numbering was only used for startup purposes, but just in case I redid the patch. New patch attached.

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

git merge ticket47861
Updating 65216ab..fe59338
Fast-forward
ldap/admin/src/scripts/60upgradeschemafiles.pl | 2 +-

65216ab..fe59338 master -> master
commit fe59338

da318fa..daffe97 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit daffe97

722117e..ba60488 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit ba604880431bc610c5dff92356b7c897d495f0a6

7dc69db..f1551fe 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit f1551fe

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.2.20

2 years ago

Login to comment on this ticket.

Metadata