tstellar / rpms / openldap

Forked from rpms/openldap 3 years ago
Clone

d8aedf8 - Upgrade to 2.3.19, which upstream now considers stable

Authored and Committed by fenlason 18 years ago
    - 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.
    
        
file modified
+4 -2
file modified
+3 -3
file modified
+14 -5
file modified
+71 -12
file modified
+2 -2