Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Mar 2011 13:48:59 -0700
From:      Xin LI <delphij@delphij.net>
To:        Kevin Oberman <oberman@es.net>
Cc:        ports@FreeBSD.ORG, umq@ueo.co.jp, Doug Barton <dougb@FreeBSD.ORG>, delphij@FreeBSD.ORG
Subject:   Re: Unable to configure dirmngr after openldap upgrade
Message-ID:  <4D90F43B.7050606@delphij.net>
In-Reply-To: <20110328194251.9F2FE1CC0C@ptavv.es.net>
References:  <20110328194251.9F2FE1CC0C@ptavv.es.net>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/28/11 12:42, Kevin Oberman wrote:
> Yup. openldap-client-2.4.24 does fine. Looks like a bug in 2.4.25. I'll
> take a look at CHANGES and see if I can figure out what broke the
> inclusion of fetch(3) support if I get a bit of time.

It seems that libldif now referenced the fetch support, and ironically
it seem be a bug but a feature :(

I have decided to disable FETCH support from now on, since it's likely
to bring more problems.

(If you would prefer to fix the problem for this specific problem, I
think adding a '-lfetch' would be sufficient; but, it seems to be
undesirable to depend fetch(3) unconditionally for all programs that
uses openldap).

Cheers,
- -- 
Xin LI <delphij@delphij.net>	http://www.delphij.net/
FreeBSD - The Power to Serve!	       Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (FreeBSD)

iQEcBAEBCAAGBQJNkPQ6AAoJEATO+BI/yjfBGi8IAJ/3o2sVhal0i7982PNuCZXW
gI2aH/e7dWDM2NfL8dSKZlmF8vH/Q0aZHHvlVpQ4o0tCYSk4Iouk8BM6MEVS1Upc
3JLmHVR12D0FBblLpetTstcdx2w2390efPrTI+j+YrJn5yz218Ypu53k1d4F4D/L
IbM3t96FwulS/vSara6pb4m1H28FMpEs7+0jqEDdeJxm26cWWe++z48Lg5yUcnwW
uh2aiDpll7ep7vEuWQGw7pfG+IBd3tsTKm1rqXJ4hgZirYI5lXg18tL2W702P0Ez
kyeye7uY7nsWqR0f7nWCBF5GMPidCQ1/fzAz/WwHtoTkbw4vPpDxiNxwox59H7I=
=m6q3
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D90F43B.7050606>