Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Jul 2014 13:16:43 +0200
From:      Kurt Jaeger <pi@FreeBSD.org>
To:        tijl@FreeBSD.org
Cc:        ports@freebsd.org, portmgr@FreeBSD.org
Subject:   upgrade to security/libgcrypt, shared lib bump, what needs to be done ?
Message-ID:  <20140706111643.GB73593@f10.opsec.eu>

next in thread | raw e-mail | index | archive | help
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

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



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