From owner-freebsd-ports@FreeBSD.ORG Tue Mar 29 08:18:43 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EBAC1065674; Tue, 29 Mar 2011 08:18:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id AA7D48FC18; Tue, 29 Mar 2011 08:18:42 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p2T8I5ql011636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Mar 2011 11:18:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p2T8I5ch031035; Tue, 29 Mar 2011 11:18:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p2T8I5SA031034; Tue, 29 Mar 2011 11:18:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 29 Mar 2011 11:18:05 +0300 From: Kostik Belousov To: d@delphij.net Message-ID: <20110329081805.GA78089@deviant.kiev.zoral.com.ua> References: <20110328194251.9F2FE1CC0C@ptavv.es.net> <4D90F43B.7050606@delphij.net> <4D90F63F.7000901@FreeBSD.org> <4D90FB97.1020208@delphij.net> <4D9119FB.6090604@FreeBSD.org> <4D911D59.3000403@delphij.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vJllvG0+tm4uff9v" Content-Disposition: inline In-Reply-To: <4D911D59.3000403@delphij.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: ports@freebsd.org, umq@ueo.co.jp, Doug Barton , delphij@freebsd.org, Kevin Oberman Subject: Re: Unable to configure dirmngr after openldap upgrade X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2011 08:18:43 -0000 --vJllvG0+tm4uff9v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 28, 2011 at 04:44:25PM -0700, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 >=20 > On 03/28/11 16:30, Doug Barton wrote: > > On 03/28/2011 14:20, Xin LI wrote: > >> On 03/28/11 13:57, Doug Barton wrote: > >>> 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 ironical= ly > >>>> it seem be a bug but a feature :( > >>>> > >>>> I have decided to disable FETCH support from now on, since it's like= ly > >>>> 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? > >> > >> hmm... how do I test fetching from an ldap keyserver? > >=20 > > I'll save you the trouble. :) I got your latest update and tested both > > scenarios myself, and the answer is that they both work. > >=20 > > So now the question is, should the FETCH OPTION be removed altogether? I > > imagine that a lot of users will be at least as confused as I, and word > > is that PRs for other ports are already showing up. >=20 > I think that's being used in some ldap utilities so it might broke some > applications that makes use of that? >=20 > I'll add a note in UPDATING to document this. I did not verified it, but suspect that libldap.so linking line missed -lfetch. Note, that I mean the libldap.so linking, and not linking of the utilities depended on libldap. --vJllvG0+tm4uff9v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk2Rlb0ACgkQC3+MBN1Mb4jotgCfTKbExVzsbTiYgApXnLqXTVxd gj0AoPYK94Ltb/OAoGkJlKoNG2aXStyy =rjLo -----END PGP SIGNATURE----- --vJllvG0+tm4uff9v--