Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Jul 2014 14:56:04 +0200
From:      Tijl Coosemans <tijl@FreeBSD.org>
To:        Kurt Jaeger <pi@FreeBSD.org>
Cc:        ports@freebsd.org, portmgr@FreeBSD.org
Subject:   Re: upgrade to security/libgcrypt, shared lib bump, what needs to be done ?
Message-ID:  <20140706145604.0483ae7f@kalimero.tijl.coosemans.org>
In-Reply-To: <20140706111643.GB73593@f10.opsec.eu>
References:  <20140706111643.GB73593@f10.opsec.eu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 6 Jul 2014 13:16:43 +0200 Kurt Jaeger wrote:
> Hello, Tijl,
> 
> Someone prepared a patch to bring security/libgcrypt from 1.5.3 to 1.6.1, see:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191256
> 
> I prepared a diff which builds and tests, see
> 
> http://people.freebsd.org/~pi/misc/libgcrypt.svndiff
> 
> and
> 
> http://people.freebsd.org/~pi/misc/libgcrypt-1.6.1.log
> 
> for the build log.
> 
> It causes a shared lib upgrade, what needs to be done to the dependencies
> (list below) ?
> 
> I've read 
> 
> http://lists.freebsd.org/pipermail/freebsd-ports/2014-May/092082.html
> 
> but I think I'm still missing some of the fine print 8-(
> 
> It needs USES=libtool, but does it *need* libtool:oldver or libtool:keepla ?
> Do I need to bump PORTREVISION on the dependencies ?
> 
> Thanks for any hints!
> 
> security/vpnc
> net/libvncserver
> textproc/libxslt
> security/libgnome-keyring
> multimedia/libaacs
> net/remmina
> net/glib-networking
> devel/gvfs
> devel/libvirt
> security/xmlsec1
> security/libotr3
> multimedia/vlc
> textproc/p5-XML-LibXSLT
> net/wireshark
> editors/libreoffice
> security/gnupg
> devel/libsoup
> net-im/mcabber
> devel/libsoup-gnome
> ftp/filezilla
> sysutils/freeipmi

You can deal with the amd64 versus x86_64 problem by adding this to the
Makefile:

CONFIGURE_TARGET=${ARCH:S/amd64/x86_64/}-portbld-${OPSYS:tl}${OSREL}

:oldver is meant to keep the library version the same in case that's
more convenient.  Because the update already modifies the library version
it makes no sense to use it.  You can add USES=libtool:keepla to the
Makefile, rebuild the port and then check with "make check-plist" what
the effects on pkg-plist are.  It looks like you'll have to add
lib/libgcrypt.so.20.0.1

Then you'll have to bump PORTREVISION on ports that depend on libgcrypt.
There are a lot more than the ones you listed.  You could take the union
of these two lists:

cd /usr/ports
grep -Rl '{PORTSDIR}/security/libgcrypt' *
pkg rquery '%o %B' | grep libgcrypt.so | sort

To actually bump ports you can use one of the scripts in Tools/scripts
like bump-revision.sh.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140706145604.0483ae7f>