From owner-freebsd-current@FreeBSD.ORG Thu Jun 17 21:56:38 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 6343B106566B for ; Thu, 17 Jun 2010 21:56:38 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 037F88FC0A for ; Thu, 17 Jun 2010 21:56:37 +0000 (UTC) Received: (qmail 8849 invoked by uid 399); 17 Jun 2010 21:56:36 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 17 Jun 2010 21:56:36 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C1A9A13.7030206@FreeBSD.org> Date: Thu, 17 Jun 2010 14:56:35 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Kevin Oberman References: <20100617182024.E3C941CC38@ptavv.es.net> In-Reply-To: <20100617182024.E3C941CC38@ptavv.es.net> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 21:56:38 -0000 [ FYI, this message should have gone to freebsd-ports@FreeBSD.org ... ] On 06/17/10 11:20, Kevin Oberman wrote: > 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. Well, I just made it a lot worse. :) As Kevin points out here, the new version of libassuan is not compatible with the old. This decision on the part of the gnupg folks has its merits, but is unarguably inconvenient during the transition. On May 11th I approached the authors of the ports that depend on libassuan asking about their plans for updating (minus ale@ unfortunately, opensc's dependency is conditional, thus I missed it until I grep'ed the tree instead of relying on INDEX). The status of the affected ports is as follows: 1. gnupg Already handled because 2.0.15 required the update 2. dirmngr They had an RC ready to go, which they released after I poked them a bit. :) So these first 2 are now done. 3. kdepim4 My understanding is that the version currently under development has support for libassuan 2.0.0, and will be released in August. The kde@ folks have indicated that if there is a need to update it sooner they can most likely do that based on patches that are currently available. 4. gpa The svn version supports assuan 2.0.0, but the release of this new version has not yet been scheduled. 5. opensc ale@ has indicated that he would prefer to wait to update his port until a new version that supports assuan 2.0.0 is released. > 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. The current situation is that having both versions installed is incompatible. My preference would be that the maintainers of the affected ports upgrade to depend on assuan 2.0.0 and then we can remove libassuan-1. If it becomes necessary to support having both versions installed then "Plan C" at this point would be to modify libassuan-1 to support this. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/