Adding debian version 2.4.47+dfsg-3+deb10u7.debian/2.4.47+dfsg-3+deb10u7debian

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 42 insertions, 0 deletions

diff --git a/debian/patches/no-bdb-ABI-second-guessing b/debian/patches/no-bdb-ABI-second-guessing
new file mode 100644
index 0000000..db76aa7
--- /dev/null
+++ b/debian/patches/no-bdb-ABI-second-guessing
@@ -0,0 +1,42 @@
+Author: Steve Langasek <vorlon@debian.org>
+Description: don't second-guess BDB ABI
+ OpenLDAP upstream conservatively assumes that any change to the version
+ number of libdb can result in an API-breaking change that could impact
+ the database.  In Debian, we know that such changes require bumping the
+ library soname and changing the package name, and demand such rigor from
+ our package maintainers even when upstreams don't deliver; so any such
+ check in the source code works against the packaging system by forcing
+ database upgrades when we know none are required.  Disable this check
+ so we rely on the packaging system to do its job.
+Bug-Debian: http://bugs.debian.org/651333
+Forwarded: not-needed
+
+--- a/servers/slapd/back-bdb/init.c
++++ b/servers/slapd/back-bdb/init.c
+@@ -762,7 +762,7 @@ bdb_back_initialize(
+ 	bi->bi_controls = controls;
+ 
+ 	{	/* version check */
+-		int major, minor, patch, ver;
++		int major, minor, patch;
+ 		char *version = db_version( &major, &minor, &patch );
+ #ifdef HAVE_EBCDIC
+ 		char v2[1024];
+@@ -776,17 +776,6 @@ bdb_back_initialize(
+ 		version = v2;
+ #endif
+ 
+-		ver = (major << 24) | (minor << 16) | patch;
+-		if( ver != DB_VERSION_FULL ) {
+-			/* fail if a versions don't match */
+-			Debug( LDAP_DEBUG_ANY,
+-				LDAP_XSTRING(bdb_back_initialize) ": "
+-				"BDB library version mismatch:"
+-				" expected " DB_VERSION_STRING ","
+-				" got %s\n", version, 0, 0 );
+-			return -1;
+-		}
+-
+ 		Debug( LDAP_DEBUG_TRACE, LDAP_XSTRING(bdb_back_initialize)
+ 			": %s\n", version, 0, 0 );
+ 	}