From owner-freebsd-ports@FreeBSD.ORG  Sun Jul  6 19:27:25 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 776F4195;
 Sun,  6 Jul 2014 19:27:25 +0000 (UTC)
Received: from f10.opsec.eu (f10.opsec.eu [IPv6:2001:14f8:200:4::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2CC4A2D80;
 Sun,  6 Jul 2014 19:27:25 +0000 (UTC)
Received: from pi by f10.opsec.eu with local (Exim 4.82_1-5b7a7c0-XX (FreeBSD))
 (envelope-from <pi@FreeBSD.org>)
 id 1X3s5o-000GDY-1V; Sun, 06 Jul 2014 21:27:20 +0200
Date: Sun, 6 Jul 2014 21:27:20 +0200
From: Kurt Jaeger <pi@FreeBSD.org>
To: Tijl Coosemans <tijl@FreeBSD.org>
Subject: Re: upgrade to security/libgcrypt, shared lib bump, what needs to be
 done ?
Message-ID: <20140706192720.GD73593@f10.opsec.eu>
References: <20140706111643.GB73593@f10.opsec.eu>
 <20140706145604.0483ae7f@kalimero.tijl.coosemans.org>
 <20140706174859.GC73593@f10.opsec.eu>
 <20140706205203.4176600e@kalimero.tijl.coosemans.org>
 <20140706205623.2288c2d5@kalimero.tijl.coosemans.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140706205623.2288c2d5@kalimero.tijl.coosemans.org>
Cc: ports@freebsd.org, Kurt Jaeger <pi@FreeBSD.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jul 2014 19:27:25 -0000

Hi!

> On Sun, 6 Jul 2014 20:52:03 +0200 Tijl Coosemans wrote:
> > On Sun, 6 Jul 2014 19:48:59 +0200 Kurt Jaeger wrote:
> >> I prepared a new diff, see
> >> 
> >> http://people.freebsd.org/~pi/misc/libgcrypt.svndiff-v2
> >> 
> >> Can you have a look at it, before I mess up the whole tree 8-} ?
> > 
> > net/samba4/Makefile: PORTREVISION messed up 
> > net/samba41/Makefile: PORTREVISION messed up

Ah, thanks, fixed.

> > security/libgcrypt/Makefile: Keep post-patch silent maybe?

If possible, I would like to keep those post-patch changes in the open.

> > Looks good otherwise, so go ahead and commit
> 
> There's no major incompatibility with the old version of libgcrypt right?

In the 1.6.0 release notes at

http://lists.gnupg.org/pipermail/gcrypt-devel/2013-December/002775.html

there is a list of changed APIs. Some of them are removed.
Which might cause issues.

> Have you tried to compile some of the ports that depend on libgcrypt
> to see if nothing breaks?

No, due to number of ports involved (104), list at

http://people.freebsd.org/~pi/misc/libgcrypt-related-ports

For this we probably need some exp-run ?

If one considers this a security-related change, and probably needs
testing on functionality as well, I think that "commit and fix those few
that break" looks like a possible short-cut 8-}

-- 
pi@FreeBSD.org         +49 171 3101372                          6 years to go !