[OpenIndiana-discuss] OpenLDAP and BerkeleyDB

[Michal Nowak]

On 12/18/18 06:33 PM, Dieter Klünter wrote:
> Am Tue, 18 Dec 2018 14:01:47 +0100
> schrieb "Michal Nowak" <mnowak at startmail.com>:
> 
>> On Tuesday, December 18, 2018 at 9:10 AM, Michal Nowak
>> <mnowak at startmail.com> wrote:
>>> On 12/17/18 09:54 PM, Dieter Klünter wrote:
>>>> Hi,
>>>> I'm trying to get OpenLDAP running, but a BDB library mismatch
>>>> prevents it :-(
>>>>
>>>> bdb_back_initialize: BDB library version mismatch: expected
>>>> Berkeley DB 5.3.21: (May 11, 2012), got Berkeley DB 5.3.28:
>>>> (September  9, 2013
>>>>
>>>> OpenLDAP: slapd 2.4.44 (Feb 11 2018 07:52:01) $
>>>> @hipster.openindiana.org:/jenkins/jobs/oi-userland/workspace/components/network/openldap/build/amd64/servers/slapd
>>>>
>>>>
>>>> Whoever built this package,  PLEASE either stick to library
>>>> conformance or, even better, refrain from building slapd with
>>>> BerkeleyDB, as this is deprecated, the announcement has been made
>>>> at LDAPCon 2007. If you have to stick to BerkeleyDB build back_bdb
>>>> and back_hdb as modules.
>>>>
>>>> -Dieter
>>>
>>> Hello Dieter,
>>>
>>> I am sorry for the problem with OpenLDAP, it was caused by updated
>>> BerkeleyDB.
>>>
>>> I created a request for OpenLDAP to be rebuild
>>> (https://github.com/OpenIndiana/oi-userland/pull/4657), after that
>>> slapd should initialize correctly.
>>
>> Dieter,
>>
>> this is now released as library/openldap at 2.4.44,5.11-2018.0.0.1. Does
>> it work for you?
> 
> I receive some pkg errors, so i have to wait a few days :-)
> 
> pkg update: No matching version of library/openldap can be installed:
>   Reject: pkg://openindiana.org/library/openldap@2.4.44-2018.0.0.1
> 
> AFAI understand, this package has not been distributed yet.
> 
> -Dieter
> 

I just installed it on a different system, so it is distributed via 
openindiana.org publisher. What is the full reject reason output? Note 
that common problem is that you can't update newer package on a host 
which wasn't updated for many months, `pkg update -v` and boot to new BE 
is the solution in such a case.

Michal