389-ds-base version 1.2.8.3 is released to the Stable repositories. This release contains fixes for bugs found in 1.2.8.2 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages. Other 389 packages have been updated as well. See below for the new packages and versions.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base \
389-admin idm-console-framework 389-ds-console 389-admin-console
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: There is a new sub package 389-ds-base-libs. This package contains libraries used by 389-ds-base and 389-ds-base-devel. If you use yum to install 389-ds-base, this dependency will automatically be taken care of. To remove the 389-ds-base package from the system, you must also remove the -libs package. If you use yum erase 389-ds-base-libs it will also remove 389-ds-base and any other dependent package.
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is a bug fix release, no new features
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8.2 in 389-ds-base:
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8.2 is released to the Stable repositories. This release contains a fix for a bug found in 1.2.8.1 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages. Other 389 packages have been updated as well. See below for the new packages and versions.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base \
389-admin idm-console-framework 389-ds-console 389-admin-console
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: There is a new sub package 389-ds-base-libs. This package contains libraries used by 389-ds-base and 389-ds-base-devel. If you use yum to install 389-ds-base, this dependency will automatically be taken care of. To remove the 389-ds-base package from the system, you must also remove the -libs package. If you use yum erase 389-ds-base-libs it will also remove 389-ds-base and any other dependent package.
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is a bug fix release, no new features
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8.1 in 389-ds-base:
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8.2 has been released to the Testing repositories. This release contains a fix for a bug found in 1.2.8.1 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base \
389-admin idm-console-framework 389-ds-console 389-admin-console
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: There is a new sub package 389-ds-base-libs. This package contains libraries used by 389-ds-base and 389-ds-base-devel. If you use yum to install 389-ds-base, this dependency will automatically be taken care of. To remove the 389-ds-base package from the system, you must also remove the -libs package. If you use yum erase 389-ds-base-libs it will also remove 389-ds-base and any other dependent package.
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is a bug fix release, no new features
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8.1 in 389-ds-base:
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8.1 has been released to the Testing repositories. This release contains many fixes for bugs found in 1.2.7 and 1.2.8 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base \
389-admin idm-console-framework 389-ds-console 389-admin-console
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: There is a new sub package 389-ds-base-libs. This package contains libraries used by 389-ds-base and 389-ds-base-devel. If you use yum to install 389-ds-base, this dependency will automatically be taken care of. To remove the 389-ds-base package from the system, you must also remove the -libs package. If you use yum erase 389-ds-base-libs it will also remove 389-ds-base and any other dependent package.
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is a bug fix release, no new features
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8 RC 5 in 389-ds-base:
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8 Release Candidate 4 (1.2.8.rc4) has been released to the Testing repositories. This release contains many fixes for bugs found in 1.2.7 and 1.2.8 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base \
389-admin idm-console-framework 389-ds-console 389-admin-console
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: There is a new sub package 389-ds-base-libs. This package contains libraries used by 389-ds-base and 389-ds-base-devel. If you use yum to install 389-ds-base, this dependency will automatically be taken care of. To remove the 389-ds-base package from the system, you must also remove the -libs package. If you use yum erase 389-ds-base-libs it will also remove 389-ds-base and any other dependent package.
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is a bug fix release, no new features
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8.rc2 in 389-ds-base:
Bugs fixed in admin server and console:
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8 Release Candidate 2 (1.2.8.rc2) has been released to the Testing repositories. This release contains many fixes for bugs found in 1.2.7 and 1.2.8 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base \
389-admin idm-console-framework 389-ds-console 389-admin-console
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: There is a new sub package 389-ds-base-libs. This package contains libraries used by 389-ds-base and 389-ds-base-devel. If you use yum to install 389-ds-base, this dependency will automatically be taken care of. To remove the 389-ds-base package from the system, you must also remove the -libs package. If you use yum erase 389-ds-base-libs it will also remove 389-ds-base and any other dependent package.
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is a bug fix release, no new features
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8.rc1 in 389-ds-base:
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8 Release Candidate 1 (1.2.8.rc1) has been released to the Testing repositories. This release contains many fixes for bugs found in 1.2.7 and 1.2.8 alpha testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base \
389-admin idm-console-framework 389-ds-console 389-admin-console
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: There is a new sub package 389-ds-base-libs. This package contains libraries used by 389-ds-base and 389-ds-base-devel. If you use yum to install 389-ds-base, this dependency will automatically be taken care of. To remove the 389-ds-base package from the system, you must also remove the -libs package. If you use yum erase 389-ds-base-libs it will also remove 389-ds-base and any other dependent package.
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is a bug fix release, no new features
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8.a3 in 389-ds-base:
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8 Alpha 3 (1.2.8.a3) has been released to the Testing repositories. This release contains many fixes for bugs found in 1.2.7 and 1.2.8 alpha testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base \
389-admin idm-console-framework 389-ds-console 389-admin-console
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is a bug fix release, no new features
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8.a2 in 389-ds-base:
Bugs fixed in other packages:
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8 Alpha 2 (1.2.8.a2) has been released to the Testing repositories. This release contains many fixes for bugs found in 1.2.7 and 1.2.8.a1 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is primarily a bug fix release, but there are some minor new features of interest to plugin authors
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
Bugs fixed since 1.2.8.a1
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.8 Alpha 1 (1.2.8.a1) has been released to the Testing repositories. This release contains many fixes for bugs found in 1.2.7. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6 or 1.2.7, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 13 are no longer supported. If you are running Fedora 12 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This is primarily a bug fix release, but there are some minor new features of interest to plugin authors
NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.7.5 fixes some key bugs found in 1.2.7.2, .3, and .4 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install 389-ds
setup-ds-admin.pl
yum upgrade 389-ds-base
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
The following bugs were fixed since 1.2.7.2:
For 1.2.7, we ran Coverity against the 389-ds-base code, found hundreds of issues (most of which were not serious and not security issues) and fixed them. The code is now Coverity clean. This release also contains fixes for some of the upgrade problems reported by the community, as well as many other bug fixes. NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.7.2 has been released to the Testing repositories. This release fixes some key bugs found in 1.2.7 and 1.2.7.1 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base 389-admin 389-adminutil 389-dsgw perl-Mozilla-LDAP
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 13, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 13 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
The following bugs from 1.2.7, 1.2.7.1 and 1.1.12 were fixed in 1.2.7.2:
For 1.2.7, we ran Coverity against the 389-ds-base code, found hundreds of issues (most of which were not serious and not security issues) and fixed them. The code is now Coverity clean. This release also contains fixes for some of the upgrade problems reported by the community, as well as many other bug fixes. NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.7.1 has been released to the Testing repositories. This release fixes some key bugs found in 1.2.7 testing. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base 389-admin 389-adminutil 389-dsgw perl-Mozilla-LDAP
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
The following bugs from 1.2.7 and 1.1.12 were fixed in 1.2.7.1 and 1.1.13:
For 1.2.7, we ran Coverity against the 389-ds-base code, found hundreds of issues (most of which were not serious and not security issues) and fixed them. The code is now Coverity clean. This release also contains fixes for some of the upgrade problems reported by the community, as well as many other bug fixes. NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.7 has been released to the Testing repositories. This release has some new features and many bug fixes. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK. We have removed the SELinux policy from the 389-ds-base and 389-admin packages on Fedora. The policy will be provided by the SELinux policy in the base OS. On EL, the policy will continue to be provided by the 389 packages.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base 389-admin 389-adminutil 389-dsgw perl-Mozilla-LDAP
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
We ran Coverity against the 389-ds-base code, found hundreds of issues (most of which were not serious and not security issues) and fixed them. The code is now Coverity clean. This release also contains fixes for some of the upgrade problems reported by the community, as well as many other bug fixes. NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
389-ds-base version 1.2.7 Alpha 3 has been released to the Testing repositories. This release has some new features and many bug fixes. On those platforms which have OpenLDAP built with Mozilla NSS crypto support (Fedora 14 and later), the packages are built with OpenLDAP instead of the Mozilla LDAP C SDK.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, or a stable 1.2.6, there is no problem.
The new packages and versions are:
yum install --enablerepo=[updates-testing|epel-testing] 389-ds
setup-ds-admin.pl
yum upgrade --enablerepo=[updates-testing|epel-testing] 389-ds-base 389-admin 389-adminutil 389-dsgw perl-Mozilla-LDAP
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
We ran Coverity against the 389-ds-base code, found hundreds of issues (most of which were not serious and not security issues) and fixed them. The code is now Coverity clean. This release also contains fixes for some of the upgrade problems reported by the community, as well as many other bug fixes. NOTE: bugs marked MODIFIED have been fixed but not fully tested and verified.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
The 389-ds-base 1.2.6.1 release is a bug fix release to fix a couple of crash problems and a couple of other problems.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, there is no problem.
The new packages and versions are:
Installation
yum install 389-ds
setup-ds-admin.pl
Upgrade
yum upgrade 389-ds-base
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
There are no new features in this release. This is a bug fix release only.
This release contains some important bug fixes. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
The 389-ds-base 1.2.6 release is essentially the same as the 1.2.6.rc7 release. The 389-admin-1.1.11 release is essentially the same as the 1.1.11.rc2 release. 1.2.6 contains several new features and many bug fixes.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
If you are upgrading from 1.2.5 or earlier, there is no problem.
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, there is no problem.
The new packages and versions are:
Installation
yum install 389-ds
setup-ds-admin.pl
Upgrade
yum upgrade
setup-ds-admin.pl -u
See Download for more information about setting up yum access. See Install_Guide for more information about the initial installation, setup, and upgrade
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
WARNING: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
This release contains many, many bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, there is no problem.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 7 for the 1.2.6 release. The new packages available for testing are:
Instructions for installing these from the testing repositories - different for Fedora and EPEL - difference is name of testing repo - on Fedora is updates-testing and for EPEL is epel-testing
Fedora new install
yum install –enablerepo=updates-testing 389-ds
Fedora upgrade
yum upgrade –enablerepo=updates-testing 389-ds-base
EPEL new install
yum install –enablerepo=epel-testing 389-ds
EPEL upgrade
yum upgrade –enablerepo=epel-testing 389-ds-base
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Now using EPEL for Enterprise Linux packages. See Download for more information.
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 11 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
NOTE: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
This release contains one bug fix. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
WARNING: If you are upgrading from a previous 1.2.6 release candidate, you will need to run fixfiles to fix some SELinux AVCs, or directory server will not start. See bug https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate, you will need to manually fix your entryrdn index files. See Subtree Rename Warning for more information. If you are upgrading from 1.2.5 or earlier, there is no problem.
Note: RC4 and RC5 were never released.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 6 for the 1.2.6 release. The new packages available for testing are:
Instructions for installing these from the testing repositories - different for Fedora and EPEL - difference is name of testing repo - on Fedora is updates-testing and for EPEL is epel-testing
Fedora new install
yum install –enablerepo=updates-testing 389-ds
Fedora upgrade
yum upgrade –enablerepo=updates-testing 389-ds-base 389-admin
EPEL new install
yum install –enablerepo=epel-testing 389-ds
EPEL upgrade
yum upgrade –enablerepo=epel-testing 389-ds-base 389-admin
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Now using EPEL for Enterprise Linux packages. See Download for more information.
NOTE: Fedora versions below 12 are no longer supported. If you are running Fedora 11 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 11 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
NOTE: If you are upgrading from 389 1.2.6 rcN (N < 6), simple upgrade won’t work due to the entryrdn format change (See also Bug 616608 - SIGBUS in RDN index reads on platforms with strict alignments ). Please follow the steps described in this section.
This release contains several bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 3 for the 1.2.6 release. The new packages available for testing are:
Instructions for installing these from the testing repositories - different for Fedora and EPEL - difference is name of testing repo - on Fedora is updates-testing and for EPEL is epel-testing
Fedora new install
yum install –enablerepo=updates-testing 389-ds
Fedora upgrade
yum upgrade –enablerepo=updates-testing 389-ds-base
EPEL new install
yum install –enablerepo=epel-testing 389-ds
EPEL upgrade
yum upgrade –enablerepo=epel-testing 389-ds-base
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 for 389-ds-base-1.2.6-0.8.rc3.fc12, 389-admin-1.1.11-0.4.rc1.fc12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Now using EPEL for Enterprise Linux packages. See Download for more information.
NOTE: Fedora versions below 11 are no longer supported. If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 11 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains a few bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 2 for the 1.2.6 release. The new packages available for testing are:
Instructions for installing these from the testing repositories - different for Fedora and EPEL - difference is name of testing repo - on Fedora is updates-testing and for EPEL is epel-testing
Fedora new install
yum install –enablerepo=updates-testing 389-ds
Fedora upgrade
yum upgrade –enablerepo=updates-testing 389-ds-base
EPEL new install
yum install –enablerepo=epel-testing 389-ds
EPEL upgrade
yum upgrade –enablerepo=epel-testing 389-ds-base
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 for 389-ds-base-1.2.6-0.7.rc2.fc12, 389-admin-1.1.11-0.4.rc1.fc12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Now using EPEL for Enterprise Linux packages. See Download for more information.
NOTE: Fedora versions below 11 are no longer supported. If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 11 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains a couple of bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 1 for the 1.2.6 release. The new packages available for testing are:
Instructions for installing these from the testing repositories - different for Fedora and EPEL - difference is name of testing repo - on Fedora is updates-testing and for EPEL is epel-testing
Fedora new install
yum install –enablerepo=updates-testing 389-ds
Fedora upgrade
yum upgrade –enablerepo=updates-testing 389-ds-base 389-admin
EPEL new install
yum install –enablerepo=epel-testing 389-ds
EPEL upgrade
yum upgrade –enablerepo=epel-testing 389-ds-base 389-admin
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 for 389-ds-base-1.2.6-0.4.rc1.fc12, 389-admin-1.1.11-0.4.rc1.fc12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Now using EPEL for Enterprise Linux packages. See Download for more information.
NOTE: Fedora versions below 11 are no longer supported. If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 11 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains a couple of bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Alpha 3 for the 1.2.6 release. The new packages available for testing are:
Instructions for installing these from the testing repositories - different for Fedora and EPEL - difference is name of testing repo - on Fedora is updates-testing and for EPEL is epel-testing
Fedora new install
yum install –enablerepo=updates-testing 389-ds
Fedora upgrade
yum upgrade –enablerepo=updates-testing 389-ds 389-ds-base 389-admin
EPEL new install
yum install –enablerepo=epel-testing 389-ds
EPEL upgrade
yum upgrade –enablerepo=epel-testing 389-ds 389-ds-base 389-admin
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 for 389-ds-base-1.2.6-0.4.a4.fc12, 389-admin-1.1.11-0.4.a4.fc12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Now using EPEL for Enterprise Linux packages. See Download for more information.
NOTE: Fedora versions below 11 are no longer supported. If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 11 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains many bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Alpha 3 for the 1.2.6 release. The new packages available for testing are:
Previous versions had a separate -selinux package for 389-ds-base and 389-admin - these are now gone - the selinux policy for the package is now provided by the package itself. Upgrading from a previous version should obsolete these packages.
Instructions for installing these from the testing repositories - different for Fedora and EPEL - difference is name of testing repo on Fedora is updates-testing and for EPEL is epel-testing
Fedora new install
yum install –enablerepo=updates-testing 389-ds
Fedora upgrade
yum upgrade –enablerepo=updates-testing 389-ds 389-ds-base 389-admin idm-console-framework 389-console 389-ds-console
EPEL new install
yum install –enablerepo=epel-testing 389-ds
EPEL upgrade
yum upgrade –enablerepo=epel-testing 389-ds 389-ds-base 389-admin idm-console-framework 389-console 389-ds-console
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 for 389-ds-base-1.2.6-0.3.a3.fc12, 389-admin-1.1.11-0.3.a3.fc12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Now using EPEL for Enterprise Linux packages. See Download for more information.
NOTE: Fedora versions below 11 are no longer supported. If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 11 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains many bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Alpha 2 for the 1.2.6 release. The new packages available for testing are:
Instructions for installing these from the testing repositories - different for Fedora and EPEL - difference is name of testing repo on Fedora is updates-testing and for EPEL is epel-testing
Fedora new install
yum install –enablerepo=updates-testing 389-ds
Fedora upgrade
yum upgrade –enablerepo=updates-testing 389-ds 389-ds-base 389-ds-base-selinux 389-admin 389-admin-selinux 389-adminutil
EPEL new install
yum install –enablerepo=epel-testing 389-ds
EPEL upgrade
yum upgrade –enablerepo=epel-testing 389-ds 389-ds-base 389-ds-base-selinux 389-admin 389-admin-selinux 389-adminutil
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. Each update is broken down by package and platform. For example, if you are using Fedora 12, and you have successfully installed or upgraded all of the packages, and the console and etc. works, then go to the links below for Fedora 12 for 389-ds-base-1.2.6-0.2.a2.fc12, 389-admin-1.1.11-0.2.a2.fc12, and 389-adminutil-1.1.10.fc12 and provide feedback.
scroll down to the bottom of the page, and click on the Add a comment >> link
If you are using a build on another platform, just send us an email to 389-users@lists.fedoraproject.org
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: Now using EPEL for Enterprise Linux packages. See Download for more information.
NOTE: Fedora versions below 11 are no longer supported. If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 11 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains many bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
Version 1.2.5 contains one new feature as well as several bug fixes. This release is essentially the same as 1.2.5 RC4.
NOTE: Packages for Enterprise Linux are available from Fedora EPEL. We will no longer have a separate yum repo hosted on this site.
NOTE: Fedora versions below 11 are no longer supported. If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. Fedora has Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 4 for the 1.2.5 release. The new packages available for testing are:
NOTE: Packages for Enterprise Linux are available from EPEL. We will no longer have a separate yum repo hosted on this site.
Instructions for installing these from the testing repositories:
yum install --enablerepo=updates-testing 389-ds # Fedora new install
yum upgrade --enablerepo=updates-testing 389-ds-base # Fedora upgrade
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. If you have an account, go here:
If you are using a build on another platform, just send us an email to 389-users@redhat.com.
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: FC6 (EL5) package updates are no longer available. Get them from EPEL instead.
NOTE: Fedora versions below 11 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. Fedora 9 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
None - this is primarily to fix bugs found in 1.2.5.rc3
This release contains one bug fix. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 3 for the 1.2.5 release. The new packages available for testing are:
NOTE: Packages for Enterprise Linux are available from EPEL. We will no longer have a separate yum repo hosted on this site.
Instructions for installing these from the testing repositories:
yum install --enablerepo=updates-testing 389-ds # Fedora new install
yum upgrade --enablerepo=updates-testing 389-ds-base 389-admin 389-console # Fedora upgrade
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. If you have an account, go here:
If you are using a build on another platform, just send us an email to 389-users@redhat.com.
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: FC6 (EL5) package updates are no longer available. Get them from EPEL instead.
NOTE: Fedora versions below 11 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 10 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. Fedora 9 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
None - this is primarily to fix bugs found in 1.2.5.rc2
This release contains a couple of bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 2 for the 1.2.5 release. The new package available for testing is:
Instructions for installing these from the testing repositories:
yum install --enablerepo=updates-testing 389-ds # Fedora new install
yum upgrade --enablerepo=updates-testing 389-ds-base 389-admin 389-console # Fedora upgrade
or EL5
yum install --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing 389-ds # new install
yum upgrade --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing 389-ds-base # upgrade
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. If you have an account, go here:
If you are using a build on another platform, just send us an email to 389-users@redhat.com.
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: If using the FC6 (EL5) packages, you must update your yum repo files - the URLs have changed. See Download for more information.
NOTE: Fedora versions below 10 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 9 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 9 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
None - this is primarily to fix bugs found in 1.2.5.rc1
This release contains a couple of bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This has been released for testing. The packages are available from the testing repositories. This is Release Candidate 1 for the 1.2.5 release. The new package available for testing is:
Instructions for installing these from the testing repositories:
yum install --enablerepo=updates-testing 389-ds # Fedora new install
yum upgrade --enablerepo=updates-testing 389-ds-base 389-admin 389-console # Fedora upgrade
or EL5
yum install --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing 389-ds # new install
yum upgrade --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing 389-ds-base # upgrade
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. If you have an account, go here:
If you are using a build on another platform, just send us an email to 389-users@redhat.com.
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: If using the FC6 (EL5) packages, you must update your yum repo files - the URLs have changed. See Download for more information.
NOTE: Fedora versions below 10 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 9 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 9 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains a couple of bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This is the alpha 1 (.a1) release. See Release_Procedure for information about release numbering. This release supports Windows Server 2008 in addition to 2003. 2000 is no longer supported (although it may work, we don’t test it). We also have 64-bit packages in addition to the 32-bit packages.
This release uses the 389 branding. The program files folder will be named 389 Management Console.
This release supports Windows Server 2008 in addition to 2003. 2000 is no longer supported (although it may work, we don’t test it). We also have 64-bit packages in addition to the 32-bit packages.
This release uses the 389 branding. The program files folder will be named 389 Password Sync. If you are upgrading from Fedora PassSync, the upgrade will attempt to copy your db and log files from the Fedora folder to the new 389 folder. It will not remove the old Fedora folder. You can remove that manually after you have verified that the 389 PassSync is working correctly.
This has been released for testing. The packages are available from the testing repositories, not the official release repositories yet. We are seeking feedback. The new package available for testing is:
Instructions for installing these from the testing repositories:
yum install --enablerepo=updates-testing 389-ds # Fedora new install
yum upgrade --enablerepo=updates-testing 389-ds-base 389-admin 389-console # Fedora upgrade
or EL5
yum install --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing 389-ds # new install
yum upgrade --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing 389-ds-base # upgrade
See Download for more information about setting up yum access.
The best way to provide feedback is via the Fedora Update system. If you have an account, go here:
If you are using a build on another platform, just send us an email to 389-users@redhat.com.
If you find a bug, or would like to see a new feature, you can enter it here - https://bugzilla.redhat.com/enter_bug.cgi?product=389
NOTE: If using the FC6 (EL5) packages, you must update your yum repo files - the URLs have changed. See Download for more information.
NOTE: Fedora versions below 10 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 9 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 9 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixed some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. For more information, see the 1.2.3 release notes below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains a couple of bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This release supports Windows Server 2008 in addition to 2003. 2000 is no longer supported (although it may work, we don’t test it). We also have 64-bit packages in addition to the 32-bit packages.
This release uses the 389 branding. The program files folder will be named 389 Password Sync. If you are upgrading from Fedora PassSync, the upgrade will attempt to copy your db and log files from the Fedora folder to the new 389 folder. It will not remove the old Fedora folder. You can remove that manually after you have verified that the 389 PassSync is working correctly.
This has been released for testing. The packages are available from the testing repositories, not the official release repositories yet. We are seeking feedback. The two new packages available for testing are:
Instructions for installing these from the testing repositories:
yum install --enablerepo=updates-testing 389-ds # Fedora new install
yum upgrade --enablerepo=updates-testing 389-ds-base 389-admin 389-console # Fedora upgrade
or EL5
yum install --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing 389-ds # new install
yum upgrade --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing 389-ds-base 389-admin 389-console # new install
See Download for more information about setting up yum access.
NOTE: If using the FC6 (EL5) packages, you must update your yum repo files - the URLs have changed. See Download for more information.
NOTE: Fedora versions below 10 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 9 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 9 and later have Java 1.6 OpenJDK.
NOTE: If you are using the console, after installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. 1.2.3 fixes some bugs related to update - it will remove old Fedora servers from the console, and will preserve TLS/SSL configuration. See the buglist below.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
This release contains several bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
NOTE: Fedora versions below 10 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 9 or earlier, you should upgrade.
NOTE: This release is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 9 and later have Java 1.6 OpenJDK.
NOTE: After installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. There is a bug in setup - it will leave the old versions of the server in console - you can ignore the old versions.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
There are no new features in this release. This release fixes some critical bugs.
This release contains several bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
NOTE: Fedora versions below 10 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 9 or earlier, you should upgrade.
NOTE: This is the first release that is branded as 389. All of the RPMs have been marked as obsoleting their Fedora DS counterparts. When upgrading via yum, you must use yum upgrade (not update) so that the obsoletes will be processed.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 9 and later have Java 1.6 OpenJDK.
NOTE: After installing the updates, you must run setup-ds-admin.pl -u to refresh your console and admin server configuration with the new version information. There is a bug in setup - it will leave the old versions of the server in console - you can ignore the old versions.
NOTE: 389-console is the command to run the console. This replaces fedora-idm-console.
There are several new features in this release. For more information, see New Features for 1.2.1
This release contains several bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
NOTE: Fedora versions below 9 are no longer supported (except for Fedora Core 6 - see below). If you are running Fedora 8 or earlier, you should upgrade.
NOTE: The console now requires Java 1.6. This is available on most platforms via OpenJDK (IcedTea). If you are using some derivative of Enterprise Linux 5, and cannot find Java 1.6, Java 1.6 is available from Fedora EPEL. See the Download page for information about Enterprise Linux 5. Fedora 9 and later have Java 1.6 OpenJDK.
This release contains over 200 bug fixes. The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED have been fixed but are still in testing.
groupdn=”ldap:///cn=Administrators,dc=example,dc=com)”
groupdn=”ldap:///suffix)??scope?(filter)”
(groupdn = ”ldap:///ou=Groups, dc=example,dc=com??sub?(cn=s_0)” or groupdn = ”ldap:///ou=Groups,dc=example,dc=com)??sub?(cn=s_1)”) and groupdn = ”ldap:///ou=Groups), dc=example,dc=com??sub?(cn=*s_2)”
means the user must belong to the group ending with s_0 or s_1, and the group ending with s_2
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This release fixes a bug in the Windows Sync code that was introduced with 1.1.2. If you are using Windows Sync or plan to use freeIPA, you should upgrade to 1.1.3.
See Fedora Directory Server 1.1.2 for additional information.
NOTE: If you had servers that did not show up console, or you want to update the information displayed for those servers in the console, run setup-ds-admin.pl with the new update option (-u or –update) - this will re-register all of your servers with the console. It is ok to run this even if your servers are already registered correctly and show up in the console - it will update the date and version information.
setup-ds-admin.pl -u
This will prompt for the Configuration Directory Server Admin password (i.e. the password for the admin user).
This release contains many, many bug fixes, including some security problems and memory leaks The complete list of bugs fixed is found at the link below. Note that bugs marked as MODIFIED are considered fixed. Only bugs in the NEW or ASSIGNED state have not been fixed or resolved.
The Download page has information about how to get the binaries. The Install_Guide has information about installation and setup.
This is primarily a bug fix update. New features:
WARNING: Following the instructions below will upgrade your 1.0 installation to 1.1. If you want to do this, run /usr/sbin/migrate-ds-admin.pl after installation. If you do not want to do this, use a clean machine or a VM to install Fedora DS 1.1.
Init scripts!
service dirsrv {start|stop|restart} [instance name] service dirsrv-admin {start|stop|restart} edit /etc/sysconfig/dirsrv or /etc/sysconfig/dirsrv-admin to set environment
If you are already using fedora-ds-base from Fedora, you must first upgrade it
rpm -qi fedora-ds-base
If that returns an error, skip to the next bullet, otherwise
yum upgrade fedora-ds-base
Set up your Fedora DS yum repo - as root
cd /etc/yum.repos.d wget http:///binaries/idmcommon.repo) wget http:///binaries/dirsrv.repo)
Full install
yum install fedora-ds
This will install many dependencies too. NOTE: On Fedora 8, the IcedTea Java can run the console. On Fedora 7 and earlier, you will still need to install a proprietary JRE in order to run - see Install_Guide for information about how to install Java.
NOTE: If you are upgrading from 1.0, DO NOT USE setup-ds-admin.pl - use migrate-ds-admin.pl instead
Follow the above steps to set up the yum repositories, then just install the fedora-idm-console package:
yum install fedora-idm-console
Then use /usr/bin/fedora-idm-console
Follow the above steps to set up the yum repositories, then just install the fedora-ds-base package:
yum install fedora-ds-base
FedoraConsole.msi is a Windows Installer file for the Console for Fedora Directory Server 1.1. Go to Download to download the file.
WARNING: Following the instructions below will upgrade your 1.0 installation to 1.1. If you want to do this, run /usr/sbin/migrate-ds-admin.pl after installation. If you do not want to do this, use a clean machine or a VM to install Fedora DS 1.1.
What’s new?
Init scripts!
service dirsrv {start|stop|restart} [instance name] service dirsrv-admin {start|stop|restart} edit /etc/sysconfig/dirsrv or /etc/sysconfig/dirsrv-admin to set environment
If you are already using fedora-ds-base from Fedora, you must first upgrade it
rpm -qi fedora-ds-base
If that returns an error, skip to the next bullet, otherwise
yum upgrade fedora-ds-base
Set up your Fedora DS yum repo - as root
cd /etc/yum.repos.d wget http:///binaries/idmcommon.repo wget http:///binaries/dirsrv.repo
Install
yum install fedora-ds
This will install many dependencies too. NOTE: On Fedora 8, the IcedTea Java can run the console. On Fedora 7 and earlier, you will still need to install a proprietary JRE in order to run - see Install_Guide for information about how to install Java.
NOTE: If you are upgrading from 1.0, DO NOT USE setup-ds-admin.pl - use migrate-ds-admin.pl instead
What’s new?
First, Download the binaries. Next, if you are upgrading from an earlier release, use rpm -Uvh to install, otherwise, use rpm -ivh. If upgrading, make sure your slapd and admin server are running:
cd /opt/fedora-ds
./slapd-yourhost/start-slapd
./start-admin
Next, if you are using password syntax checking, disable it before running setup:
ldapmodify -x -D "cn=directory manager" -w password
dn: cn=config
changetype: modify
replace: passwordCheckSyntax
passwordCheckSyntax: off
Finally, run setup as follows:
cd /opt/fedora-ds ; ./setup/setup
Then, if you are using password syntax checking, enable it again:
ldapmodify -x -D "cn=directory manager" -w password
dn: cn=config
changetype: modify
replace: passwordCheckSyntax
passwordCheckSyntax: on
Please refer to the Install_Guide for more information.
What’s new?
First, Download the binaries. Next, if you are upgrading from an earlier release, use rpm -Uvh to install, otherwise, use rpm -ivh. If upgrading, make sure your slapd and admin server are running:
cd /opt/fedora-ds
./slapd-yourhost/start-slapd
./start-admin
Finally, run setup as follows:
cd /opt/fedora-ds ; ./setup/setup
Please refer to the Install_Guide for more information.
What’s new?
First, Download the binaries. Next, if you are upgrading from an earlier release, use rpm -Uvh to install, otherwise, use rpm -ivh. Finally, run setup as follows:
cd /opt/fedora-ds ; ./setup/setup
If upgrading, you may need to restart your slapd and/or admin server after running setup:
cd /opt/fedora-ds
./slapd-yourhost/start-slapd
./start-admin
Please refer to the Install_Guide for more information.
This is a patch release to address the following problems:
First, Download the binaries.
If you are upgrading from Fedora DS 1.0, DO NOT RUN SETUP after doing the rpm -Uvh. Instead, just restart your directory servers, followed by restarting your admin server. e.g.
cd /opt/fedora-ds
./slapd-name/start-slapd
./slapd-name2/start-slapd
...
./slapd-nameN/start-slapd
./start-admin
If you are installing the software for the first time, please refer to Install_Guide for more information.