[Pkg-openldap-devel] [openldap] 07/07: move BDB format note closer to related notes, update version

[Ryan Tandy]

This is an automated email from the git hooks/post-receive script.

rtandy-guest pushed a commit to branch master
in repository openldap.

commit 0c381959666bb449293c8d44043372a9065250d0
Author: Ryan Tandy <ryan at nardis.ca>
Date:   Thu Aug 28 21:07:56 2014 -0700

    move BDB format note closer to related notes, update version
---
 debian/slapd.README.Debian | 41 +++++++++++++++++++----------------------
 1 file changed, 19 insertions(+), 22 deletions(-)

diff --git a/debian/slapd.README.Debian b/debian/slapd.README.Debian
index f5be4e6..632727e 100644
--- a/debian/slapd.README.Debian
+++ b/debian/slapd.README.Debian
@@ -65,16 +65,32 @@ Using BDB/HDB Backends
 
 BerkeleyDB Version
 
-  slapd has been built against version 4.8.30 of BerkeleyDB. This version is
-  supported by the upstream developers.
+  slapd has been built against version 5.3.28 of BerkeleyDB.
 
   slapd will automatically handle database recovery, so you generally do
   not need the BerkeleyDB utilities.  However, if you want to perform
   other operations directly on the raw database without using the slapd
-  tools, install db4.8-util and use those BerkeleyDB utilities. Utilities
+  tools, install db5.3-util and use those BerkeleyDB utilities. Utilities
   from other db*-util packages will not work correctly and may render the
   database unusable by slapd.
 
+BerkeleyDB database format upgrades
+
+  When upgrading slapd to a new version where the Berkeley DB library's
+  storage format has changed, the database has to be backed up using
+  slapcat(8) before upgrading and restored using slapadd(8) afterwards.
+  Normally the maintainer scripts will handle this automatically,
+  performing the dump and restore as needed.
+
+  If, after upgrading, slapd fails to start and you see the message
+  "Program version doesn't match environment version" in syslog, then
+  the DB version may have changed without a dump and reload. This should
+  be reported as a bug in the slapd package. In this case you will have
+  to downgrade slapd to the previous version as the new tools are unable
+  to dump the old database, and the same error would prevent you from
+  upgrading to the fixed version. Old package versions can be
+  found at <http://snapshot.debian.org> if needed.
+
 Logging
 
   slapd logs to the facility local4. If you want to direct slapd's logs to
@@ -220,22 +236,3 @@ Modifications Compared to Upstream
   openldap source package.
 
  -- Russ Allbery <rra at debian.org>, Thu, 14 Feb 2008 18:47:07 -0800
-
-Database format upgrades
-
-  When upgrading slapd to a new version where the Berkeley DB library's
-  storage format has changed, the database has to be backed up using
-  slapcat(8) before upgrading and restored using slapadd(8) afterwards.
-  Normally the maintainer scripts will handle this automatically,
-  performing the dump and restore as needed.
-
-  If, after upgrading, slapd fails to start and you see the message
-  "Program version doesn't match environment version" in syslog, then
-  the DB version may have changed without a dump and reload. This should
-  be reported as a bug in the slapd package. In this case you will have
-  to downgrade slapd to the previous version as the new tools are unable
-  to dump the old database, and the same error would prevent you from
-  upgrading to the fixed version. Old package versions can be
-  found at http://snapshot.debian.org if needed.
-
- -- Ryan Tandy <ryan at nardis.ca>, Thu, 19 Jun 2014 12:51:38 -0700

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-openldap/openldap.git