[Pkg-openldap-devel] Bug#593550: Bug#593550: Bug#593550: Bug#593550: A fix

Matthijs Mohlmann matthijs at cacholong.nl
Fri Aug 20 11:06:18 UTC 2010

On Aug 19, 2010, at 11:19 PM, Russ Allbery wrote:

> Quanah Gibson-Mount <quanah at zimbra.com> writes:
>> Michael Rasmussen <mir at datanom.net> wrote:
>>> Quanah Gibson-Mount <quanah at zimbra.com> wrote:
>>>> What version was being migrated from (i.e., what version of BDB was
>>>> openldap linked against?).  If it was prior to BDB 4.8, then you have
>>>> to do a slapcat/slapadd of the database (I assume that's already being
>>>> done), but before that, it is critical to completely checkpoint the
>>>> database via db_recover (one of the steps taken above).
>>> I think this is the key question. Apparently the db-tools cannot handle
>>> a migration from <= 4.7 to 4.8 in which case the only reliable way to
>>> do this is slapcat/slapadd.
>> Correct, it is never possible to use db-tools to upgrade OpenLDAP
>> Databases across BDB versions.  The only method is slapcat/slapadd.
> Right, and the package already has all the logic to do that already.  I
> think the only problem here is that it didn't trigger when it should have
> for your installation.  Maybe the version number for the check for when to
> do this isn't quite right?
>> I'd also note that BDB 4.8 versions prior to 4.8.30 are not reliable and
>> should be avoided (Not sure what's in debian atm).
> 4.8.30 is in unstable and will migrate to testing as soon as we figure out
> what's going on with the mips and sparc builds.

This has to do with gcj on these platforms which are fixed already, but probably
the build is not ready on those platforms. I have to check if gcj is already
build and then db4.8 can be rescheduled on those platforms.


Matthijs Möhlmann

More information about the Pkg-openldap-devel mailing list