Date: Mon, 28 Mar 2011 13:57:35 -0700 From: Doug Barton <dougb@FreeBSD.org> To: d@delphij.net Cc: ports@FreeBSD.ORG, delphij@FreeBSD.ORG, umq@ueo.co.jp, Xin LI <delphij@delphij.net>, Kevin Oberman <oberman@es.net> Subject: Re: Unable to configure dirmngr after openldap upgrade Message-ID: <4D90F63F.7000901@FreeBSD.org> In-Reply-To: <4D90F43B.7050606@delphij.net> References: <20110328194251.9F2FE1CC0C@ptavv.es.net> <4D90F43B.7050606@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/28/2011 13:48, Xin LI wrote: > 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). I know next to nothing about how the openldap-client stuff works, so I'm sorry if these questions are silly. :) The biggest question is, does dirmngr compile after your change? The other question is that the only reason I have openldap installed at all is so that gnupg can use it to fetch keys from ldap keyservers. Will this still work when the FETCH option is no longer present? Thanks, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D90F63F.7000901>