Bug#651700: [Pkg-openldap-devel] Bug#651700: slapd: BDB library version mismatch
Hi Quanah, On Mon, Dec 12, 2011 at 01:35:50PM -0800, Quanah Gibson-Mount wrote: OpenLDAP was compiled using 5.1.25, and the libs were updated to 5.1.29. OpenLDAP *must* be recompiled against 5.1.29 as well in that case. If that is done, then everything will move along happily. This is by design because Oracle/Sleepycat has made API changes in patch level releases before. back-hdb/bdb *must* be compiled against the exact BDB library version they are linked to. In this case, the patch level does matter. On Mon, Dec 12, 2011 at 01:58:13PM -0800, Quanah Gibson-Mount wrote: --On Monday, December 12, 2011 10:54 PM +0100 Julien Cristau jcris...@debian.org wrote: If bdb breaks ABI then it needs to bump SONAME. If it doesn't then apps compiled against an earlier version must still work. A check for the patchlevel version is just broken. Feel free to take that up with Oracle. ;) Until they fix their development practices, the OpenLDAP behavior remains. Under the circumstances that seems a perfectly reasonable behavior for upstream to implement, but in Debian we hold libraries to a higher standard. If the library *does* change its ABI, the package name in Debian will change even if upstream fails to handle this, so the check within OpenLDAP is redundant; and in cases where Oracle releases a patchlevel release that doesn't change the ABI, this actively works against the packaging system. So I think the correct course of action here is to patch this check out of the Debian package. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#651700: [Pkg-openldap-devel] Bug#651700: slapd: BDB library version mismatch
--On Monday, December 12, 2011 1:29 PM -0800 Quanah Gibson-Mount qua...@zimbra.com wrote: --On Sunday, December 11, 2011 12:14 PM +0100 stor...@club-internet.fr jp.po...@izzop.net wrote: Package: slapd Version: 2.4.25-4+b1 Severity: important Dear Maintainer, I think that the openldap package was not compiled with the last version : bdb_back_initialize: BDB library version mismatch: expected Berkeley DB 5.1.25: (January 28, 2011) got Berkeley DB 5.1.29: (October 25, 2011). slapd stopped. Actually this indicates that OpenLDAP was recompiled with the latest BDB version (5.1.29). It is complaining about the fact that your database was created using the 5.1.25 version, and thus it refuses to start. Ugh, nm, misread that. OpenLDAP was compiled using 5.1.25, and the libs were updated to 5.1.29. OpenLDAP *must* be recompiled against 5.1.29 as well in that case. If that is done, then everything will move along happily. This is by design because Oracle/Sleepycat has made API changes in patch level releases before. back-hdb/bdb *must* be compiled against the exact BDB library version they are linked to. In this case, the patch level does matter. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. Zimbra :: the leader in open source messaging and collaboration -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651700: [Pkg-openldap-devel] Bug#651700: slapd: BDB library version mismatch
--On Sunday, December 11, 2011 12:14 PM +0100 stor...@club-internet.fr jp.po...@izzop.net wrote: Package: slapd Version: 2.4.25-4+b1 Severity: important Dear Maintainer, I think that the openldap package was not compiled with the last version : bdb_back_initialize: BDB library version mismatch: expected Berkeley DB 5.1.25: (January 28, 2011) got Berkeley DB 5.1.29: (October 25, 2011). slapd stopped. Actually this indicates that OpenLDAP was recompiled with the latest BDB version (5.1.29). It is complaining about the fact that your database was created using the 5.1.25 version, and thus it refuses to start. The correct behavior on Debian's part is to export the database(s) prior to updating the BDB library via slapcat, and then reimport it via slapadd post upgrade. OpenLDAP is working as designed. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. Zimbra :: the leader in open source messaging and collaboration -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651700: [Pkg-openldap-devel] Bug#651700: slapd: BDB library version mismatch
On Mon, Dec 12, 2011 at 13:35:50 -0800, Quanah Gibson-Mount wrote: OpenLDAP was compiled using 5.1.25, and the libs were updated to 5.1.29. OpenLDAP *must* be recompiled against 5.1.29 as well in that case. If that is done, then everything will move along happily. This is by design because Oracle/Sleepycat has made API changes in patch level releases before. back-hdb/bdb *must* be compiled against the exact BDB library version they are linked to. In this case, the patch level does matter. If bdb breaks ABI then it needs to bump SONAME. If it doesn't then apps compiled against an earlier version must still work. A check for the patchlevel version is just broken. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651700: [Pkg-openldap-devel] Bug#651700: slapd: BDB library version mismatch
--On Monday, December 12, 2011 10:54 PM +0100 Julien Cristau jcris...@debian.org wrote: On Mon, Dec 12, 2011 at 13:35:50 -0800, Quanah Gibson-Mount wrote: OpenLDAP was compiled using 5.1.25, and the libs were updated to 5.1.29. OpenLDAP *must* be recompiled against 5.1.29 as well in that case. If that is done, then everything will move along happily. This is by design because Oracle/Sleepycat has made API changes in patch level releases before. back-hdb/bdb *must* be compiled against the exact BDB library version they are linked to. In this case, the patch level does matter. If bdb breaks ABI then it needs to bump SONAME. If it doesn't then apps compiled against an earlier version must still work. A check for the patchlevel version is just broken. Feel free to take that up with Oracle. ;) Until they fix their development practices, the OpenLDAP behavior remains. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. Zimbra :: the leader in open source messaging and collaboration -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
