From owner-freebsd-current@FreeBSD.ORG Thu Jun 17 18:20:29 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9A14106567C for ; Thu, 17 Jun 2010 18:20:29 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 68DFA8FC2C for ; Thu, 17 Jun 2010 18:20:29 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id o5HIKPim025545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 17 Jun 2010 11:20:26 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id E3C941CC38; Thu, 17 Jun 2010 11:20:24 -0700 (PDT) To: eculp In-reply-to: Your message of "Thu, 17 Jun 2010 13:00:42 CDT." <20100617130042.128751koi3cptack@econet.encontacto.net> Date: Thu, 17 Jun 2010 11:20:24 -0700 From: "Kevin Oberman" Message-Id: <20100617182024.E3C941CC38@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-06-17_03:2010-02-06, 2010-06-17, 2010-06-17 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-1005130000 definitions=main-1006170100 Cc: current Subject: Re: Having a problem with security/libassuan-1 when compiling gnupg. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 18:20:29 -0000 > Date: Thu, 17 Jun 2010 13:00:42 -0500 > From: eculp > > Quoting Kevin Oberman : > > >> Date: Thu, 17 Jun 2010 12:03:48 -0500 > >> From: eculp > >> Sender: owner-freebsd-current@freebsd.org > >> > >> Having a problem with security/libassuan-1 when compiling gnupg. I > >> did the upgrade to libassuan-2.0.0 following the instructions in > >> UPDATING and this is the first problem that I have seen. > >> > >> ===> gnupg-2.0.14_3 depends on package: libassuan-1>=1.0.5 - not found > >> ===> Verifying install for libassuan-1>=1.0.5 in > >> /usr/ports/security/libassua > >> n-1 > >> > >> ===> libassuan-1-1.0.5 conflicts with installed package(s): > >> libassuan-2.0.0 > >> > >> They install files into the same place. > >> Please remove them first with pkg_delete(1). > >> *** Error code 1 > >> > >> Stop in /usr/ports/security/libassuan-1. > >> *** Error code 1 > >> > >> Stop in /usr/ports/security/gnupg. > >> > >> ===>>> make failed for security/gnupg > >> ===>>> Aborting update > >> > >> Any suggestions will be appreciated. > > > > Sorry. Just re-read the message. > > > > Since you already have libassuan-2.0.0 installed, you will probably need > > to: > > pkg_delete -f libassuan-2.0.0 > > portinstall libassuan-1 > > or > > portmaster security/libassuan-1 > > > Thanks a lot, Kevin. It is now working fin as far as I can tell. I > was confused as to which was the prefered version for Current and was > sure that I had seen somewhere that is was 2.x but was probably > confused with another port. 2.0.0 should be the preferred version, but its API is incompatible with the old one. Many ports using libassuan (listed in UPDATING) have not been updated to support V2, so the libassuan-1 port was created. As soon as deskutils/kdepim4 and security/{dirmngr|gnupg|gpa|opensc} are updated, there will be a need to move to 2.0.0. I am unsure what happens when some ports want v1 and others want v2. This may not be an issue if the updated ports can be deal with either API, but I have no idea whether that is the case. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751