[pkg-db-commits] [SCM] Berkeley DB Debian packaging branch, debian-sid, updated. debian/5.1.25-10-34-g42cbaf8
Ondřej Surý
ondrej at sury.org
Fri Jan 20 18:35:14 UTC 2012
The following commit has been merged in the debian-sid branch:
commit 1a30d1766430b605e3d89b2bb7e8e574e92f731a
Author: Ondřej Surý <ondrej at sury.org>
Date: Fri Sep 23 11:36:03 2011 +0200
Adapt debian/ directory from db5.1 to db5.2
diff --git a/debian/control b/debian/control
index 75ce971..4f41e66 100644
--- a/debian/control
+++ b/debian/control
@@ -1,4 +1,4 @@
-Source: db
+Source: db5.2
Section: libs
Priority: standard
Maintainer: Debian Berkeley DB Group <pkg-db-devel at lists.alioth.debian.org>
@@ -14,200 +14,200 @@ Homepage: http://www.oracle.com/technology/software/products/berkeley-db/index.h
Vcs-Browser: http://git.debian.org/?p=pkg-db/db.git
Vcs-Git: git://git.debian.org/pkg-db/db.git
-Package: db5.1-doc
+Package: db5.2-doc
Architecture: all
Section: doc
Priority: optional
Depends: ${misc:Depends}
-Description: Berkeley v5.1 Database Documentation [html]
+Description: Berkeley v5.2 Database Documentation [html]
This package contains documentation in HTML format for all of
the APIs (C, C++, C#, STL, Java, Tcl) and utilities provided
- by version 5.1 of Berkeley DB.
+ by version 5.2 of Berkeley DB.
-Package: libdb5.1-dev
+Package: libdb5.2-dev
Architecture: any
Section: libdevel
Priority: extra
-Depends: libdb5.1 (= ${binary:Version}),
+Depends: libdb5.2 (= ${binary:Version}),
${misc:Depends}
-Suggests: db5.1-doc
-Conflicts: libdb4.6-dev, libdb4.7-dev, libdb4.8-dev
-Description: Berkeley v5.1 Database Libraries [development]
+Suggests: db5.2-doc
+Conflicts: libdb4.6-dev, libdb4.7-dev, libdb4.8-dev, libdb5.1-dev
+Description: Berkeley v5.2 Database Libraries [development]
This is the development package which contains headers and static
- libraries for the Berkeley v5.1 database library.
+ libraries for the Berkeley v5.2 database library.
-Package: libdb5.1
+Package: libdb5.2
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends},
${misc:Depends}
-Description: Berkeley v5.1 Database Libraries [runtime]
- This is the runtime package for programs that use the v5.1 Berkeley
+Description: Berkeley v5.2 Database Libraries [runtime]
+ This is the runtime package for programs that use the v5.2 Berkeley
database library.
-Package: db5.1-util
+Package: db5.2-util
Architecture: any
Section: database
Priority: optional
Multi-Arch: foreign
Depends: ${shlibs:Depends},
${misc:Depends}
-Description: Berkeley v5.1 Database Utilities
+Description: Berkeley v5.2 Database Utilities
This package provides different tools for manipulating databases
- in the Berkeley v5.1 database format, and includes:
- - db5.1_archive: write the pathnames of the log files no longer in use.
- - db5.1_checkpoint: daemon process to monitor the database log and
+ in the Berkeley v5.2 database format, and includes:
+ - db5.2_archive: write the pathnames of the log files no longer in use.
+ - db5.2_checkpoint: daemon process to monitor the database log and
checkpoint it periodically.
- - db5.1_deadlock: traverse the database environment lock region and
+ - db5.2_deadlock: traverse the database environment lock region and
abort lock requests when a deadlock is detected.
- - db5.1_load: loads (and creates) a database from standard input.
- - db5.1_dump: read a database file and write it in a format understood
+ - db5.2_load: loads (and creates) a database from standard input.
+ - db5.2_dump: read a database file and write it in a format understood
by db4.{2..8}_load.
- - db5.1_printlog: dump log files in human readable format.
- - db5.1_stat: display statistics for Berkeley DB environments.
- - db5.1_upgrade: upgrades the version of files and the databases they
+ - db5.2_printlog: dump log files in human readable format.
+ - db5.2_stat: display statistics for Berkeley DB environments.
+ - db5.2_upgrade: upgrades the version of files and the databases they
contain.
- - db5.1_verify: check the structure of files and their databases.
+ - db5.2_verify: check the structure of files and their databases.
-Package: db5.1-sql-util
+Package: db5.2-sql-util
Architecture: any
Section: database
Priority: extra
Depends: ${shlibs:Depends},
${misc:Depends}
-Description: Berkeley v5.1 SQL Database Utilities
+Description: Berkeley v5.2 SQL Database Utilities
This package provides different tools for manipulating databases
- in the Berkeley v5.1 SQL database format, and includes:
- - db5.1
+ in the Berkeley v5.2 SQL database format, and includes:
+ - db5.2_sql: sqlite compatible command-line utility
-Package: libdb5.1++
+Package: libdb5.2++
Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends},
${misc:Depends}
Priority: optional
-Description: Berkeley v5.1 Database Libraries for C++ [runtime]
- This is the runtime package for programs that use the Berkeley v5.1
+Description: Berkeley v5.2 Database Libraries for C++ [runtime]
+ This is the runtime package for programs that use the Berkeley v5.2
database library. This is only for programs which use the C++ interface.
-Package: libdb5.1++-dev
+Package: libdb5.2++-dev
Architecture: any
Section: libdevel
Priority: extra
-Depends: libdb5.1++ (= ${binary:Version}),
- libdb5.1-dev (= ${binary:Version}),
+Depends: libdb5.2++ (= ${binary:Version}),
+ libdb5.2-dev (= ${binary:Version}),
${misc:Depends}
-Conflicts: libdb4.6++-dev, libdb4.7++-dev, libdb4.8++-dev
-Description: Berkeley v5.1 Database Libraries for C++ [development]
+Conflicts: libdb4.6++-dev, libdb4.7++-dev, libdb4.8++-dev, libdb5.1++-dev
+Description: Berkeley v5.2 Database Libraries for C++ [development]
This is the development package which contains headers and static
- libraries for the Berkeley v5.1 database library. This is only for
+ libraries for the Berkeley v5.2 database library. This is only for
programs which will use the C++ interface.
-Package: libdb5.1-tcl
+Package: libdb5.2-tcl
Architecture: any
Section: interpreters
Priority: extra
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
-Conflicts: libdb4.6-tcl, libdb4.7-tcl, libdb4.8-tcl
+Conflicts: libdb4.6-tcl, libdb4.7-tcl, libdb4.8-tcl, libdb5.1-tcl
Depends: ${tcl:Depends},
${shlibs:Depends},
${misc:Depends}
-Description: Berkeley v5.1 Database Libraries for Tcl [module]
- This package provides a Tcl module suitable for accessing Berkeley v5.1
+Description: Berkeley v5.2 Database Libraries for Tcl [module]
+ This package provides a Tcl module suitable for accessing Berkeley v5.2
databases from within Tcl programs.
-Package: libdb5.1-dbg
+Package: libdb5.2-dbg
Architecture: any
Section: debug
Priority: extra
-Depends: libdb5.1 (= ${binary:Version}),
+Depends: libdb5.2 (= ${binary:Version}),
${misc:Depends}
Multi-Arch: same
-Description: Berkeley v5.1 Database Libraries [debug]
- This package provides the debug symbols for the Berkeley v5.1 database
+Description: Berkeley v5.2 Database Libraries [debug]
+ This package provides the debug symbols for the Berkeley v5.2 database
libraries and binaries.
-Package: libdb5.1-java
+Package: libdb5.2-java
Architecture: any
Section: java
Priority: optional
Depends: ${shlibs:Depends},
${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
-Recommends: libdb5.1-java-gcj
+Recommends: libdb5.2-java-gcj
Multi-Arch: same
-Description: Berkeley v5.1 Database Libraries for Java
- This package provides the Java interface for the Berkeley v5.1 database
+Description: Berkeley v5.2 Database Libraries for Java
+ This package provides the Java interface for the Berkeley v5.2 database
library.
-Package: libdb5.1-java-gcj
+Package: libdb5.2-java-gcj
Architecture: any
Section: java
Priority: optional
-Depends: libdb5.1-java (= ${binary:Version}),
+Depends: libdb5.2-java (= ${binary:Version}),
${shlibs:Depends},
${misc:Depends}
-Description: Berkeley v5.1 Database Libraries for Java (native code)
- This package provides the Java interface for the Berkeley v5.1 database
+Description: Berkeley v5.2 Database Libraries for Java (native code)
+ This package provides the Java interface for the Berkeley v5.2 database
library.
.
This package contains the natively compiled code for use by gij.
-Package: libdb5.1-java-dev
+Package: libdb5.2-java-dev
Architecture: any
Section: libdevel
Priority: optional
-Depends: libdb5.1-java (= ${binary:Version}),
+Depends: libdb5.2-java (= ${binary:Version}),
${shlibs:Depends},
${misc:Depends}
-Conflicts: libdb4.6-java-dev, libdb4.7-java-dev, libdb4.8-java-dev
-Description: Berkeley v5.1 Database Libraries for Java [development]
- This package provides the Java interface for the Berkeley v5.1 database
+Conflicts: libdb4.6-java-dev, libdb4.7-java-dev, libdb4.8-java-dev, libdb5.1-java-dev
+Description: Berkeley v5.2 Database Libraries for Java [development]
+ This package provides the Java interface for the Berkeley v5.2 database
library.
-Package: libdb5.1-sql-dev
+Package: libdb5.2-sql-dev
Architecture: any
Section: libdevel
Priority: extra
-Depends: libdb5.1-sql (= ${binary:Version}),
+Depends: libdb5.2-sql (= ${binary:Version}),
${misc:Depends}
-Suggests: db5.1-doc
-Description: Berkeley v5.1 Database Libraries [SQL development]
+Suggests: db5.2-doc
+Description: Berkeley v5.2 Database Libraries [SQL development]
This is the development package which contains headers and static
- libraries for the Berkeley v5.1 database library.
+ libraries for the Berkeley v5.2 database library.
-Package: libdb5.1-sql
+Package: libdb5.2-sql
Architecture: any
Priority: extra
Depends: ${shlibs:Depends},
${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
Multi-Arch: same
-Description: Berkeley v5.1 Database Libraries [SQL runtime]
- This is the runtime package for programs that use the v5.1 Berkeley
+Description: Berkeley v5.2 Database Libraries [SQL runtime]
+ This is the runtime package for programs that use the v5.2 Berkeley
database SQL library.
-Package: libdb5.1-stl-dev
+Package: libdb5.2-stl-dev
Architecture: any
Section: libdevel
Priority: extra
-Depends: libdb5.1-stl (= ${binary:Version}),
+Depends: libdb5.2-stl (= ${binary:Version}),
${misc:Depends}
-Suggests: db5.1-doc
-Description: Berkeley v5.1 Database Libraries [STL development]
+Suggests: db5.2-doc
+Description: Berkeley v5.2 Database Libraries [STL development]
This is the development package which contains headers and static
- libraries for the Berkeley v5.1 database library.
+ libraries for the Berkeley v5.2 database library.
-Package: libdb5.1-stl
+Package: libdb5.2-stl
Architecture: any
Priority: extra
Depends: ${shlibs:Depends},
${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
Multi-Arch: same
-Description: Berkeley v5.1 Database Libraries [STL runtime]
- This is the runtime package for programs that use the v5.1 Berkeley
+Description: Berkeley v5.2 Database Libraries [STL runtime]
+ This is the runtime package for programs that use the v5.2 Berkeley
database STL library.
diff --git a/debian/db5.1-sql-util.install b/debian/db5.1-sql-util.install
deleted file mode 100644
index eec6063..0000000
--- a/debian/db5.1-sql-util.install
+++ /dev/null
@@ -1 +0,0 @@
-/usr/bin/db5.1_sql
diff --git a/debian/db5.1-util.install b/debian/db5.1-util.install
deleted file mode 100644
index 55e09fb..0000000
--- a/debian/db5.1-util.install
+++ /dev/null
@@ -1,13 +0,0 @@
-usr/bin/db5.1_archive
-usr/bin/db5.1_checkpoint
-usr/bin/db5.1_deadlock
-usr/bin/db5.1_dump
-usr/bin/db5.1_hotbackup
-usr/bin/db5.1_load
-usr/bin/db5.1_log_verify
-usr/bin/db5.1_printlog
-usr/bin/db5.1_recover
-usr/bin/db5.1_replicate
-usr/bin/db5.1_stat
-usr/bin/db5.1_upgrade
-usr/bin/db5.1_verify
diff --git a/debian/db5.1-doc.docs b/debian/db5.2-doc.docs
similarity index 100%
rename from debian/db5.1-doc.docs
rename to debian/db5.2-doc.docs
diff --git a/debian/db5.1-sql-util.dirs b/debian/db5.2-sql-util.dirs
similarity index 100%
rename from debian/db5.1-sql-util.dirs
rename to debian/db5.2-sql-util.dirs
diff --git a/debian/db5.2-sql-util.install b/debian/db5.2-sql-util.install
new file mode 100644
index 0000000..22d2f9b
--- /dev/null
+++ b/debian/db5.2-sql-util.install
@@ -0,0 +1 @@
+/usr/bin/db5.2_sql
diff --git a/debian/db5.1-util.dirs b/debian/db5.2-util.dirs
similarity index 100%
rename from debian/db5.1-util.dirs
rename to debian/db5.2-util.dirs
diff --git a/debian/db5.2-util.install b/debian/db5.2-util.install
new file mode 100644
index 0000000..5d2b258
--- /dev/null
+++ b/debian/db5.2-util.install
@@ -0,0 +1,13 @@
+usr/bin/db5.2_archive
+usr/bin/db5.2_checkpoint
+usr/bin/db5.2_deadlock
+usr/bin/db5.2_dump
+usr/bin/db5.2_hotbackup
+usr/bin/db5.2_load
+usr/bin/db5.2_log_verify
+usr/bin/db5.2_printlog
+usr/bin/db5.2_recover
+usr/bin/db5.2_replicate
+usr/bin/db5.2_stat
+usr/bin/db5.2_upgrade
+usr/bin/db5.2_verify
diff --git a/debian/db5.1-util.manpages b/debian/db5.2-util.manpages
similarity index 100%
rename from debian/db5.1-util.manpages
rename to debian/db5.2-util.manpages
diff --git a/debian/libdb5.1++.lintian-overrides b/debian/libdb5.1++.lintian-overrides
deleted file mode 100644
index 2d9136e..0000000
--- a/debian/libdb5.1++.lintian-overrides
+++ /dev/null
@@ -1,2 +0,0 @@
-# historical reasons
-libdb5.1++: package-name-doesnt-match-sonames libdb-cxx-5.1
\ No newline at end of file
diff --git a/debian/libdb5.1-java.install b/debian/libdb5.1-java.install
deleted file mode 100644
index ba00d13..0000000
--- a/debian/libdb5.1-java.install
+++ /dev/null
@@ -1 +0,0 @@
-usr/lib/*/libdb_java-5.1*.so
diff --git a/debian/libdb5.1-java.lintian-overrides b/debian/libdb5.1-java.lintian-overrides
deleted file mode 100644
index bafd867..0000000
--- a/debian/libdb5.1-java.lintian-overrides
+++ /dev/null
@@ -1,2 +0,0 @@
-# historical reasons
-libdb5.1-java: package-name-doesnt-match-sonames libdb-java-5.1
diff --git a/debian/libdb5.1-sql.lintian-overrides b/debian/libdb5.1-sql.lintian-overrides
deleted file mode 100644
index e555242..0000000
--- a/debian/libdb5.1-sql.lintian-overrides
+++ /dev/null
@@ -1,4 +0,0 @@
-# historical reasons
-libdb5.1-sql: package-name-doesnt-match-sonames libdb-sql-5.1
-# not true, libdb5.1-sql provides sqlite3 ABI
-libdb5.1-sql: embedded-library * sqlite
diff --git a/debian/libdb5.1-stl.lintian-overrides b/debian/libdb5.1-stl.lintian-overrides
deleted file mode 100644
index bc9ba1f..0000000
--- a/debian/libdb5.1-stl.lintian-overrides
+++ /dev/null
@@ -1,2 +0,0 @@
-# historical reasons
-libdb5.1-stl: package-name-doesnt-match-sonames libdb-stl-5.1
\ No newline at end of file
diff --git a/debian/libdb5.1-tcl.lintian-overrides b/debian/libdb5.1-tcl.lintian-overrides
deleted file mode 100644
index 81ed531..0000000
--- a/debian/libdb5.1-tcl.lintian-overrides
+++ /dev/null
@@ -1,2 +0,0 @@
-# historical reasons
-libdb5.1-tcl: package-name-doesnt-match-sonames libdb-tcl-5.1
diff --git a/debian/libdb5.1.lintian-overrides b/debian/libdb5.1.lintian-overrides
deleted file mode 100644
index 97fead0..0000000
--- a/debian/libdb5.1.lintian-overrides
+++ /dev/null
@@ -1,2 +0,0 @@
-# historical reasons
-libdb5.1: package-name-doesnt-match-sonames libdb-5.1
diff --git a/debian/libdb5.1++-dev.dirs b/debian/libdb5.2++-dev.dirs
similarity index 100%
rename from debian/libdb5.1++-dev.dirs
rename to debian/libdb5.2++-dev.dirs
diff --git a/debian/libdb5.1++-dev.install b/debian/libdb5.2++-dev.install
similarity index 100%
rename from debian/libdb5.1++-dev.install
rename to debian/libdb5.2++-dev.install
diff --git a/debian/libdb5.1++.dirs b/debian/libdb5.2++.dirs
similarity index 100%
rename from debian/libdb5.1++.dirs
rename to debian/libdb5.2++.dirs
diff --git a/debian/libdb5.1++.install b/debian/libdb5.2++.install
similarity index 100%
rename from debian/libdb5.1++.install
rename to debian/libdb5.2++.install
diff --git a/debian/libdb5.2++.lintian-overrides b/debian/libdb5.2++.lintian-overrides
new file mode 100644
index 0000000..597848e
--- /dev/null
+++ b/debian/libdb5.2++.lintian-overrides
@@ -0,0 +1,2 @@
+# historical reasons
+libdb5.2++: package-name-doesnt-match-sonames libdb-cxx-5.2
\ No newline at end of file
diff --git a/debian/libdb5.1-dev.dirs b/debian/libdb5.2-dev.dirs
similarity index 100%
rename from debian/libdb5.1-dev.dirs
rename to debian/libdb5.2-dev.dirs
diff --git a/debian/libdb5.1-dev.install b/debian/libdb5.2-dev.install
similarity index 100%
rename from debian/libdb5.1-dev.install
rename to debian/libdb5.2-dev.install
diff --git a/debian/libdb5.1-java-dev.dirs b/debian/libdb5.2-java-dev.dirs
similarity index 100%
rename from debian/libdb5.1-java-dev.dirs
rename to debian/libdb5.2-java-dev.dirs
diff --git a/debian/libdb5.1-java-dev.install b/debian/libdb5.2-java-dev.install
similarity index 100%
rename from debian/libdb5.1-java-dev.install
rename to debian/libdb5.2-java-dev.install
diff --git a/debian/libdb5.1-java-gcj.dirs b/debian/libdb5.2-java-gcj.dirs
similarity index 100%
rename from debian/libdb5.1-java-gcj.dirs
rename to debian/libdb5.2-java-gcj.dirs
diff --git a/debian/libdb5.1-java.dirs b/debian/libdb5.2-java.dirs
similarity index 100%
rename from debian/libdb5.1-java.dirs
rename to debian/libdb5.2-java.dirs
diff --git a/debian/libdb5.2-java.install b/debian/libdb5.2-java.install
new file mode 100644
index 0000000..f1e0671
--- /dev/null
+++ b/debian/libdb5.2-java.install
@@ -0,0 +1 @@
+usr/lib/*/libdb_java-5.2*.so
diff --git a/debian/libdb5.1-java.jlibs b/debian/libdb5.2-java.jlibs
similarity index 100%
rename from debian/libdb5.1-java.jlibs
rename to debian/libdb5.2-java.jlibs
diff --git a/debian/libdb5.2-java.lintian-overrides b/debian/libdb5.2-java.lintian-overrides
new file mode 100644
index 0000000..23db31a
--- /dev/null
+++ b/debian/libdb5.2-java.lintian-overrides
@@ -0,0 +1,2 @@
+# historical reasons
+libdb5.2-java: package-name-doesnt-match-sonames libdb-java-5.2
diff --git a/debian/libdb5.1-sql-dev.dirs b/debian/libdb5.2-sql-dev.dirs
similarity index 100%
rename from debian/libdb5.1-sql-dev.dirs
rename to debian/libdb5.2-sql-dev.dirs
diff --git a/debian/libdb5.1-sql-dev.install b/debian/libdb5.2-sql-dev.install
similarity index 100%
rename from debian/libdb5.1-sql-dev.install
rename to debian/libdb5.2-sql-dev.install
diff --git a/debian/libdb5.1-sql.dirs b/debian/libdb5.2-sql.dirs
similarity index 100%
rename from debian/libdb5.1-sql.dirs
rename to debian/libdb5.2-sql.dirs
diff --git a/debian/libdb5.1-sql.install b/debian/libdb5.2-sql.install
similarity index 100%
rename from debian/libdb5.1-sql.install
rename to debian/libdb5.2-sql.install
diff --git a/debian/libdb5.2-sql.lintian-overrides b/debian/libdb5.2-sql.lintian-overrides
new file mode 100644
index 0000000..54209d1
--- /dev/null
+++ b/debian/libdb5.2-sql.lintian-overrides
@@ -0,0 +1,4 @@
+# historical reasons
+libdb5.2-sql: package-name-doesnt-match-sonames libdb-sql-5.2
+# not true, libdb5.2-sql provides sqlite3 ABI
+libdb5.2-sql: embedded-library * sqlite
diff --git a/debian/libdb5.1-stl-dev.dirs b/debian/libdb5.2-stl-dev.dirs
similarity index 100%
rename from debian/libdb5.1-stl-dev.dirs
rename to debian/libdb5.2-stl-dev.dirs
diff --git a/debian/libdb5.1-stl-dev.install b/debian/libdb5.2-stl-dev.install
similarity index 100%
rename from debian/libdb5.1-stl-dev.install
rename to debian/libdb5.2-stl-dev.install
diff --git a/debian/libdb5.1-stl.dirs b/debian/libdb5.2-stl.dirs
similarity index 100%
rename from debian/libdb5.1-stl.dirs
rename to debian/libdb5.2-stl.dirs
diff --git a/debian/libdb5.1-stl.install b/debian/libdb5.2-stl.install
similarity index 100%
rename from debian/libdb5.1-stl.install
rename to debian/libdb5.2-stl.install
diff --git a/debian/libdb5.2-stl.lintian-overrides b/debian/libdb5.2-stl.lintian-overrides
new file mode 100644
index 0000000..2a97c2e
--- /dev/null
+++ b/debian/libdb5.2-stl.lintian-overrides
@@ -0,0 +1,2 @@
+# historical reasons
+libdb5.2-stl: package-name-doesnt-match-sonames libdb-stl-5.2
\ No newline at end of file
diff --git a/debian/libdb5.1-tcl.dirs b/debian/libdb5.2-tcl.dirs
similarity index 100%
rename from debian/libdb5.1-tcl.dirs
rename to debian/libdb5.2-tcl.dirs
diff --git a/debian/libdb5.1-tcl.install b/debian/libdb5.2-tcl.install
similarity index 100%
rename from debian/libdb5.1-tcl.install
rename to debian/libdb5.2-tcl.install
diff --git a/debian/libdb5.2-tcl.lintian-overrides b/debian/libdb5.2-tcl.lintian-overrides
new file mode 100644
index 0000000..22b011f
--- /dev/null
+++ b/debian/libdb5.2-tcl.lintian-overrides
@@ -0,0 +1,2 @@
+# historical reasons
+libdb5.2-tcl: package-name-doesnt-match-sonames libdb-tcl-5.2
diff --git a/debian/libdb5.1.dirs b/debian/libdb5.2.dirs
similarity index 100%
rename from debian/libdb5.1.dirs
rename to debian/libdb5.2.dirs
diff --git a/debian/libdb5.1.docs b/debian/libdb5.2.docs
similarity index 100%
rename from debian/libdb5.1.docs
rename to debian/libdb5.2.docs
diff --git a/debian/libdb5.1.install b/debian/libdb5.2.install
similarity index 100%
rename from debian/libdb5.1.install
rename to debian/libdb5.2.install
diff --git a/debian/libdb5.2.lintian-overrides b/debian/libdb5.2.lintian-overrides
new file mode 100644
index 0000000..8c97bfb
--- /dev/null
+++ b/debian/libdb5.2.lintian-overrides
@@ -0,0 +1,2 @@
+# historical reasons
+libdb5.2: package-name-doesnt-match-sonames libdb-5.2
diff --git a/debian/manpages/berkeley_db5.1_svc.1 b/debian/manpages/berkeley_db5.1_svc.1
deleted file mode 100644
index 89895cf..0000000
--- a/debian/manpages/berkeley_db5.1_svc.1
+++ /dev/null
@@ -1,59 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH BERKELEY_DB5.1_SVC 1 "28 January 2005"
-.SH NAME
-berkeley_db5.1_svc \- Berkeley DB RPC server
-.SH SYNOPSIS
-.B berkeley_db5.1_svc
-[-Vv] [-h home] [-I seconds] [-L file] [-t seconds] [-T seconds]
-.SH DESCRIPTION
-The berkeley_db5.1_svc utility is the Berkeley DB RPC server.
-.SH OPTIONS
-.IP \fB\-h\fR
-Add the specified home directory to the list of allowed home directories
-that can be specified by the client. The home directory should be an
-absolute pathname. The last component of each home directory specified
-must be unique because that is how clients specify which database environment
-they want to join.
-.sp
-Recovery will be run on each specified environment before the server
-begins accepting requests from clients. For this reason, only one copy
-of the server program should ever be run at any time because recovery
-must always be single-threaded.
-.IP \fB\-I\fR
-Set the default idle timeout for client environments to the specified
-number of seconds. The default timeout is 24 hours.
-.IP \fB\-L\fR
-Log the execution of the berkeley_db5.1_svc utility to the specified file in the
-following format, where \fI###\fR is the process ID, and the date
-is the time the utility was started.
-.sp
-berkeley_db5.1_svc: ### Wed Jun 15 01:23:45 EDT 1995
-.sp
-This file will be removed if the berkeley_db5.1_svc utility exits gracefully.
-.IP \fB\-t\fR
-Set the default timeout for client resources (idle transactions and
-cursors) to the specified number of seconds. When the timeout expires,
-if the resource is a transaction, it is aborted; if the resource is a
-cursor, it is closed. The default timeout is 5 minutes.
-.IP \fB\-T\fR
-Set the maximum timeout allowed for client resources. The default
-timeout is 20 minutes. If a client application requests a server
-timeout greater than the maximum timeout set for this server, the
-client's timeout will be capped at the maximum timeout value.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.IP \fB\-v\fR
-Run in verbose mode.
-.PP
-The berkeley_db5.1_svc utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for berkeley_db_svc from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/berkeley_db5.2_svc.1 b/debian/manpages/berkeley_db5.2_svc.1
new file mode 100644
index 0000000..b1d45bb
--- /dev/null
+++ b/debian/manpages/berkeley_db5.2_svc.1
@@ -0,0 +1,59 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH BERKELEY_DB5.2_SVC 1 "28 January 2005"
+.SH NAME
+berkeley_db5.2_svc \- Berkeley DB RPC server
+.SH SYNOPSIS
+.B berkeley_db5.2_svc
+[-Vv] [-h home] [-I seconds] [-L file] [-t seconds] [-T seconds]
+.SH DESCRIPTION
+The berkeley_db5.2_svc utility is the Berkeley DB RPC server.
+.SH OPTIONS
+.IP \fB\-h\fR
+Add the specified home directory to the list of allowed home directories
+that can be specified by the client. The home directory should be an
+absolute pathname. The last component of each home directory specified
+must be unique because that is how clients specify which database environment
+they want to join.
+.sp
+Recovery will be run on each specified environment before the server
+begins accepting requests from clients. For this reason, only one copy
+of the server program should ever be run at any time because recovery
+must always be single-threaded.
+.IP \fB\-I\fR
+Set the default idle timeout for client environments to the specified
+number of seconds. The default timeout is 24 hours.
+.IP \fB\-L\fR
+Log the execution of the berkeley_db5.2_svc utility to the specified file in the
+following format, where \fI###\fR is the process ID, and the date
+is the time the utility was started.
+.sp
+berkeley_db5.2_svc: ### Wed Jun 15 01:23:45 EDT 1995
+.sp
+This file will be removed if the berkeley_db5.2_svc utility exits gracefully.
+.IP \fB\-t\fR
+Set the default timeout for client resources (idle transactions and
+cursors) to the specified number of seconds. When the timeout expires,
+if the resource is a transaction, it is aborted; if the resource is a
+cursor, it is closed. The default timeout is 5 minutes.
+.IP \fB\-T\fR
+Set the maximum timeout allowed for client resources. The default
+timeout is 20 minutes. If a client application requests a server
+timeout greater than the maximum timeout set for this server, the
+client's timeout will be capped at the maximum timeout value.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.IP \fB\-v\fR
+Run in verbose mode.
+.PP
+The berkeley_db5.2_svc utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for berkeley_db_svc from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_archive.1 b/debian/manpages/db5.1_archive.1
deleted file mode 100644
index 83eea33..0000000
--- a/debian/manpages/db5.1_archive.1
+++ /dev/null
@@ -1,95 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_ARCHIVE 1 "28 January 2005"
-.SH NAME
-db5.1_archive \- Find unused log files for archiving purposes
-.SH SYNOPSIS
-.B db5.1_archive
-[-adlsVv] [-h home] [-P password]
-.SH DESCRIPTION
-The db5.1_archive utility writes the pathnames of log files that
-are no longer in use (for example, no longer involved in active
-transactions), to the standard output, one pathname per line. These
-log files should be written to backup media to provide for recovery in
-the case of catastrophic failure (which also requires a snapshot of the
-database files), but they may then be deleted from the system to reclaim
-disk space.
-.SH OPTIONS
-.PP
-.IP \fB\-a\fR
-Write all pathnames as absolute pathnames, instead of relative to the
-database home directories.
-.IP \fB\-d\fR
-Remove log files that are no longer needed; no filenames are written.
-Automatic log file removal is likely to make catastrophic recovery
-impossible.
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-l\fR
-Write out the pathnames of all the database log files, whether or not
-they are involved in active transactions.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-s\fR
-Write the pathnames of all the database files that need to be archived
-in order to recover the database from catastrophic failure. If any of
-the database files have not been accessed during the lifetime of the
-current log files, db5.1_archive will not include them in this
-output.
-.sp
-It is possible that some of the files to which the log refers have since
-been deleted from the system. In this case, db5.1_archive will
-ignore them. When db5.1_recover is run, any files to which the
-log refers that are not present during recovery are assumed to have been
-deleted and will not be recovered.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.IP \fB\-v\fR
-Run in verbose mode, listing the checkpoints in the log files as they
-are reviewed.
-.PP
-Log cursor handles (returned by the DB_ENV->log_cursor method) may have open
-file descriptors for log files in the database environment. Also, the
-Berkeley DB interfaces to the database environment logging subsystem (for
-example, DB_ENV->log_put and DB_TXN->abort) may allocate log cursors
-and have open file descriptors for log files as well. On operating
-systems where filesystem related system calls (for example, rename and
-unlink on Windows/NT) can fail if a process has an open file descriptor
-for the affected file, attempting to move or remove the log files listed
-by db5.1_archive may fail. All Berkeley DB internal use of log cursors
-operates on active log files only and furthermore, is short-lived in
-nature. So, an application seeing such a failure should be restructured
-to close any open log cursors it may have, and otherwise to retry the
-operation until it succeeds. (Although the latter is not likely to be
-necessary; it is hard to imagine a reason to move or rename a log file
-in which transactions are being logged or aborted.)
-.PP
-The db5.1_archive utility uses a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_archive should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_archive
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The DB_ENV->log_archive method is the underlying method used by the db5.1_archive utility.
-See the db5.1_archive utility source code for an example of using
-DB_ENV->log_archive in a IEEE/ANSI Std 1003.1 (POSIX) environment.
-.PP
-The db5.1_archive utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_archive from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_checkpoint.1 b/debian/manpages/db5.1_checkpoint.1
deleted file mode 100644
index 21b56b5..0000000
--- a/debian/manpages/db5.1_checkpoint.1
+++ /dev/null
@@ -1,78 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_CHECKPOINT 1 "28 January 2005"
-.SH NAME
-db5.1_checkpoint \- Periodically checkpoint transactions
-.SH SYNOPSIS
-.B db5.1_checkpoint
-[-1Vv] [-h home] [-k kbytes] [-L file] [-P password] [-p min]
-.SH DESCRIPTION
-The db5.1_checkpoint utility is a daemon process that monitors the database log,
-and periodically calls DB_ENV->txn_checkpoint to checkpoint it.
-.SH OPTIONS
-.IP \fB\-1\fR
-Checkpoint the log once, regardless of whether or not there has been
-activity since the last checkpoint and then exit.
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-k\fR
-Checkpoint the database at least as often as every \fBkbytes\fR of log
-file are written.
-.IP \fB\-L\fR
-Log the execution of the db5.1_checkpoint utility to the specified file in the
-following format, where \fI###\fR is the process ID, and the date
-is the time the utility was started.
-.sp
-.TP 8
-db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995
-.sp
-This file will be removed if the db5.1_checkpoint utility exits gracefully.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-p\fR
-Checkpoint the database at least every \fBmin\fR minutes if there has
-been any activity since the last checkpoint.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.IP \fB\-v\fR
-Write the time of each checkpoint attempt to the standard output.
-.PP
-At least one of the \fB-1\fR, \fB-k\fR, and \fB-p\fR options
-must be specified.
-.PP
-The db5.1_checkpoint utility uses a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_checkpoint should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_checkpoint
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_checkpoint utility does not attempt to create the Berkeley DB
-shared memory regions if they do not already exist. The application
-that creates the region should be started first, and once the region is
-created, the db5.1_checkpoint utility should be started.
-.PP
-The DB_ENV->txn_checkpoint method is the underlying method used by the
-db5.1_checkpoint utility. See the db_checkpoint utility source code for an
-example of using DB_ENV->txn_checkpoint in a IEEE/ANSI Std 1003.1
-(POSIX) environment.
-.PP
-The db5.1_checkpoint utility exits 0 on success, and >0 if an error occurs.
-.PP
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_checkpoint from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_codegen.1 b/debian/manpages/db5.1_codegen.1
deleted file mode 100644
index ab73d93..0000000
--- a/debian/manpages/db5.1_codegen.1
+++ /dev/null
@@ -1,319 +0,0 @@
-.\" Copyright \(co 2010 by Thorsten Glaser <tg at debian.org>
-.\" <!--$Id: db_codegen.so,v 10.6 2007/05/17 18:29:34 bostic Exp $-->
-.\" <!--Copyright (c) 1997,2008 Oracle. All rights reserved.-->
-.\" <!--See the file LICENSE for redistribution information.-->
-.\"
-.Dd January 12, 2011
-.Dt DB5.1_CODEGEN 1
-.Os "Berkeley DB"
-.Sh NAME
-.Nm db5.1_codegen
-.Nd generate application code for Berkeley DB
-.Sh SYNOPSIS
-.Nm
-.Op Fl Vv
-.Op Fl a Ar api
-.Op Fl i Ar file
-.Op Fl o Ar prefix
-.Sh DESCRIPTION
-The
-.Nm
-utility generates application code to create and configure
-Berkeley DB database environments and databases based on a simple
-description language and writes it to one or more output files.
-The generated code may need modification, in the case of complicated
-applications, but will usually significantly reduce the time required
-to create Berkeley DB applications.
-.Pp
-The options are as follows:
-.Bl -tag -width XXX
-.It Fl a Ar api
-Generate code for the specified API
-.Pq currently, only Do c Dc is accepted .
-.It Fl i Ar file
-Specify an input
-.Ar file ;
-by default, standard input is used.
-.It Fl o Ar prefix
-Specify an output file
-.Ar prefix ;
-by default,
-.Dq application
-is used.
-.It Fl V
-Write the library version number to standard output and exit.
-.It Fl v
-Run in verbose mode.
-.El
-.Pp
-The
-.Nm
-utility exits 0 on success, and >0 if an error occurs.
-.Sh C Language Specific Information
-By default, when the
-.Nm
-utility generates C-language code, the output file is named
-.Dq Pa application.c .
-The output filename can be specified with the
-.Fl o
-option.
-.Pp
-At the beginning of the output file is a list of public database environment
-.Pq Vt DB_ENV
-handles and database
-.Pq Vt DB
-handles, as specified by the description language.
-The database environment handle variables are named
-.Dq Ar XXX Ns _dbenv ,
-where
-.Dq Ar XXX
-is the name of the environment in the input specification.
-For databases associated with a database environment, the database
-handle variables are named
-.Dq Ar XXX Ns _ Ns Ar YYY ,
-where
-.Dq Ar XXX
-is the name of the environment, and
-.Dq Ar YYY
-is the name of the database.
-For standalone databases, the database handle variables are named
-.Dq Ar XXX ,
-where
-.Dq Ar XXX
-is the name of the database.
-.Pp
-There are two public functions in the output file:
-.Fn bdb_startup
-and
-.Fn bdb_shutdown .
-The
-.Fn bdb_startup
-function should be called to create and configure the database
-environments and databases, and the
-.Fn bdb_shutdown
-function should be called to gracefully shut down the environments
-and databases.
-.Sh Specification Language
-The
-.Nm
-uses a simple description language:
-.Pp
-.Bl -bullet -compact
-.It
-Lines in the input consist of white-space separated tokens.
-.It
-Tokens are case-insensitive.
-.It
-Empty lines and lines where the first non-space character is a hash mark
-.Pq Dq \&#
-are ignored.
-In addition, hash marks may appear in lines, in which case the content
-of the line from the hash mark to the end of the line is ignored.
-.El
-.Pp
-There are two top-level objects:
-.Dq environment
-and
-.Dq database ,
-which correspond to database environments and databases, respectively.
-These top-level objects can be associated with keywords to describe
-their configuration and relationships.
-.Pp
-For example, the following input would create two standalone databases:
-.Bd -literal -offset indent
-database data_one {
- type btree
-}
-database data_two {
- type btree
-}
-.Ed
-.Pp
-In this case, there would be no
-.Vt DB_ENV
-handle, and the public
-.Vt DB
-handles would be:
-.Bd -literal -offset indent
-DB *data_one;
-DB *data_two;
-.Ed
-.Pp
-For example, the following input would create a database environment which
-contains three databases:
-.Bd -literal -offset indent
-environment myenv {
- database data_one {
- type btree
- }
- database data_two {
- type btree
- }
- database data_three {
- type btree
- }
-}
-.Ed
-.Pp
-In this case, the public
-.Vt DB_ENV
-and
-.Vt DB
-handles would be:
-.Bd -literal -offset indent
-DB_ENV *myenv_dbenv;
-DB *myenv_data_one;
-DB *myenv_data_two;
-DB *myenv_data_three;
-.Ed
-.Pp
-A variety of keywords can be specified for the databases and the environments.
-For example, the cache size can be specified for the database environment,
-and the page size can be specified for the database, as well as for secondary
-relationships:
-.Bd -literal -offset indent
-environment myenv {
- cachesize 2 0 10
- database data_one {
- type btree
- pagesize 1024
- }
- database data_two {
- primary data_one
- secondary_offset 10 15
- type btree
- pagesize 32768
- }
- database data_three {
- type btree
- pagesize 512
- }
-}
-.Ed
-.Ss Environment Keywords
-.Bl -tag -width secondary_offset
-.It Ic environment
-Start a database environment block.
-.Pp
-There must be three tokens on the line: the keyword, the name of the
-environment and an opening brace
-.Pq Dq \&{ .
-.It Ic home
-Specify the database environment home directory.
-.Pp
-There must be two tokens on the line: the keyword and the home directory.
-.It Ic cachesize
-Specify the database environment cache size.
-.Pp
-There must be two tokens on the line: the keyword, the gigabytes of cache,
-the bytes of cache, and the number of caches (the number of underlying
-physical areas into which the cache is logically divided).
-.It Ic private
-Specify the database environment is private.
-.Pp
-There must be one token on the line: the keyword by itself.
-.It Ic \&}
-End the database environment block.
-.Pp
-There must be one token on the line: the keyword by itself.
-.El
-.Ss Database Keywords
-.Bl -tag -width secondary_offset
-.It Ic database
-Start a database block.
-.Pp
-There must be three tokens on the line: the keyword, the name of the
-database and an opening brace
-.Pq Dq \&{ .
-.It Ic custom
-Specify a custom key-comparison routine.
-This is used when the Btree database requires a specific sort that
-.Nm
-cannot generate.
-A stub key comparison routine will be created and configured for the
-database which should be modified as necessary.
-See the
-.Dq Ic key_type
-keyword for more information.
-.Pp
-There must be one token on the line: the keyword by itself.
-.It Ic dupsort
-Configure the database to support sorted duplicates.
-.Pp
-There must be one token on the line: the keyword by itself.
-.It Ic extentsize
-Configure the size of the Queue database extent files.
-.Pp
-There must be two tokens on the line: the keyword and the extent file
-size, as a number of pages.
-.It Ic key_type
-Configure a integral type key-comparison routine.
-This is used when the Btree database key is an integral type (such as
-.Dq Vt "unsigned int"
-or
-.Dq Vt u_int32_t ) .
-Any C-language integral type may be specified.
-See the
-.Dq Ic custom
-keyword for more information.
-A Btree comparison routine based on the type of the key will be
-created and configured.
-.Pp
-There must be two tokens on the line: the keyword and the type.
-.It Ic pagesize
-Configure the database page size.
-.Pp
-There must be two tokens on the line: the keyword and the page size in bytes.
-.It Ic primary
-Configure the database as a secondary index.
-A stub secondary callback routine will be created and configured for the
-database, which should be modified as necessary.
-See the
-.Dq Ic secondary_offset
-keyword for more information.
-.Pp
-There must be two tokens on the line: the keyword and the
-name of the primary database for which this database is a secondary.
-.It Ic recnum
-Configure the Btree database to support record number access.
-.Pp
-There must be one token on the line: the keyword by itself.
-.It Ic re_len
-Configure the record length for a Queue database or a fixed-length
-Recno database.
-.Pp
-There must be two tokens on the line: the keyword and the length
-of a record, in bytes.
-.Pp
-.It Ic secondary_offset
-Configure a secondary callback routine based on a byte string found
-in the primary database's data item.
-.Pp
-There must be three tokens on the line: the keyword, the byte offset from
-the beginning of the primary data item where the secondary key occurs, and
-the length of the secondary key in bytes.
-.It Ic transaction
-Configure the database (and, by extension, the database environment),
-to be transactional.
-.Pp
-There must be one token on the line: the keyword by itself.
-.It Ic type
-Configure the database type.
-.Pp
-There must be two tokens on the line: the keyword and the type,
-where the type is one of
-.Dq btree ,
-.Dq hash ,
-.Dq queue
-or
-.Dq recno .
-.It Ic \&}
-End the database environment block.
-.Pp
-There must be one token on the line: the keyword by itself.
-.El
-.Sh AUTHORS
-.An Thorsten Glaser Aq tg at debian.org
-wrote this manual page for the Debian project (but may be
-used by others) after the original HTML format documentation
-Copyright \(co 1996,2008 Oracle. All rights reserved.
diff --git a/debian/manpages/db5.1_deadlock.1 b/debian/manpages/db5.1_deadlock.1
deleted file mode 100644
index ed76077..0000000
--- a/debian/manpages/db5.1_deadlock.1
+++ /dev/null
@@ -1,97 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_DEADLOCK 1 "28 January 2005"
-.SH NAME
-db5.1_deadlock \- Detect and abort deadlocks
-.SH SYNOPSIS
-.B db5.1_deadlock
-[-Vv] [-a e | m | n | o | W | w | y] [-h home] [-L file] [-t sec.usec]
-.SH DESCRIPTION
-The db5.1_deadlock utility traverses the database environment lock region, and
-aborts a lock request each time it detects a deadlock or a lock request that
-has timed out. By default, in the case of a deadlock, a random lock request is
-chosen to be aborted.
-.PP
-This utility should be run as a background daemon, or the underlying Berkeley
-DB deadlock detection interfaces should be called in some other way, whenever
-there are multiple threads or processes accessing a database and at least one
-of them is modifying it.
-.SH OPTIONS
-.IP \fB\-a\fR
-When a deadlock is detected, abort the locker:
-.RS
-.IP m
-with the most locks
-.IP n
-with the fewest locks
-.IP o
-with the oldest lock
-.IP W
-with the most write locks
-.IP w
-with the fewest write locks
-.IP y
-with the youngest lock
-.RE
-.IP
-When lock or transaction timeouts have been specified:
-.RS
-.IP e
-abort any lock request that has timed out
-.RE
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-L\fR
-Log the execution of the db5.1_deadlock utility to the specified file in the
-following format, where \fI###\fR is the process ID, and the date
-is the time the utility was started.
-.sp
-.TP 8
-db_deadlock: ### Wed Jun 15 01:23:45 EDT 1995
-.sp
-This file will be removed if the db5.1_deadlock utility exits gracefully.
-.IP \fB\-t\fR
-Check the database environment every \fBsec\fR seconds plus
-\fBusec\fR microseconds to see if a process has been forced to wait
-for a lock; if one has, review the database environment lock
-structures.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.IP \fB\-v\fR
-Run in verbose mode, generating messages each time the detector runs.
-.PP
-If the \fB-t\fR option is not specified, db5.1_deadlock will
-run once and exit.
-.PP
-The db5.1_deadlock utility uses a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_deadlock should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_deadlock
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_deadlock utility does not attempt to create the Berkeley DB
-shared memory regions if they do not already exist. The application
-which creates the region should be started first, and then, once the
-region is created, the db5.1_deadlock utility should be started.
-.PP
-The DB_ENV->lock_detect method is the underlying method used by the
-db_deadlock utility. See the db_deadlock utility source code for an
-example of using DB_ENV->lock_detect
-in a IEEE/ANSI Std 1003.1 (POSIX) environment.
-.PP
-The db5.1_deadlock utility exits 0 on success, and >0 if an error occurs.
-.PP
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_deadlock from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_dump.1 b/debian/manpages/db5.1_dump.1
deleted file mode 100644
index 338ebdd..0000000
--- a/debian/manpages/db5.1_dump.1
+++ /dev/null
@@ -1,120 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_DUMP 1 "28 January 2005"
-.SH NAME
-db5.1_dump \- Write database to flat-text format
-.SH SYNOPSIS
-.B db5.1_dump
-[-klNpRrV] [-d ahr] [-f output] [-h home] [-P password] [-s database] file
-.SH DESCRIPTION
-The db5.1_dump utility reads the database file file and writes it to the standard
-output using a portable flat-text format understood by the db5.1_load utility.
-The file argument must be a file produced using the Berkeley DB library
-functions.
-.SH OPTIONS
-.IP \fB\-d\fR
-Dump the specified database in a format helpful for debugging the Berkeley DB
-library routines.
-.RS
-.IP a
-Display all information.
-.IP h
-Display only page headers.
-.IP r
-Do not display the free-list or pages on the free list. This
-mode is used by the recovery tests.
-.RE
-.IP
-\fBThe output format of the -d option is not standard and may change,
-without notice, between releases of the Berkeley DB library.\fR
-.IP \fB\-f\fR
-Write to the specified \fBfile\fR instead of to the standard output.
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-k\fR
-Dump record numbers from Queue and Recno databases as keys.
-.IP \fB\-l\fR
-List the databases stored in the file.
-.IP \fB\-N\fR
-Do not acquire shared region mutexes while running. Other problems,
-such as potentially fatal errors in Berkeley DB, will be ignored as well.
-This option is intended only for debugging errors, and should not be
-used under any other circumstances.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-p\fR
-If characters in either the key or data items are printing characters (as
-defined by \fBisprint\fR(3)), use printing characters in \fBfile\fR
-to represent them. This option permits users to use standard text editors
-and tools to modify the contents of databases.
-.sp
-Note: different systems may have different notions about what characters
-are considered \fIprinting characters\fR, and databases dumped in
-this manner may be less portable to external systems.
-.IP \fB\-R\fR
-Aggressively salvage data from a possibly corrupt file. The \fB-R\fR
-flag differs from the \fB-r\fR option in that it will return all
-possible data from the file at the risk of also returning already deleted
-or otherwise nonsensical items. Data dumped in this fashion will almost
-certainly have to be edited by hand or other means before the data is
-ready for reload into another database
-.IP \fB\-r\fR
-Salvage data from a possibly corrupt file. When used on a uncorrupted
-database, this option should return equivalent data to a normal dump, but
-most likely in a different order.
-.IP \fB\-s\fR
-Specify a single database to dump. If no database is specified, all
-databases in the database file are dumped.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.PP
-Dumping and reloading Hash databases that use user-defined hash
-functions will result in new databases that use the default hash
-function. Although using the default hash function may not be optimal
-for the new database, it will continue to work correctly.
-.PP
-Dumping and reloading Btree databases that use user-defined prefix or
-comparison functions will result in new databases that use the default
-prefix and comparison functions.
-\fBIn this case, it is quite likely that the database will be damaged
-beyond repair permitting neither record storage or retrieval.\fR
-.PP
-The only available workaround for either case is to modify the sources
-for the db5.1_load utility to load the database using the correct
-hash, prefix, and comparison functions.
-.PP
-The db5.1_dump utility output format is documented in the
-Dump Output Formats section of the Berkeley DB Reference Guide.
-.PP
-The db5.1_dump utility may be used with a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_dump should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_dump
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-Even when using a Berkeley DB database environment, the db5.1_dump
-utility does not use any kind of database locking if it is invoked with
-the \fB-d\fR, \fB-R\fR, or \fB-r\fR arguments. If used with
-one of these arguments, the db5.1_dump utility may only be safely
-run on databases that are not being modified by any other process;
-otherwise, the output may be corrupt.
-.PP
-The db5.1_dump utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_dump from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_hotbackup.1 b/debian/manpages/db5.1_hotbackup.1
deleted file mode 100644
index 4cf5b08..0000000
--- a/debian/manpages/db5.1_hotbackup.1
+++ /dev/null
@@ -1,119 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_HOTBACKUP 1 "28 January 2005"
-.SH NAME
-db5.1_hotbackup \- Create "hot backup" or "hot failover" snapshots
-.SH SYNOPSIS
-.B db5.1_hotbackup
-[-cDuVv] [-d data_dir ...] [-h home] [-l log_dir] [-P password] -b backup_dir
-.SH DESCRIPTION
-The db5.1_hotbackup utility creates "hot backup" or "hot failover" snapshots of Berkeley DB database environments.
-.PP
-The db5.1_hotbackup utility performs the following steps:
-.RS
-.IP 1.
-If the \-c option is specified, checkpoint the source home database
-environment, and remove any unnecessary log files.
-.IP 2.
-If the target directory for the backup does not exist, it is created with mode
-read-write-execute for the owner.
-.sp
-If the target directory for the backup does exist and the \-u option was
-specified, all log files in the target directory are removed; if the \-u option
-was not specified, all files in the target directory are removed.
-.IP 3.
-If the \-u option was not specified, copy application-specific files found in
-the database environment home directory, or any directory specified using the
--d option, into the target directory for the backup.
-.IP 4.
-Copy all log files found in the directory specified by the \-l option (or in the
-database environment home directory, if no \-l option was specified), into the
-target directory for the backup.
-.IP 5.
-Perform catastrophic recovery on the hot backup.
-.IP 6.
-Remove any unnecessary log files from the hot backup.
-.RE
-.PP
-The db5.1_hotbackup utility does not resolve pending transactions that are in the
-prepared state. Applications that use DB_TXN->prepare should specify
-DB_RECOVER_FATAL when opening the environment, and run DB_ENV->txn_recover to
-resolve any pending transactions, when failing over to the hot backup.
-.SH OPTIONS
-.IP \fB\-b\fR
-Specify the target directory for the backup.
-.IP \fB\-c\fR
-Before performing the snapshot, checkpoint the source database environment
-and remove any log files that are no longer required in that environment.
-\fBTo avoid making catastrophic failure impossible, log file removal
-must be integrated with log file archival.\fR
-.IP \fB\-d\fR
-Specify one or more source directories that contain databases; if none
-is specified, the database environment home directory will be searched
-for database files. As database files are copied into a single backup
-directory, files named the same, stored in different source directories,
-could overwrite each other when copied into the backup directory.
-.IP \fB\-h\fR
-Specify the source directory for the backup, that is, the database
-environment home directory.
-.IP \fB\-l\fR
-Specify a source directory that contains log files; if none is specified,
-the database environment home directory will be searched for log files.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-u\fR
-Update a pre-existing hot backup snapshot by copying in new log files.
-If the \fB\-u\fR option is specified, no databases will be copied
-into the target directory.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.IP \fB\-v\fR
-Run in verbose mode, listing operations as they are done.
-.IP \fB\-D\fR
-Use the data directories listed in the DB_CONFIG configuration
-file in the source directory. This option has three effects:
-First, if they do not already exist, the specified data directories
-will be created relative to the target directory (with mode read-write-execute
-owner). Second, all files in the source data directories will be copied to
-the target data directories. If the DB_CONFIG file specifies one
-or more absolute pathnames, files in those source directories will be
-copied to the top-level target directory. Third, the DB_CONFIG configuration
-file will be copied from the +source directory to the target directory, and
-subsequently used for configuration if recovery is run in the target directory.
-.PP
-Care should be taken with the \fB-D\fR option and data directories
-which are named relative to the source directory but are not
-subdirectories (that is, the name includes the element "..")
-Specifically, the constructed target directory names must be meaningful
-and distinct from the source directory names, otherwise running recovery
-in the target directory might corrupt the source data files.
-.PP
-\fBIt is an error to use absolute pathnames for data directories
-or the log directory in this mode, as the DB_CONFIG configuration
-file copied into the target directory would then point at the source
-directories and running recovery would corrupt the source data files.\fR
-.PP
-The db5.1_hotbackup utility uses a Berkeley DB environment (as described for the
-\fB\-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_hotbackup should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_hotbackup
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_hotbackup utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Oracle Corporation. This manual page was created based on
-the HTML documentation for db_hotbackup from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_load.1 b/debian/manpages/db5.1_load.1
deleted file mode 100644
index 9c836d5..0000000
--- a/debian/manpages/db5.1_load.1
+++ /dev/null
@@ -1,186 +0,0 @@
-.\" Manual Page for Berkeley DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_LOAD 1 "22 November 2009"
-.SH NAME
-db5.1_load \- Load data from standard input
-.SH SYNOPSIS
-.B db5.1_load
-[-nTV] [-c name=value] [-f file] [-h home] [-P password] [-t btree | hash | queue | recno] file
-
-.B db5.1_load
-[-r lsn | fileid] [-h home] [-P password] file
-.SH DESCRIPTION
-The db5.1_load utility reads from the standard input and loads it into the
-database file. The database file is created if it does not already exist.
-.PP
-The input to db5.1_load must be in the output format specified by the db5.0_dump
-utility, utilities, or as specified for the -T below.
-.SH OPTIONS
-.IP \fB\-c\fR
-Specify configuration options ignoring any value they may have based on
-the input. The command-line format is \fBname=value\fR. See the
-Supported Keywords section below for a list of keywords supported by
-the \fB-c\fR option.
-.IP \fB\-f\fR
-Read from the specified \fBinput\fR file instead of from the standard
-input.
-.IP \fB\-h\fR
-Specify a home directory for the database environment.
-.sp
-If a home directory is specified, the database environment is opened
-using the DB_INIT_LOCK, DB_INIT_LOG, DB_INIT_MPOOL, DB_INIT_TXN, and
-DB_USE_ENVIRON flags to DB_ENV->open. (This means that db5.1_load can be
-used to load data into databases while they are in use by other
-processes.) If the DB_ENV->open call fails, or if no home
-directory is specified, the database is still updated, but the
-environment is ignored; for example, no locking is done.
-.IP \fB\-n\fR
-Do not overwrite existing keys in the database when loading into an
-already existing database. If a key/data pair cannot be loaded into the
-database for this reason, a warning message is displayed on the standard
-error output, and the key/data pair are skipped.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-r\fR
-Reset the database's file ID or log sequence numbers (LSNs).
-.sp
-All database pages in transactional environments contain references to
-the environment's log records. In order to copy a database into a
-different database environment, database page references to the old
-environment's log records must be reset, otherwise data corruption can
-occur when the database is modified in the new environment. The
-\fB-r\fR \fBlsn\fR option resets a database's log sequence
-numbers.
-.sp
-All databases contain an ID string used to identify the database in the
-database environment cache. If a database is copied, and used in the
-same environment as another file with the same ID string, corruption can
-occur. The \fB-r\fR \fBfileid\fR option resets a database's file
-ID to a new value.
-.sp
-\fBIn both cases, the physical file specified by the file argument
-is modified in-place.\fR
-.IP \fB\-T\fR
-The \fB-T\fR option allows non-Berkeley DB applications to easily load text
-files into databases.
-.sp
-If the database to be created is of type Btree or Hash, or the keyword
-\fBkeys\fR is specified as set, the input must be paired lines of text,
-where the first line of the pair is the key item, and the second line of
-the pair is its corresponding data item. If the database to be created
-is of type Queue or Recno and the keyword \fBkeys\fR is not set, the
-input must be lines of text, where each line is a new data item for the
-database.
-.sp
-A simple escape mechanism, where newline and backslash (\\)
-characters are special, is applied to the text input. Newline characters
-are interpreted as record separators. Backslash characters in the text
-will be interpreted in one of two ways: If the backslash character
-precedes another backslash character, the pair will be interpreted as a
-literal backslash. If the backslash character precedes any other
-character, the two characters following the backslash will be interpreted
-as a hexadecimal specification of a single character; for example,
-\\0a is a newline character in the ASCII character set.
-.sp
-For this reason, any backslash or newline characters that naturally
-occur in the text input must be escaped to avoid misinterpretation by
-db5.1_load.
-.sp
-If the \fB-T\fR option is specified, the underlying access method type
-must be specified using the \fB-t\fR option.
-.IP \fB\-t\fR
-Specify the underlying access method. If no \fB-t\fR option is
-specified, the database will be loaded into a database of the same type
-as was dumped; for example, a Hash database will be created if a Hash
-database was dumped.
-.sp
-Btree and Hash databases may be converted from one to the other. Queue
-and Recno databases may be converted from one to the other. If the
-\fB-k\fR option was specified on the call to db5.1_dump then Queue
-and Recno databases may be converted to Btree or Hash, with the key being
-the integer record number.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.PP
-The db5.1_load utility may be used with a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_load should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_load
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_load utility exits 0 on success, 1 if one or more key/data
-pairs were not loaded into the database because the key already existed,
-and >1 if an error occurs.
-.SH EXAMPLES
-The db5.1_load utility can be used to load text files into databases.
-For example, the following command loads the standard UNIX
-\fI/etc/passwd\fR file into a database, with the login name as the
-key item and the entire password entry as the data item:
-.PP
-.TP 8
-awk \-F: '{print $1; print $0}' < /etc/passwd |
-sed 's/\\\\/\\\\\\\\/g' | db5.1_load \-T \-t hash passwd.db
-.PP
-Note that backslash characters naturally occurring in the text are escaped
-to avoid interpretation as escape characters by db5.1_load.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH SUPPORTED KEYWORDS
-The following keywords are supported for the \fB-c\fR command-line
-ption to the db5.1_load utility. See DB->open for further
-discussion of these keywords and what values should be specified.
-.PP
-The parenthetical listing specifies how the value part of the
-\fBname=value\fR pair is interpreted. Items listed as (boolean)
-expect value to be \fB1\fR (set) or \fB0\fR (unset). Items listed
-as (number) convert value to a number. Items listed as (string) use
-the string value without modification.
-.IP "bt_minkey (number)"
-The minimum number of keys per page.
-.IP "chksum (boolean)"
-Enable page checksums.
-.IP "database (string)"
-The database to load.
-.IP "db_lorder (number)"
-The byte order for integers in the stored database metadata.
-.IP "db_pagesize (number)"
-The size of database pages, in bytes.
-.IP "duplicates (boolean)"
-The value of the DB_DUP flag.
-.IP "dupsort (boolean)"
-The value of the DB_DUPSORT flag.
-.IP "extentsize (number)"
-The size of database extents, in pages, for Queue databases configured
-to use extents.
-.IP "h_ffactor (number)"
-The density within the Hash database.
-.IP "h_nelem (number)"
-The size of the Hash database.
-.IP "keys (boolean)"
-Specify whether keys are present for Queue or Recno databases.
-.IP "re_len (number)"
-Specify fixed-length records of the specified length.
-.IP "re_pad (string)"
-Specify the fixed-length record pad character.
-.IP "recnum (boolean)"
-The value of the DB_RECNUM flag.
-.IP "renumber (boolean)"
-The value of the DB_RENUMBER flag.
-.IP "subdatabase (string)"
-The subdatabase to load.
-
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_load from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_printlog.1 b/debian/manpages/db5.1_printlog.1
deleted file mode 100644
index 6416f33..0000000
--- a/debian/manpages/db5.1_printlog.1
+++ /dev/null
@@ -1,59 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_PRINTLOG 1 "28 January 2005"
-.SH NAME
-db5.1_printlog \- Dumps Berkeley DB log files in a human-readable format
-.SH SYNOPSIS
-.B db5.1_printlog
-[-NrV] [-b start-LSN] [-e stop-LSN] [-h home] [-P password]
-.SH DESCRIPTION
-The db5.1_printlog utility is a debugging utility that dumps Berkeley DB log files
-in a human-readable format.
-.SH OPTIONS
-.IP \fB\-b\fR
-Display log records starting at log sequence number (LSN) \fBstart-LSN\fR;
-\fBstart-LSN\fR is specified as a file number, followed by a slash (/)
-character, followed by an offset number, with no intervening whitespace.
-.IP \fB\-e\fR
-Stop displaying log records at log sequence number (LSN) \fBstop-LSN\fR;
-\fBstop-LSN\fR is specified as a file number, followed by a slash (/)
-character, followed by an offset number, with no intervening whitespace.
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-N\fR
-Do not acquire shared region mutexes while running. Other problems,
-such as potentially fatal errors in Berkeley DB, will be ignored as well.
-This option is intended only for debugging errors, and should not be
-used under any other circumstances.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-r\fR
-Read the log files in reverse order.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.PP
-The db5.1_printlog utility uses a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_printlog should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_printlog
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_printlog utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_printlog from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_recover.1 b/debian/manpages/db5.1_recover.1
deleted file mode 100644
index 1a36c66..0000000
--- a/debian/manpages/db5.1_recover.1
+++ /dev/null
@@ -1,95 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_RECOVER 1 "28 January 2005"
-.SH NAME
-db5.1_recover \- Restore the database to a consistent state
-.SH SYNOPSIS
-.B db5.1_recover
-[-ceVv] [-h home] [-P password] [-t [[CC]YY]MMDDhhmm[.SS]]]
-.SH DESCRIPTION
-The db5.1_recover utility must be run after an unexpected application, Berkeley
-DB, or system failure to restore the database to a consistent state. All
-committed transactions are guaranteed to appear after db5.1_recover has run, and
-all uncommitted transactions will be completely undone.
-.SH OPTIONS
-.IP \fB\-c\fR
-Perform catastrophic recovery instead of normal recovery.
-.IP \fB\-e\fR
-Retain the environment after running recovery. This option
-will rarely be used unless a DB_CONFIG file is present in the home
-directory. If a DB_CONFIG file is not present, then the regions will be
-created with default parameter values.
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-t\fR
-Recover to the time specified rather than to the most current possible
-date. The timestamp argument should be in the form
-[[CC]YY]MMDDhhmm[.SS] where each pair of
-letters represents the following:
-.RS
-.IP CC
-The first two digits of the year (the century).
-.IP YY
-The second two digits of the year. If "YY" is specified, but "CC" is not,
-a value for "YY" between 69 and 99 results in a "CC" value of 19. Otherwise,
-a "YY" value of 20 is used.
-.IP MM
-The month of the year, from 1 to 12.
-.IP DD
-The day of the month, from 1 to 31.
-.IP hh
-The hour of the day, from 0 to 23.
-.IP mm
-The minute of the hour, from 0 to 59.
-.IP SS
-The second of the minute, from 0 to 61.
-.RE
-.IP
-If the "CC" and "YY" letter pairs are not specified, the values default
-to the current year. If the "SS" letter pair is not specified, the value
-defaults to 0.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.IP \fB\-v\fR
-Run in verbose mode.
-.PP
-In the case of catastrophic recovery, an archival copy - or
-\fIsnapshot\fR - of all database files must be restored along with
-all of the log files written since the database file snapshot was made.
-(If disk space is a problem, log files may be referenced by symbolic
-links).
-.PP
-If the failure was not catastrophic, the files present on the system at the
-time of failure are sufficient to perform recovery.
-.PP
-If log files are missing, db5.1_recover will identify the missing
-log file(s) and fail, in which case the missing log files need to be
-restored and recovery performed again.
-.PP
-The db5.1_recover utility uses a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_recover should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_recover
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_recover utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_recover from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_stat.1 b/debian/manpages/db5.1_stat.1
deleted file mode 100644
index 254a3ba..0000000
--- a/debian/manpages/db5.1_stat.1
+++ /dev/null
@@ -1,127 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_STAT 1 "28 January 2005"
-.SH NAME
-db5.1_stat \- Display statistics for Berkeley DB environments
-.SH SYNOPSIS
-.B db5.1_stat
--d file [-fN] [-h home] [-P password] [-s database]
-
-.B db5.1_stat
-[-cEelmNrtVZ] [-C Aclop] [-h home] [-L A] [-M A] [-R A] [-P password]
-.SH DESCRIPTION
-The db5.1_stat utility displays statistics for Berkeley DB environments.
-.SH OPTIONS
-.IP \fB\-C\fR
-Display internal information about the locking subsystem. (The output
-from this option is often both voluminous and meaningless, and is
-intended only for debugging.)
-.RS
-.IP A
-Display all information.
-.IP c
-Display lock conflict matrix.
-.IP l
-Display lockers within hash chains.
-.IP o
-Display lock objects within hash chains.
-.IP p
-Display locking subsystem parameters.
-.RE
-.IP \fB\-c\fR
-Display locking subsystem statistics, as described in DB_ENV->lock_stat.
-.IP \fB\-d\fR
-Display database statistics for the specified file, as described in
-DB->stat.
-.sp
-If the database contains multiple databases and the \fB-s\fR flag is
-not specified, the statistics are for the internal database that describes
-the other databases the file contains, and not for the file as a whole.
-.IP \fB\-E\fR
-Display internal information about the database environment, including
-all configured subsystems of the database environment. (The
-output from this option is often both voluminous and meaningless, and
-is intended only for debugging.)
-.IP \fB\-e\fR
-Display information about the database environment, including
-all configured subsystems of the database environment.
-.IP \fB\-f\fR
-Display only those database statistics that can be
-acquired without traversing the database.
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-l\fR
-Display logging subsystem statistics, as described in DB_ENV->log_stat.
-.IP \fB\-M\fR
-Display internal information about the cache. (The output from this
-option is often both voluminous and meaningless, and is intended only
-for debugging.)
-.RS
-.IP A
-Display all information.
-.IP h
-Display buffers within hash chains.
-.RE
-.IP \fB\-m\fR
-Display cache statistics, as described in DB_ENV->memp_stat.
-.IP \fB\-N\fR
-Do not acquire shared region mutexes while running. Other problems,
-such as potentially fatal errors in Berkeley DB, will be ignored as well.
-This option is intended only for debugging errors, and should not be
-used under any other circumstances.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-R\fR
-Display internal information about the replication subsystem. (The
-output from this option is often both voluminous and meaningless, and
-is intended only for debugging.)
-.RS
-.IP A
-Display all information.
-.RE
-.IP \fB\-r\fR
-Display replication statistics, as described in DB_ENV->rep_stat.
-.IP \fB\-s\fR
-Display statistics for the specified database contained in the file
-specified with the \fB-d\fR flag.
-.IP \fB\-t\fR
-Display transaction subsystem statistics, as described in DB_ENV->txn_stat.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.IP \fB\-Z\fR
-Reset the statistics after reporting them; valid only with the \fB-C\fR,
-\fB-c\fR, \fB-E\fR, \fB-e\fR, \fB-L\fR, \fB-l\fR,
-\fB-M\fR, \fB-m\fR, \fB-R\fR, \fB-r\fR, and \fB-t\fR
-options.
-.PP
-Values normally displayed in quantities of bytes are displayed as a
-combination of gigabytes (GB), megabytes (MB), kilobytes (KB), and bytes
-(B). Otherwise, values smaller than 10 million are displayed without
-any special notation, and values larger than 10 million are displayed
-as a number followed by "M".
-.PP
-The db5.1_stat utility may be used with a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_stat should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_stat
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_stat utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_stat from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_upgrade.1 b/debian/manpages/db5.1_upgrade.1
deleted file mode 100644
index b510f3b..0000000
--- a/debian/manpages/db5.1_upgrade.1
+++ /dev/null
@@ -1,81 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_UPGRADE 1 "28 January 2005"
-.SH NAME
-db5.1_upgrade \- Upgrade the Berkeley DB version to the current release version.
-.SH SYNOPSIS
-.B db5.1_upgrade
-[-NsVv] [-h home] [-P password] file ...
-.SH DESCRIPTION
-The db5.1_upgrade utility upgrades the Berkeley DB version of one or more files
-and the databases they contain to the current release version.
-.SH OPTIONS
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-N\fR
-Do not acquire shared region mutexes while running. Other problems,
-such as potentially fatal errors in Berkeley DB, will be ignored as well.
-This option is intended only for debugging errors, and should not be
-used under any other circumstances.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-s\fR
-This flag is only meaningful when upgrading databases from releases
-before the Berkeley DB 3.1 release.
-.sp
-As part of the upgrade from the Berkeley DB 3.0 release to the 3.1 release,
-the on-disk format of duplicate data items changed. To correctly upgrade
-the format requires that applications specify whether duplicate data
-items in the database are sorted or not. Specifying the \fB-s\fR
-flag means that the duplicates are sorted; otherwise, they are assumed
-to be unsorted. Incorrectly specifying the value of this flag may lead
-to database corruption.
-.sp
-Because the db5.1_upgrade utility upgrades a physical file
-(including all the databases it contains), it is not possible to use
-db5.1_upgrade to upgrade files where some of the databases it
-includes have sorted duplicate data items, and some of the databases it
-includes have unsorted duplicate data items. If the file does not have
-more than a single database, if the databases do not support duplicate
-data items, or if all the databases that support duplicate data items
-support the same style of duplicates (either sorted or unsorted),
-db5.1_upgrade will work correctly as long as the \fB-s\fR flag
-is correctly specified. Otherwise, the file cannot be upgraded using
-db5.1_upgrade, and must be upgraded manually using the
-db5.1_dump and db5.0_load utilities.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.IP \fB\-v\fR
-Run in verbose mode, displaying a message for each successful upgrade.
-.PP
-\fBIt is important to realize that Berkeley DB database upgrades are done
-in place, and so are potentially destructive.\fR This means that if the
-system crashes during the upgrade procedure, or if the upgrade procedure
-runs out of disk space, the databases may be left in an inconsistent and
-unrecoverable state.
-.PP
-The db5.1_upgrade utility may be used with a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_upgrade should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_upgrade
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_upgrade utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_upgrade from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.1_verify.1 b/debian/manpages/db5.1_verify.1
deleted file mode 100644
index df11841..0000000
--- a/debian/manpages/db5.1_verify.1
+++ /dev/null
@@ -1,69 +0,0 @@
-.\" Manual Page for Berkely DB utils, created from upstream
-.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
-.TH DB5.1_VERIFY 1 "28 January 2005"
-.SH NAME
-db5.1_verify \- Verifies the structure databases
-.SH SYNOPSIS
-.B db5.1_verify
-[-NoqV] [-h home] [-P password] file ...
-.SH DESCRIPTION
-The db5.1_verify utility verifies the structure of one or more files and the
-databases they contain.
-.SH OPTIONS
-.IP \fB\-h\fR
-Specify a home directory for the database environment; by
-default, the current working directory is used.
-.IP \fB\-o\fR
-Skip the database checks for btree and duplicate sort order and for
-hashing.
-.sp
-If the file being verified contains databases with non-default
-comparison or hashing configurations, calling the db5.1_verify
-utility without the \fB-o\fR flag will usually return failure. The
-\fB-o\fR flag causes db5.1_verify to ignore database sort or
-hash ordering and allows db5.1_verify to be used on these files.
-To fully verify these files, verify them explicitly using the
-DB->verify method, after configuring the correct comparison or hashing
-functions.
-.IP \fB\-N\fR
-Do not acquire shared region mutexes while running. Other problems,
-such as potentially fatal errors in Berkeley DB, will be ignored as well.
-This option is intended only for debugging errors, and should not be
-used under any other circumstances.
-.IP \fB\-P\fR
-Specify an environment password. Although Berkeley DB utilities overwrite
-password strings as soon as possible, be aware there may be a window of
-vulnerability on systems where unprivileged users can see command-line
-arguments or where utilities are not able to overwrite the memory
-containing the command-line arguments.
-.IP \fB\-q\fR
-Suppress the printing of any error descriptions, simply exit success or
-failure.
-.IP \fB\-V\fR
-Write the library version number to the standard output, and exit.
-.PP
-\fBThe db5.1_verify utility does not perform any locking, even in
-Berkeley DB environments that are configured with a locking subsystem. As
-such, it should only be used on files that are not being modified by
-another thread of control.\fR
-.PP
-The db5.1_verify utility may be used with a Berkeley DB environment (as described for the
-\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
-because the utility was run in a directory containing a Berkeley DB
-environment). In order to avoid environment corruption when using a
-Berkeley DB environment, db5.1_verify should always be given the chance to
-detach from the environment and exit gracefully. To cause db5.1_verify
-to release all environment resources and exit cleanly, send it an
-interrupt signal (SIGINT).
-.PP
-The db5.1_verify utility exits 0 on success, and >0 if an error occurs.
-.SH ENVIRONMENT
-.IP \fBDB_HOME\fR
-If the \fB-h\fR option is not specified and the environment variable
-DB_HOME is set, it is used as the path of the database home, as described
-in DB_ENV->open.
-.SH AUTHORS
-Sleepycat Software, Inc. This manual page was created based on
-the HTML documentation for db_verify from Sleepycat,
-by Thijs Kinkhorst <thijs at kinkhorst.com>,
-for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_archive.1 b/debian/manpages/db5.2_archive.1
new file mode 100644
index 0000000..41a62b4
--- /dev/null
+++ b/debian/manpages/db5.2_archive.1
@@ -0,0 +1,95 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_ARCHIVE 1 "28 January 2005"
+.SH NAME
+db5.2_archive \- Find unused log files for archiving purposes
+.SH SYNOPSIS
+.B db5.2_archive
+[-adlsVv] [-h home] [-P password]
+.SH DESCRIPTION
+The db5.2_archive utility writes the pathnames of log files that
+are no longer in use (for example, no longer involved in active
+transactions), to the standard output, one pathname per line. These
+log files should be written to backup media to provide for recovery in
+the case of catastrophic failure (which also requires a snapshot of the
+database files), but they may then be deleted from the system to reclaim
+disk space.
+.SH OPTIONS
+.PP
+.IP \fB\-a\fR
+Write all pathnames as absolute pathnames, instead of relative to the
+database home directories.
+.IP \fB\-d\fR
+Remove log files that are no longer needed; no filenames are written.
+Automatic log file removal is likely to make catastrophic recovery
+impossible.
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-l\fR
+Write out the pathnames of all the database log files, whether or not
+they are involved in active transactions.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-s\fR
+Write the pathnames of all the database files that need to be archived
+in order to recover the database from catastrophic failure. If any of
+the database files have not been accessed during the lifetime of the
+current log files, db5.2_archive will not include them in this
+output.
+.sp
+It is possible that some of the files to which the log refers have since
+been deleted from the system. In this case, db5.2_archive will
+ignore them. When db5.2_recover is run, any files to which the
+log refers that are not present during recovery are assumed to have been
+deleted and will not be recovered.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.IP \fB\-v\fR
+Run in verbose mode, listing the checkpoints in the log files as they
+are reviewed.
+.PP
+Log cursor handles (returned by the DB_ENV->log_cursor method) may have open
+file descriptors for log files in the database environment. Also, the
+Berkeley DB interfaces to the database environment logging subsystem (for
+example, DB_ENV->log_put and DB_TXN->abort) may allocate log cursors
+and have open file descriptors for log files as well. On operating
+systems where filesystem related system calls (for example, rename and
+unlink on Windows/NT) can fail if a process has an open file descriptor
+for the affected file, attempting to move or remove the log files listed
+by db5.2_archive may fail. All Berkeley DB internal use of log cursors
+operates on active log files only and furthermore, is short-lived in
+nature. So, an application seeing such a failure should be restructured
+to close any open log cursors it may have, and otherwise to retry the
+operation until it succeeds. (Although the latter is not likely to be
+necessary; it is hard to imagine a reason to move or rename a log file
+in which transactions are being logged or aborted.)
+.PP
+The db5.2_archive utility uses a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_archive should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_archive
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The DB_ENV->log_archive method is the underlying method used by the db5.2_archive utility.
+See the db5.2_archive utility source code for an example of using
+DB_ENV->log_archive in a IEEE/ANSI Std 1003.1 (POSIX) environment.
+.PP
+The db5.2_archive utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_archive from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_checkpoint.1 b/debian/manpages/db5.2_checkpoint.1
new file mode 100644
index 0000000..15e827b
--- /dev/null
+++ b/debian/manpages/db5.2_checkpoint.1
@@ -0,0 +1,78 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_CHECKPOINT 1 "28 January 2005"
+.SH NAME
+db5.2_checkpoint \- Periodically checkpoint transactions
+.SH SYNOPSIS
+.B db5.2_checkpoint
+[-1Vv] [-h home] [-k kbytes] [-L file] [-P password] [-p min]
+.SH DESCRIPTION
+The db5.2_checkpoint utility is a daemon process that monitors the database log,
+and periodically calls DB_ENV->txn_checkpoint to checkpoint it.
+.SH OPTIONS
+.IP \fB\-1\fR
+Checkpoint the log once, regardless of whether or not there has been
+activity since the last checkpoint and then exit.
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-k\fR
+Checkpoint the database at least as often as every \fBkbytes\fR of log
+file are written.
+.IP \fB\-L\fR
+Log the execution of the db5.2_checkpoint utility to the specified file in the
+following format, where \fI###\fR is the process ID, and the date
+is the time the utility was started.
+.sp
+.TP 8
+db_checkpoint: ### Wed Jun 15 01:23:45 EDT 1995
+.sp
+This file will be removed if the db5.2_checkpoint utility exits gracefully.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-p\fR
+Checkpoint the database at least every \fBmin\fR minutes if there has
+been any activity since the last checkpoint.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.IP \fB\-v\fR
+Write the time of each checkpoint attempt to the standard output.
+.PP
+At least one of the \fB-1\fR, \fB-k\fR, and \fB-p\fR options
+must be specified.
+.PP
+The db5.2_checkpoint utility uses a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_checkpoint should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_checkpoint
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_checkpoint utility does not attempt to create the Berkeley DB
+shared memory regions if they do not already exist. The application
+that creates the region should be started first, and once the region is
+created, the db5.2_checkpoint utility should be started.
+.PP
+The DB_ENV->txn_checkpoint method is the underlying method used by the
+db5.2_checkpoint utility. See the db_checkpoint utility source code for an
+example of using DB_ENV->txn_checkpoint in a IEEE/ANSI Std 1003.1
+(POSIX) environment.
+.PP
+The db5.2_checkpoint utility exits 0 on success, and >0 if an error occurs.
+.PP
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_checkpoint from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_codegen.1 b/debian/manpages/db5.2_codegen.1
new file mode 100644
index 0000000..5e533a1
--- /dev/null
+++ b/debian/manpages/db5.2_codegen.1
@@ -0,0 +1,319 @@
+.\" Copyright \(co 2010 by Thorsten Glaser <tg at debian.org>
+.\" <!--$Id: db_codegen.so,v 10.6 2007/05/17 18:29:34 bostic Exp $-->
+.\" <!--Copyright (c) 1997,2008 Oracle. All rights reserved.-->
+.\" <!--See the file LICENSE for redistribution information.-->
+.\"
+.Dd January 12, 2011
+.Dt DB5.2_CODEGEN 1
+.Os "Berkeley DB"
+.Sh NAME
+.Nm db5.2_codegen
+.Nd generate application code for Berkeley DB
+.Sh SYNOPSIS
+.Nm
+.Op Fl Vv
+.Op Fl a Ar api
+.Op Fl i Ar file
+.Op Fl o Ar prefix
+.Sh DESCRIPTION
+The
+.Nm
+utility generates application code to create and configure
+Berkeley DB database environments and databases based on a simple
+description language and writes it to one or more output files.
+The generated code may need modification, in the case of complicated
+applications, but will usually significantly reduce the time required
+to create Berkeley DB applications.
+.Pp
+The options are as follows:
+.Bl -tag -width XXX
+.It Fl a Ar api
+Generate code for the specified API
+.Pq currently, only Do c Dc is accepted .
+.It Fl i Ar file
+Specify an input
+.Ar file ;
+by default, standard input is used.
+.It Fl o Ar prefix
+Specify an output file
+.Ar prefix ;
+by default,
+.Dq application
+is used.
+.It Fl V
+Write the library version number to standard output and exit.
+.It Fl v
+Run in verbose mode.
+.El
+.Pp
+The
+.Nm
+utility exits 0 on success, and >0 if an error occurs.
+.Sh C Language Specific Information
+By default, when the
+.Nm
+utility generates C-language code, the output file is named
+.Dq Pa application.c .
+The output filename can be specified with the
+.Fl o
+option.
+.Pp
+At the beginning of the output file is a list of public database environment
+.Pq Vt DB_ENV
+handles and database
+.Pq Vt DB
+handles, as specified by the description language.
+The database environment handle variables are named
+.Dq Ar XXX Ns _dbenv ,
+where
+.Dq Ar XXX
+is the name of the environment in the input specification.
+For databases associated with a database environment, the database
+handle variables are named
+.Dq Ar XXX Ns _ Ns Ar YYY ,
+where
+.Dq Ar XXX
+is the name of the environment, and
+.Dq Ar YYY
+is the name of the database.
+For standalone databases, the database handle variables are named
+.Dq Ar XXX ,
+where
+.Dq Ar XXX
+is the name of the database.
+.Pp
+There are two public functions in the output file:
+.Fn bdb_startup
+and
+.Fn bdb_shutdown .
+The
+.Fn bdb_startup
+function should be called to create and configure the database
+environments and databases, and the
+.Fn bdb_shutdown
+function should be called to gracefully shut down the environments
+and databases.
+.Sh Specification Language
+The
+.Nm
+uses a simple description language:
+.Pp
+.Bl -bullet -compact
+.It
+Lines in the input consist of white-space separated tokens.
+.It
+Tokens are case-insensitive.
+.It
+Empty lines and lines where the first non-space character is a hash mark
+.Pq Dq \&#
+are ignored.
+In addition, hash marks may appear in lines, in which case the content
+of the line from the hash mark to the end of the line is ignored.
+.El
+.Pp
+There are two top-level objects:
+.Dq environment
+and
+.Dq database ,
+which correspond to database environments and databases, respectively.
+These top-level objects can be associated with keywords to describe
+their configuration and relationships.
+.Pp
+For example, the following input would create two standalone databases:
+.Bd -literal -offset indent
+database data_one {
+ type btree
+}
+database data_two {
+ type btree
+}
+.Ed
+.Pp
+In this case, there would be no
+.Vt DB_ENV
+handle, and the public
+.Vt DB
+handles would be:
+.Bd -literal -offset indent
+DB *data_one;
+DB *data_two;
+.Ed
+.Pp
+For example, the following input would create a database environment which
+contains three databases:
+.Bd -literal -offset indent
+environment myenv {
+ database data_one {
+ type btree
+ }
+ database data_two {
+ type btree
+ }
+ database data_three {
+ type btree
+ }
+}
+.Ed
+.Pp
+In this case, the public
+.Vt DB_ENV
+and
+.Vt DB
+handles would be:
+.Bd -literal -offset indent
+DB_ENV *myenv_dbenv;
+DB *myenv_data_one;
+DB *myenv_data_two;
+DB *myenv_data_three;
+.Ed
+.Pp
+A variety of keywords can be specified for the databases and the environments.
+For example, the cache size can be specified for the database environment,
+and the page size can be specified for the database, as well as for secondary
+relationships:
+.Bd -literal -offset indent
+environment myenv {
+ cachesize 2 0 10
+ database data_one {
+ type btree
+ pagesize 1024
+ }
+ database data_two {
+ primary data_one
+ secondary_offset 10 15
+ type btree
+ pagesize 32768
+ }
+ database data_three {
+ type btree
+ pagesize 512
+ }
+}
+.Ed
+.Ss Environment Keywords
+.Bl -tag -width secondary_offset
+.It Ic environment
+Start a database environment block.
+.Pp
+There must be three tokens on the line: the keyword, the name of the
+environment and an opening brace
+.Pq Dq \&{ .
+.It Ic home
+Specify the database environment home directory.
+.Pp
+There must be two tokens on the line: the keyword and the home directory.
+.It Ic cachesize
+Specify the database environment cache size.
+.Pp
+There must be two tokens on the line: the keyword, the gigabytes of cache,
+the bytes of cache, and the number of caches (the number of underlying
+physical areas into which the cache is logically divided).
+.It Ic private
+Specify the database environment is private.
+.Pp
+There must be one token on the line: the keyword by itself.
+.It Ic \&}
+End the database environment block.
+.Pp
+There must be one token on the line: the keyword by itself.
+.El
+.Ss Database Keywords
+.Bl -tag -width secondary_offset
+.It Ic database
+Start a database block.
+.Pp
+There must be three tokens on the line: the keyword, the name of the
+database and an opening brace
+.Pq Dq \&{ .
+.It Ic custom
+Specify a custom key-comparison routine.
+This is used when the Btree database requires a specific sort that
+.Nm
+cannot generate.
+A stub key comparison routine will be created and configured for the
+database which should be modified as necessary.
+See the
+.Dq Ic key_type
+keyword for more information.
+.Pp
+There must be one token on the line: the keyword by itself.
+.It Ic dupsort
+Configure the database to support sorted duplicates.
+.Pp
+There must be one token on the line: the keyword by itself.
+.It Ic extentsize
+Configure the size of the Queue database extent files.
+.Pp
+There must be two tokens on the line: the keyword and the extent file
+size, as a number of pages.
+.It Ic key_type
+Configure a integral type key-comparison routine.
+This is used when the Btree database key is an integral type (such as
+.Dq Vt "unsigned int"
+or
+.Dq Vt u_int32_t ) .
+Any C-language integral type may be specified.
+See the
+.Dq Ic custom
+keyword for more information.
+A Btree comparison routine based on the type of the key will be
+created and configured.
+.Pp
+There must be two tokens on the line: the keyword and the type.
+.It Ic pagesize
+Configure the database page size.
+.Pp
+There must be two tokens on the line: the keyword and the page size in bytes.
+.It Ic primary
+Configure the database as a secondary index.
+A stub secondary callback routine will be created and configured for the
+database, which should be modified as necessary.
+See the
+.Dq Ic secondary_offset
+keyword for more information.
+.Pp
+There must be two tokens on the line: the keyword and the
+name of the primary database for which this database is a secondary.
+.It Ic recnum
+Configure the Btree database to support record number access.
+.Pp
+There must be one token on the line: the keyword by itself.
+.It Ic re_len
+Configure the record length for a Queue database or a fixed-length
+Recno database.
+.Pp
+There must be two tokens on the line: the keyword and the length
+of a record, in bytes.
+.Pp
+.It Ic secondary_offset
+Configure a secondary callback routine based on a byte string found
+in the primary database's data item.
+.Pp
+There must be three tokens on the line: the keyword, the byte offset from
+the beginning of the primary data item where the secondary key occurs, and
+the length of the secondary key in bytes.
+.It Ic transaction
+Configure the database (and, by extension, the database environment),
+to be transactional.
+.Pp
+There must be one token on the line: the keyword by itself.
+.It Ic type
+Configure the database type.
+.Pp
+There must be two tokens on the line: the keyword and the type,
+where the type is one of
+.Dq btree ,
+.Dq hash ,
+.Dq queue
+or
+.Dq recno .
+.It Ic \&}
+End the database environment block.
+.Pp
+There must be one token on the line: the keyword by itself.
+.El
+.Sh AUTHORS
+.An Thorsten Glaser Aq tg at debian.org
+wrote this manual page for the Debian project (but may be
+used by others) after the original HTML format documentation
+Copyright \(co 1996,2008 Oracle. All rights reserved.
diff --git a/debian/manpages/db5.2_deadlock.1 b/debian/manpages/db5.2_deadlock.1
new file mode 100644
index 0000000..0ff6035
--- /dev/null
+++ b/debian/manpages/db5.2_deadlock.1
@@ -0,0 +1,97 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_DEADLOCK 1 "28 January 2005"
+.SH NAME
+db5.2_deadlock \- Detect and abort deadlocks
+.SH SYNOPSIS
+.B db5.2_deadlock
+[-Vv] [-a e | m | n | o | W | w | y] [-h home] [-L file] [-t sec.usec]
+.SH DESCRIPTION
+The db5.2_deadlock utility traverses the database environment lock region, and
+aborts a lock request each time it detects a deadlock or a lock request that
+has timed out. By default, in the case of a deadlock, a random lock request is
+chosen to be aborted.
+.PP
+This utility should be run as a background daemon, or the underlying Berkeley
+DB deadlock detection interfaces should be called in some other way, whenever
+there are multiple threads or processes accessing a database and at least one
+of them is modifying it.
+.SH OPTIONS
+.IP \fB\-a\fR
+When a deadlock is detected, abort the locker:
+.RS
+.IP m
+with the most locks
+.IP n
+with the fewest locks
+.IP o
+with the oldest lock
+.IP W
+with the most write locks
+.IP w
+with the fewest write locks
+.IP y
+with the youngest lock
+.RE
+.IP
+When lock or transaction timeouts have been specified:
+.RS
+.IP e
+abort any lock request that has timed out
+.RE
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-L\fR
+Log the execution of the db5.2_deadlock utility to the specified file in the
+following format, where \fI###\fR is the process ID, and the date
+is the time the utility was started.
+.sp
+.TP 8
+db_deadlock: ### Wed Jun 15 01:23:45 EDT 1995
+.sp
+This file will be removed if the db5.2_deadlock utility exits gracefully.
+.IP \fB\-t\fR
+Check the database environment every \fBsec\fR seconds plus
+\fBusec\fR microseconds to see if a process has been forced to wait
+for a lock; if one has, review the database environment lock
+structures.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.IP \fB\-v\fR
+Run in verbose mode, generating messages each time the detector runs.
+.PP
+If the \fB-t\fR option is not specified, db5.2_deadlock will
+run once and exit.
+.PP
+The db5.2_deadlock utility uses a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_deadlock should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_deadlock
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_deadlock utility does not attempt to create the Berkeley DB
+shared memory regions if they do not already exist. The application
+which creates the region should be started first, and then, once the
+region is created, the db5.2_deadlock utility should be started.
+.PP
+The DB_ENV->lock_detect method is the underlying method used by the
+db_deadlock utility. See the db_deadlock utility source code for an
+example of using DB_ENV->lock_detect
+in a IEEE/ANSI Std 1003.1 (POSIX) environment.
+.PP
+The db5.2_deadlock utility exits 0 on success, and >0 if an error occurs.
+.PP
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_deadlock from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_dump.1 b/debian/manpages/db5.2_dump.1
new file mode 100644
index 0000000..3bb8683
--- /dev/null
+++ b/debian/manpages/db5.2_dump.1
@@ -0,0 +1,120 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_DUMP 1 "28 January 2005"
+.SH NAME
+db5.2_dump \- Write database to flat-text format
+.SH SYNOPSIS
+.B db5.2_dump
+[-klNpRrV] [-d ahr] [-f output] [-h home] [-P password] [-s database] file
+.SH DESCRIPTION
+The db5.2_dump utility reads the database file file and writes it to the standard
+output using a portable flat-text format understood by the db5.2_load utility.
+The file argument must be a file produced using the Berkeley DB library
+functions.
+.SH OPTIONS
+.IP \fB\-d\fR
+Dump the specified database in a format helpful for debugging the Berkeley DB
+library routines.
+.RS
+.IP a
+Display all information.
+.IP h
+Display only page headers.
+.IP r
+Do not display the free-list or pages on the free list. This
+mode is used by the recovery tests.
+.RE
+.IP
+\fBThe output format of the -d option is not standard and may change,
+without notice, between releases of the Berkeley DB library.\fR
+.IP \fB\-f\fR
+Write to the specified \fBfile\fR instead of to the standard output.
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-k\fR
+Dump record numbers from Queue and Recno databases as keys.
+.IP \fB\-l\fR
+List the databases stored in the file.
+.IP \fB\-N\fR
+Do not acquire shared region mutexes while running. Other problems,
+such as potentially fatal errors in Berkeley DB, will be ignored as well.
+This option is intended only for debugging errors, and should not be
+used under any other circumstances.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-p\fR
+If characters in either the key or data items are printing characters (as
+defined by \fBisprint\fR(3)), use printing characters in \fBfile\fR
+to represent them. This option permits users to use standard text editors
+and tools to modify the contents of databases.
+.sp
+Note: different systems may have different notions about what characters
+are considered \fIprinting characters\fR, and databases dumped in
+this manner may be less portable to external systems.
+.IP \fB\-R\fR
+Aggressively salvage data from a possibly corrupt file. The \fB-R\fR
+flag differs from the \fB-r\fR option in that it will return all
+possible data from the file at the risk of also returning already deleted
+or otherwise nonsensical items. Data dumped in this fashion will almost
+certainly have to be edited by hand or other means before the data is
+ready for reload into another database
+.IP \fB\-r\fR
+Salvage data from a possibly corrupt file. When used on a uncorrupted
+database, this option should return equivalent data to a normal dump, but
+most likely in a different order.
+.IP \fB\-s\fR
+Specify a single database to dump. If no database is specified, all
+databases in the database file are dumped.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.PP
+Dumping and reloading Hash databases that use user-defined hash
+functions will result in new databases that use the default hash
+function. Although using the default hash function may not be optimal
+for the new database, it will continue to work correctly.
+.PP
+Dumping and reloading Btree databases that use user-defined prefix or
+comparison functions will result in new databases that use the default
+prefix and comparison functions.
+\fBIn this case, it is quite likely that the database will be damaged
+beyond repair permitting neither record storage or retrieval.\fR
+.PP
+The only available workaround for either case is to modify the sources
+for the db5.2_load utility to load the database using the correct
+hash, prefix, and comparison functions.
+.PP
+The db5.2_dump utility output format is documented in the
+Dump Output Formats section of the Berkeley DB Reference Guide.
+.PP
+The db5.2_dump utility may be used with a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_dump should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_dump
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+Even when using a Berkeley DB database environment, the db5.2_dump
+utility does not use any kind of database locking if it is invoked with
+the \fB-d\fR, \fB-R\fR, or \fB-r\fR arguments. If used with
+one of these arguments, the db5.2_dump utility may only be safely
+run on databases that are not being modified by any other process;
+otherwise, the output may be corrupt.
+.PP
+The db5.2_dump utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_dump from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_hotbackup.1 b/debian/manpages/db5.2_hotbackup.1
new file mode 100644
index 0000000..1b409de
--- /dev/null
+++ b/debian/manpages/db5.2_hotbackup.1
@@ -0,0 +1,119 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_HOTBACKUP 1 "28 January 2005"
+.SH NAME
+db5.2_hotbackup \- Create "hot backup" or "hot failover" snapshots
+.SH SYNOPSIS
+.B db5.2_hotbackup
+[-cDuVv] [-d data_dir ...] [-h home] [-l log_dir] [-P password] -b backup_dir
+.SH DESCRIPTION
+The db5.2_hotbackup utility creates "hot backup" or "hot failover" snapshots of Berkeley DB database environments.
+.PP
+The db5.2_hotbackup utility performs the following steps:
+.RS
+.IP 1.
+If the \-c option is specified, checkpoint the source home database
+environment, and remove any unnecessary log files.
+.IP 2.
+If the target directory for the backup does not exist, it is created with mode
+read-write-execute for the owner.
+.sp
+If the target directory for the backup does exist and the \-u option was
+specified, all log files in the target directory are removed; if the \-u option
+was not specified, all files in the target directory are removed.
+.IP 3.
+If the \-u option was not specified, copy application-specific files found in
+the database environment home directory, or any directory specified using the
+-d option, into the target directory for the backup.
+.IP 4.
+Copy all log files found in the directory specified by the \-l option (or in the
+database environment home directory, if no \-l option was specified), into the
+target directory for the backup.
+.IP 5.
+Perform catastrophic recovery on the hot backup.
+.IP 6.
+Remove any unnecessary log files from the hot backup.
+.RE
+.PP
+The db5.2_hotbackup utility does not resolve pending transactions that are in the
+prepared state. Applications that use DB_TXN->prepare should specify
+DB_RECOVER_FATAL when opening the environment, and run DB_ENV->txn_recover to
+resolve any pending transactions, when failing over to the hot backup.
+.SH OPTIONS
+.IP \fB\-b\fR
+Specify the target directory for the backup.
+.IP \fB\-c\fR
+Before performing the snapshot, checkpoint the source database environment
+and remove any log files that are no longer required in that environment.
+\fBTo avoid making catastrophic failure impossible, log file removal
+must be integrated with log file archival.\fR
+.IP \fB\-d\fR
+Specify one or more source directories that contain databases; if none
+is specified, the database environment home directory will be searched
+for database files. As database files are copied into a single backup
+directory, files named the same, stored in different source directories,
+could overwrite each other when copied into the backup directory.
+.IP \fB\-h\fR
+Specify the source directory for the backup, that is, the database
+environment home directory.
+.IP \fB\-l\fR
+Specify a source directory that contains log files; if none is specified,
+the database environment home directory will be searched for log files.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-u\fR
+Update a pre-existing hot backup snapshot by copying in new log files.
+If the \fB\-u\fR option is specified, no databases will be copied
+into the target directory.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.IP \fB\-v\fR
+Run in verbose mode, listing operations as they are done.
+.IP \fB\-D\fR
+Use the data directories listed in the DB_CONFIG configuration
+file in the source directory. This option has three effects:
+First, if they do not already exist, the specified data directories
+will be created relative to the target directory (with mode read-write-execute
+owner). Second, all files in the source data directories will be copied to
+the target data directories. If the DB_CONFIG file specifies one
+or more absolute pathnames, files in those source directories will be
+copied to the top-level target directory. Third, the DB_CONFIG configuration
+file will be copied from the +source directory to the target directory, and
+subsequently used for configuration if recovery is run in the target directory.
+.PP
+Care should be taken with the \fB-D\fR option and data directories
+which are named relative to the source directory but are not
+subdirectories (that is, the name includes the element "..")
+Specifically, the constructed target directory names must be meaningful
+and distinct from the source directory names, otherwise running recovery
+in the target directory might corrupt the source data files.
+.PP
+\fBIt is an error to use absolute pathnames for data directories
+or the log directory in this mode, as the DB_CONFIG configuration
+file copied into the target directory would then point at the source
+directories and running recovery would corrupt the source data files.\fR
+.PP
+The db5.2_hotbackup utility uses a Berkeley DB environment (as described for the
+\fB\-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_hotbackup should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_hotbackup
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_hotbackup utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Oracle Corporation. This manual page was created based on
+the HTML documentation for db_hotbackup from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_load.1 b/debian/manpages/db5.2_load.1
new file mode 100644
index 0000000..22c1fec
--- /dev/null
+++ b/debian/manpages/db5.2_load.1
@@ -0,0 +1,186 @@
+.\" Manual Page for Berkeley DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_LOAD 1 "22 November 2009"
+.SH NAME
+db5.2_load \- Load data from standard input
+.SH SYNOPSIS
+.B db5.2_load
+[-nTV] [-c name=value] [-f file] [-h home] [-P password] [-t btree | hash | queue | recno] file
+
+.B db5.2_load
+[-r lsn | fileid] [-h home] [-P password] file
+.SH DESCRIPTION
+The db5.2_load utility reads from the standard input and loads it into the
+database file. The database file is created if it does not already exist.
+.PP
+The input to db5.2_load must be in the output format specified by the db5.0_dump
+utility, utilities, or as specified for the -T below.
+.SH OPTIONS
+.IP \fB\-c\fR
+Specify configuration options ignoring any value they may have based on
+the input. The command-line format is \fBname=value\fR. See the
+Supported Keywords section below for a list of keywords supported by
+the \fB-c\fR option.
+.IP \fB\-f\fR
+Read from the specified \fBinput\fR file instead of from the standard
+input.
+.IP \fB\-h\fR
+Specify a home directory for the database environment.
+.sp
+If a home directory is specified, the database environment is opened
+using the DB_INIT_LOCK, DB_INIT_LOG, DB_INIT_MPOOL, DB_INIT_TXN, and
+DB_USE_ENVIRON flags to DB_ENV->open. (This means that db5.2_load can be
+used to load data into databases while they are in use by other
+processes.) If the DB_ENV->open call fails, or if no home
+directory is specified, the database is still updated, but the
+environment is ignored; for example, no locking is done.
+.IP \fB\-n\fR
+Do not overwrite existing keys in the database when loading into an
+already existing database. If a key/data pair cannot be loaded into the
+database for this reason, a warning message is displayed on the standard
+error output, and the key/data pair are skipped.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-r\fR
+Reset the database's file ID or log sequence numbers (LSNs).
+.sp
+All database pages in transactional environments contain references to
+the environment's log records. In order to copy a database into a
+different database environment, database page references to the old
+environment's log records must be reset, otherwise data corruption can
+occur when the database is modified in the new environment. The
+\fB-r\fR \fBlsn\fR option resets a database's log sequence
+numbers.
+.sp
+All databases contain an ID string used to identify the database in the
+database environment cache. If a database is copied, and used in the
+same environment as another file with the same ID string, corruption can
+occur. The \fB-r\fR \fBfileid\fR option resets a database's file
+ID to a new value.
+.sp
+\fBIn both cases, the physical file specified by the file argument
+is modified in-place.\fR
+.IP \fB\-T\fR
+The \fB-T\fR option allows non-Berkeley DB applications to easily load text
+files into databases.
+.sp
+If the database to be created is of type Btree or Hash, or the keyword
+\fBkeys\fR is specified as set, the input must be paired lines of text,
+where the first line of the pair is the key item, and the second line of
+the pair is its corresponding data item. If the database to be created
+is of type Queue or Recno and the keyword \fBkeys\fR is not set, the
+input must be lines of text, where each line is a new data item for the
+database.
+.sp
+A simple escape mechanism, where newline and backslash (\\)
+characters are special, is applied to the text input. Newline characters
+are interpreted as record separators. Backslash characters in the text
+will be interpreted in one of two ways: If the backslash character
+precedes another backslash character, the pair will be interpreted as a
+literal backslash. If the backslash character precedes any other
+character, the two characters following the backslash will be interpreted
+as a hexadecimal specification of a single character; for example,
+\\0a is a newline character in the ASCII character set.
+.sp
+For this reason, any backslash or newline characters that naturally
+occur in the text input must be escaped to avoid misinterpretation by
+db5.2_load.
+.sp
+If the \fB-T\fR option is specified, the underlying access method type
+must be specified using the \fB-t\fR option.
+.IP \fB\-t\fR
+Specify the underlying access method. If no \fB-t\fR option is
+specified, the database will be loaded into a database of the same type
+as was dumped; for example, a Hash database will be created if a Hash
+database was dumped.
+.sp
+Btree and Hash databases may be converted from one to the other. Queue
+and Recno databases may be converted from one to the other. If the
+\fB-k\fR option was specified on the call to db5.2_dump then Queue
+and Recno databases may be converted to Btree or Hash, with the key being
+the integer record number.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.PP
+The db5.2_load utility may be used with a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_load should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_load
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_load utility exits 0 on success, 1 if one or more key/data
+pairs were not loaded into the database because the key already existed,
+and >1 if an error occurs.
+.SH EXAMPLES
+The db5.2_load utility can be used to load text files into databases.
+For example, the following command loads the standard UNIX
+\fI/etc/passwd\fR file into a database, with the login name as the
+key item and the entire password entry as the data item:
+.PP
+.TP 8
+awk \-F: '{print $1; print $0}' < /etc/passwd |
+sed 's/\\\\/\\\\\\\\/g' | db5.2_load \-T \-t hash passwd.db
+.PP
+Note that backslash characters naturally occurring in the text are escaped
+to avoid interpretation as escape characters by db5.2_load.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH SUPPORTED KEYWORDS
+The following keywords are supported for the \fB-c\fR command-line
+ption to the db5.2_load utility. See DB->open for further
+discussion of these keywords and what values should be specified.
+.PP
+The parenthetical listing specifies how the value part of the
+\fBname=value\fR pair is interpreted. Items listed as (boolean)
+expect value to be \fB1\fR (set) or \fB0\fR (unset). Items listed
+as (number) convert value to a number. Items listed as (string) use
+the string value without modification.
+.IP "bt_minkey (number)"
+The minimum number of keys per page.
+.IP "chksum (boolean)"
+Enable page checksums.
+.IP "database (string)"
+The database to load.
+.IP "db_lorder (number)"
+The byte order for integers in the stored database metadata.
+.IP "db_pagesize (number)"
+The size of database pages, in bytes.
+.IP "duplicates (boolean)"
+The value of the DB_DUP flag.
+.IP "dupsort (boolean)"
+The value of the DB_DUPSORT flag.
+.IP "extentsize (number)"
+The size of database extents, in pages, for Queue databases configured
+to use extents.
+.IP "h_ffactor (number)"
+The density within the Hash database.
+.IP "h_nelem (number)"
+The size of the Hash database.
+.IP "keys (boolean)"
+Specify whether keys are present for Queue or Recno databases.
+.IP "re_len (number)"
+Specify fixed-length records of the specified length.
+.IP "re_pad (string)"
+Specify the fixed-length record pad character.
+.IP "recnum (boolean)"
+The value of the DB_RECNUM flag.
+.IP "renumber (boolean)"
+The value of the DB_RENUMBER flag.
+.IP "subdatabase (string)"
+The subdatabase to load.
+
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_load from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_printlog.1 b/debian/manpages/db5.2_printlog.1
new file mode 100644
index 0000000..5f1fc22
--- /dev/null
+++ b/debian/manpages/db5.2_printlog.1
@@ -0,0 +1,59 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_PRINTLOG 1 "28 January 2005"
+.SH NAME
+db5.2_printlog \- Dumps Berkeley DB log files in a human-readable format
+.SH SYNOPSIS
+.B db5.2_printlog
+[-NrV] [-b start-LSN] [-e stop-LSN] [-h home] [-P password]
+.SH DESCRIPTION
+The db5.2_printlog utility is a debugging utility that dumps Berkeley DB log files
+in a human-readable format.
+.SH OPTIONS
+.IP \fB\-b\fR
+Display log records starting at log sequence number (LSN) \fBstart-LSN\fR;
+\fBstart-LSN\fR is specified as a file number, followed by a slash (/)
+character, followed by an offset number, with no intervening whitespace.
+.IP \fB\-e\fR
+Stop displaying log records at log sequence number (LSN) \fBstop-LSN\fR;
+\fBstop-LSN\fR is specified as a file number, followed by a slash (/)
+character, followed by an offset number, with no intervening whitespace.
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-N\fR
+Do not acquire shared region mutexes while running. Other problems,
+such as potentially fatal errors in Berkeley DB, will be ignored as well.
+This option is intended only for debugging errors, and should not be
+used under any other circumstances.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-r\fR
+Read the log files in reverse order.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.PP
+The db5.2_printlog utility uses a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_printlog should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_printlog
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_printlog utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_printlog from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_recover.1 b/debian/manpages/db5.2_recover.1
new file mode 100644
index 0000000..d222f4d
--- /dev/null
+++ b/debian/manpages/db5.2_recover.1
@@ -0,0 +1,95 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_RECOVER 1 "28 January 2005"
+.SH NAME
+db5.2_recover \- Restore the database to a consistent state
+.SH SYNOPSIS
+.B db5.2_recover
+[-ceVv] [-h home] [-P password] [-t [[CC]YY]MMDDhhmm[.SS]]]
+.SH DESCRIPTION
+The db5.2_recover utility must be run after an unexpected application, Berkeley
+DB, or system failure to restore the database to a consistent state. All
+committed transactions are guaranteed to appear after db5.2_recover has run, and
+all uncommitted transactions will be completely undone.
+.SH OPTIONS
+.IP \fB\-c\fR
+Perform catastrophic recovery instead of normal recovery.
+.IP \fB\-e\fR
+Retain the environment after running recovery. This option
+will rarely be used unless a DB_CONFIG file is present in the home
+directory. If a DB_CONFIG file is not present, then the regions will be
+created with default parameter values.
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-t\fR
+Recover to the time specified rather than to the most current possible
+date. The timestamp argument should be in the form
+[[CC]YY]MMDDhhmm[.SS] where each pair of
+letters represents the following:
+.RS
+.IP CC
+The first two digits of the year (the century).
+.IP YY
+The second two digits of the year. If "YY" is specified, but "CC" is not,
+a value for "YY" between 69 and 99 results in a "CC" value of 19. Otherwise,
+a "YY" value of 20 is used.
+.IP MM
+The month of the year, from 1 to 12.
+.IP DD
+The day of the month, from 1 to 31.
+.IP hh
+The hour of the day, from 0 to 23.
+.IP mm
+The minute of the hour, from 0 to 59.
+.IP SS
+The second of the minute, from 0 to 61.
+.RE
+.IP
+If the "CC" and "YY" letter pairs are not specified, the values default
+to the current year. If the "SS" letter pair is not specified, the value
+defaults to 0.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.IP \fB\-v\fR
+Run in verbose mode.
+.PP
+In the case of catastrophic recovery, an archival copy - or
+\fIsnapshot\fR - of all database files must be restored along with
+all of the log files written since the database file snapshot was made.
+(If disk space is a problem, log files may be referenced by symbolic
+links).
+.PP
+If the failure was not catastrophic, the files present on the system at the
+time of failure are sufficient to perform recovery.
+.PP
+If log files are missing, db5.2_recover will identify the missing
+log file(s) and fail, in which case the missing log files need to be
+restored and recovery performed again.
+.PP
+The db5.2_recover utility uses a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_recover should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_recover
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_recover utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_recover from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_stat.1 b/debian/manpages/db5.2_stat.1
new file mode 100644
index 0000000..b6265bc
--- /dev/null
+++ b/debian/manpages/db5.2_stat.1
@@ -0,0 +1,127 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_STAT 1 "28 January 2005"
+.SH NAME
+db5.2_stat \- Display statistics for Berkeley DB environments
+.SH SYNOPSIS
+.B db5.2_stat
+-d file [-fN] [-h home] [-P password] [-s database]
+
+.B db5.2_stat
+[-cEelmNrtVZ] [-C Aclop] [-h home] [-L A] [-M A] [-R A] [-P password]
+.SH DESCRIPTION
+The db5.2_stat utility displays statistics for Berkeley DB environments.
+.SH OPTIONS
+.IP \fB\-C\fR
+Display internal information about the locking subsystem. (The output
+from this option is often both voluminous and meaningless, and is
+intended only for debugging.)
+.RS
+.IP A
+Display all information.
+.IP c
+Display lock conflict matrix.
+.IP l
+Display lockers within hash chains.
+.IP o
+Display lock objects within hash chains.
+.IP p
+Display locking subsystem parameters.
+.RE
+.IP \fB\-c\fR
+Display locking subsystem statistics, as described in DB_ENV->lock_stat.
+.IP \fB\-d\fR
+Display database statistics for the specified file, as described in
+DB->stat.
+.sp
+If the database contains multiple databases and the \fB-s\fR flag is
+not specified, the statistics are for the internal database that describes
+the other databases the file contains, and not for the file as a whole.
+.IP \fB\-E\fR
+Display internal information about the database environment, including
+all configured subsystems of the database environment. (The
+output from this option is often both voluminous and meaningless, and
+is intended only for debugging.)
+.IP \fB\-e\fR
+Display information about the database environment, including
+all configured subsystems of the database environment.
+.IP \fB\-f\fR
+Display only those database statistics that can be
+acquired without traversing the database.
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-l\fR
+Display logging subsystem statistics, as described in DB_ENV->log_stat.
+.IP \fB\-M\fR
+Display internal information about the cache. (The output from this
+option is often both voluminous and meaningless, and is intended only
+for debugging.)
+.RS
+.IP A
+Display all information.
+.IP h
+Display buffers within hash chains.
+.RE
+.IP \fB\-m\fR
+Display cache statistics, as described in DB_ENV->memp_stat.
+.IP \fB\-N\fR
+Do not acquire shared region mutexes while running. Other problems,
+such as potentially fatal errors in Berkeley DB, will be ignored as well.
+This option is intended only for debugging errors, and should not be
+used under any other circumstances.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-R\fR
+Display internal information about the replication subsystem. (The
+output from this option is often both voluminous and meaningless, and
+is intended only for debugging.)
+.RS
+.IP A
+Display all information.
+.RE
+.IP \fB\-r\fR
+Display replication statistics, as described in DB_ENV->rep_stat.
+.IP \fB\-s\fR
+Display statistics for the specified database contained in the file
+specified with the \fB-d\fR flag.
+.IP \fB\-t\fR
+Display transaction subsystem statistics, as described in DB_ENV->txn_stat.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.IP \fB\-Z\fR
+Reset the statistics after reporting them; valid only with the \fB-C\fR,
+\fB-c\fR, \fB-E\fR, \fB-e\fR, \fB-L\fR, \fB-l\fR,
+\fB-M\fR, \fB-m\fR, \fB-R\fR, \fB-r\fR, and \fB-t\fR
+options.
+.PP
+Values normally displayed in quantities of bytes are displayed as a
+combination of gigabytes (GB), megabytes (MB), kilobytes (KB), and bytes
+(B). Otherwise, values smaller than 10 million are displayed without
+any special notation, and values larger than 10 million are displayed
+as a number followed by "M".
+.PP
+The db5.2_stat utility may be used with a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_stat should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_stat
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_stat utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_stat from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_upgrade.1 b/debian/manpages/db5.2_upgrade.1
new file mode 100644
index 0000000..4433af0
--- /dev/null
+++ b/debian/manpages/db5.2_upgrade.1
@@ -0,0 +1,81 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_UPGRADE 1 "28 January 2005"
+.SH NAME
+db5.2_upgrade \- Upgrade the Berkeley DB version to the current release version.
+.SH SYNOPSIS
+.B db5.2_upgrade
+[-NsVv] [-h home] [-P password] file ...
+.SH DESCRIPTION
+The db5.2_upgrade utility upgrades the Berkeley DB version of one or more files
+and the databases they contain to the current release version.
+.SH OPTIONS
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-N\fR
+Do not acquire shared region mutexes while running. Other problems,
+such as potentially fatal errors in Berkeley DB, will be ignored as well.
+This option is intended only for debugging errors, and should not be
+used under any other circumstances.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-s\fR
+This flag is only meaningful when upgrading databases from releases
+before the Berkeley DB 3.1 release.
+.sp
+As part of the upgrade from the Berkeley DB 3.0 release to the 3.1 release,
+the on-disk format of duplicate data items changed. To correctly upgrade
+the format requires that applications specify whether duplicate data
+items in the database are sorted or not. Specifying the \fB-s\fR
+flag means that the duplicates are sorted; otherwise, they are assumed
+to be unsorted. Incorrectly specifying the value of this flag may lead
+to database corruption.
+.sp
+Because the db5.2_upgrade utility upgrades a physical file
+(including all the databases it contains), it is not possible to use
+db5.2_upgrade to upgrade files where some of the databases it
+includes have sorted duplicate data items, and some of the databases it
+includes have unsorted duplicate data items. If the file does not have
+more than a single database, if the databases do not support duplicate
+data items, or if all the databases that support duplicate data items
+support the same style of duplicates (either sorted or unsorted),
+db5.2_upgrade will work correctly as long as the \fB-s\fR flag
+is correctly specified. Otherwise, the file cannot be upgraded using
+db5.2_upgrade, and must be upgraded manually using the
+db5.2_dump and db5.0_load utilities.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.IP \fB\-v\fR
+Run in verbose mode, displaying a message for each successful upgrade.
+.PP
+\fBIt is important to realize that Berkeley DB database upgrades are done
+in place, and so are potentially destructive.\fR This means that if the
+system crashes during the upgrade procedure, or if the upgrade procedure
+runs out of disk space, the databases may be left in an inconsistent and
+unrecoverable state.
+.PP
+The db5.2_upgrade utility may be used with a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_upgrade should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_upgrade
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_upgrade utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_upgrade from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/manpages/db5.2_verify.1 b/debian/manpages/db5.2_verify.1
new file mode 100644
index 0000000..f3d2cfb
--- /dev/null
+++ b/debian/manpages/db5.2_verify.1
@@ -0,0 +1,69 @@
+.\" Manual Page for Berkely DB utils, created from upstream
+.\" documentation by Thijs Kinkhorst <thijs at kinkhorst.com>.
+.TH DB5.2_VERIFY 1 "28 January 2005"
+.SH NAME
+db5.2_verify \- Verifies the structure databases
+.SH SYNOPSIS
+.B db5.2_verify
+[-NoqV] [-h home] [-P password] file ...
+.SH DESCRIPTION
+The db5.2_verify utility verifies the structure of one or more files and the
+databases they contain.
+.SH OPTIONS
+.IP \fB\-h\fR
+Specify a home directory for the database environment; by
+default, the current working directory is used.
+.IP \fB\-o\fR
+Skip the database checks for btree and duplicate sort order and for
+hashing.
+.sp
+If the file being verified contains databases with non-default
+comparison or hashing configurations, calling the db5.2_verify
+utility without the \fB-o\fR flag will usually return failure. The
+\fB-o\fR flag causes db5.2_verify to ignore database sort or
+hash ordering and allows db5.2_verify to be used on these files.
+To fully verify these files, verify them explicitly using the
+DB->verify method, after configuring the correct comparison or hashing
+functions.
+.IP \fB\-N\fR
+Do not acquire shared region mutexes while running. Other problems,
+such as potentially fatal errors in Berkeley DB, will be ignored as well.
+This option is intended only for debugging errors, and should not be
+used under any other circumstances.
+.IP \fB\-P\fR
+Specify an environment password. Although Berkeley DB utilities overwrite
+password strings as soon as possible, be aware there may be a window of
+vulnerability on systems where unprivileged users can see command-line
+arguments or where utilities are not able to overwrite the memory
+containing the command-line arguments.
+.IP \fB\-q\fR
+Suppress the printing of any error descriptions, simply exit success or
+failure.
+.IP \fB\-V\fR
+Write the library version number to the standard output, and exit.
+.PP
+\fBThe db5.2_verify utility does not perform any locking, even in
+Berkeley DB environments that are configured with a locking subsystem. As
+such, it should only be used on files that are not being modified by
+another thread of control.\fR
+.PP
+The db5.2_verify utility may be used with a Berkeley DB environment (as described for the
+\fB-h\fR option, the environment variable \fBDB_HOME\fR, or
+because the utility was run in a directory containing a Berkeley DB
+environment). In order to avoid environment corruption when using a
+Berkeley DB environment, db5.2_verify should always be given the chance to
+detach from the environment and exit gracefully. To cause db5.2_verify
+to release all environment resources and exit cleanly, send it an
+interrupt signal (SIGINT).
+.PP
+The db5.2_verify utility exits 0 on success, and >0 if an error occurs.
+.SH ENVIRONMENT
+.IP \fBDB_HOME\fR
+If the \fB-h\fR option is not specified and the environment variable
+DB_HOME is set, it is used as the path of the database home, as described
+in DB_ENV->open.
+.SH AUTHORS
+Sleepycat Software, Inc. This manual page was created based on
+the HTML documentation for db_verify from Sleepycat,
+by Thijs Kinkhorst <thijs at kinkhorst.com>,
+for the Debian system (but may be used by others).
diff --git a/debian/patches/002-versioned_symbols.patch b/debian/patches/002-versioned_symbols.patch
index 88eeb6a..5ea6219 100644
--- a/debian/patches/002-versioned_symbols.patch
+++ b/debian/patches/002-versioned_symbols.patch
@@ -6,7 +6,7 @@
+Versions: $(C_OBJS)
+ rm -f $@
-+ printf "DB5_0 {\n global:\n" > $@
++ printf "DB5_2 {\n global:\n" > $@
+ nm $$(sed -n "/^pic_object='\(.*\)'$$/ { s//\1/;s,.libs/,,;p;}" $(C_OBJS)) | grep " [DTR] " | cut -d" " -f3 | sed -e 's/$$/;/' >> $@
+ printf "local: *; };\n" >> $@
+
diff --git a/debian/rules b/debian/rules
index 0d7b526..62c3363 100755
--- a/debian/rules
+++ b/debian/rules
@@ -68,11 +68,11 @@ CONFIGURE_SWITCHES += --enable-java
DH_PLUGINS += --with=javahelper
else
CONFIGURE_SWITCHES += --disable-java
-DH_OPTIONS += -Nlibdb5.1-java -Nlibdb5.1-java-dev -Nlibdb5.1-java-gcj
+DH_OPTIONS += -Nlibdb5.2-java -Nlibdb5.2-java-dev -Nlibdb5.2-java-gcj
endif
ifeq (no,$(ENABLE_GCJ))
-DH_OPTIONS += -Nlibdb5.1-java-gcj
+DH_OPTIONS += -Nlibdb5.2-java-gcj
endif
@@ -83,8 +83,8 @@ VERY_BROKEN_SYSTEMS =
export DH_OPTIONS
-package=db5.1
-bdbversion=5.1
+package=db5.2
+bdbversion=5.2
version=$(shell expr `pwd` : '.*-\([0-9.]*\)')
version_major=$(shell expr `pwd` : '.*-\([0-9]*\).[0-9.]*')
@@ -158,11 +158,11 @@ override_dh_install:
tcltk-depends
override_dh_installdocs:
- dh_installdocs -pdb5.1-doc
- dh_installdocs --remaining-packages --link-doc=libdb5.1
+ dh_installdocs -pdb5.2-doc
+ dh_installdocs --remaining-packages --link-doc=libdb5.2
override_dh_strip:
- dh_strip -s --dbg-package=libdb5.1-dbg
+ dh_strip -s --dbg-package=libdb5.2-dbg
override_dh_clean:
DH_OPTIONS="" dh_clean
--
Berkeley DB Debian packaging
More information about the pkg-db-commits
mailing list