openldap/.cvsignore

openldap-2.2.29.tgz
MigrationTools-46.tar.gz
openldap-2.3.19.tgz
db-4.4.20.tar.gz
autoconf-2.13.1.tar.gz
automake-1.4a.tar.gz
openldap-2.3.24.tgz
openldap-2.3.27.tgz
Upgrade to 2.2.29 2005-10-10 20:32:00 +00:00			`openldap-2.2.29.tgz`
Upgrade to 2.3.11, with much fanfare. 2005-11-11 03:39:40 +00:00			`MigrationTools-46.tar.gz`
- Upgrade to 2.3.19, which upstream now considers stable - Modify the -config.patch, ldap.init, and this spec file to put the pid file and args file in an ldap-owned openldap subdirectory under /var/run. - Move back_sql* out of %{_sbindir}/openldap , which requires hand-moving slapd and slurpd to _sbindir, and recreating symlinks by hand. - Retire openldap-2.3.11-ads.patch, which went upstream. - Update the ldap.init script to run slaptest as the ldap user rather than as root. This solves bz#150172 Startup failure after database problem - Add to the servers post and preun scriptlets so that on preun, the database is slapcatted to /var/lib/ldap/upgrade.ldif and the database files are saved to /var/lib/ldap/rpmorig. On post, if /var/lib/ldap/upgrade.ldif exists, it is slapadded. This means that on upgrades from 2.3.16-2 to higher versions, the database files may be automatically upgraded. Unfortunatly, because of the changes to the preun scriptlet, users have to do the slapcat, etc by hand when upgrading to 2.3.16-2. Also note that the /var/lib/ldap/rpmorig files need to be removed by hand because automatically removing your emergency fallback files is a bad idea. - Upgrade internal bdb to db-4.4.20. For a clean upgrade, this will require that users slapcat their databases into a temp file, move /var/lib/ldap someplace safe, upgrade the openldap rpms, then slapadd the temp file. 2006-01-31 21:47:36 +00:00			`openldap-2.3.19.tgz`
			`db-4.4.20.tar.gz`
			`autoconf-2.13.1.tar.gz`
			`automake-1.4a.tar.gz`
2.3.24 is now stable. 2006-06-07 17:17:21 +00:00			`openldap-2.3.24.tgz`
2.3.27 2006-08-28 20:51:47 +00:00			`openldap-2.3.27.tgz`