Date: Fri, 3 May 2013 16:59:12 -0500 From: Jeremy Messenger <mezz.freebsd@gmail.com> To: Tijl Coosemans <tijl@freebsd.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, Emanuel Haupt <ehaupt@freebsd.org>, "ports-committers@freebsd.org" <ports-committers@freebsd.org> Subject: Re: svn commit: r317227 - head Message-ID: <CADLFttdzTsRTiM%2BO9tA89N--Mo8SuPHNeGW-4PvCLwSe1ut5Ow@mail.gmail.com> In-Reply-To: <51842941.2040905@FreeBSD.org> References: <201305031759.r43Hx6vU069291@svn.freebsd.org> <51841656.4060809@FreeBSD.org> <CADLFttfy4RG_ahO0euCSzpjCEy4fzbNZukmSTtNPQBHqjZKwHA@mail.gmail.com> <51842941.2040905@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 3, 2013 at 4:16 PM, Tijl Coosemans <tijl@freebsd.org> wrote: > On 2013-05-03 22:24, Jeremy Messenger wrote: >> On Fri, May 3, 2013 at 2:56 PM, Tijl Coosemans <tijl@freebsd.org> wrote: >>> On 2013-05-03 19:59, Emanuel Haupt wrote: >>>> Author: ehaupt >>>> Date: Fri May 3 17:59:06 2013 >>>> New Revision: 317227 >>>> URL: http://svnweb.freebsd.org/changeset/ports/317227 >>>> >>>> Log: >>>> Add a note about the security/libgcrypt update. >>>> >>>> Modified: >>>> head/UPDATING >>>> >>>> Modified: head/UPDATING >>>> ============================================================================== >>>> --- head/UPDATING Fri May 3 17:42:12 2013 (r317226) >>>> +++ head/UPDATING Fri May 3 17:59:06 2013 (r317227) >>>> @@ -5,6 +5,27 @@ they are unavoidable. >>>> You should get into the habit of checking this file for changes each time >>>> you update your ports collection, before attempting any port upgrades. >>>> >>>> +20130503: >>>> + AFFECTS: users of security/libgcrypt and any port that depends on it >>>> + AUTHOR: ehaupt@FreeBSD.org >>>> + >>>> + The libgcrypt port has been updated to 1.5.2 and all shared libraries >>>> + versions have been bumped. So you need to rebuild all applications that >>>> + depend on libgcrypt. Do something like: >>> >>> This shouldn't have happened. >>> >>> In the configure.ac for version 1.5.0 it says: >>> >>>> # LT Version numbers, remember to change them just *before* a release. >>>> # (Interfaces removed: CURRENT++, AGE=0, REVISION=0) >>>> # (Interfaces added: CURRENT++, AGE++, REVISION=0) >>>> # (No interfaces changed: REVISION++) >>>> LIBGCRYPT_LT_CURRENT=18 >>>> LIBGCRYPT_LT_AGE=7 >>>> LIBGCRYPT_LT_REVISION=0 >>> >>> In 1.5.2 it is: >>> >>>> # LT Version numbers, remember to change them just *before* a release. >>>> # (Interfaces removed: CURRENT++, AGE=0, REVISION=0) >>>> # (Interfaces added: CURRENT++, AGE++, REVISION=0) >>>> # (No interfaces changed: REVISION++) >>>> # NOTE: This is a stable branch, thus you may only bump up REVISION >>>> # unless you coordinate with the development branch. >>>> # >>>> LIBGCRYPT_LT_CURRENT=19 >>>> LIBGCRYPT_LT_AGE=8 >>>> LIBGCRYPT_LT_REVISION=1 >>> >>> The library version should be CURRENT - AGE, i.e. 11 in both cases and >>> therefore no version bump. >> >> Add USE_GNOME=ltverhack will fix this bug. >> >> While I am here, it will be great if someone can move it over to USES >> since it's not specific to GNOME. Something like USES=libtool:verhack >> libtool:asneededhack or different idea. :-) We have three patches for >> libtool: > > Doesn't every port using libtool need this? Yes, but it will be a very huge task to do it. It will forcing a lot of rebuild around. I think we need to do a baby step and baby step by using patch until we get it all then we can push patch to the libtool port and upstream. > And if so is libtool doing something wrong on FreeBSD? http://people.freebsd.org/~mezz/libtool.txt -- mezz.freebsd@gmail.com - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLFttdzTsRTiM%2BO9tA89N--Mo8SuPHNeGW-4PvCLwSe1ut5Ow>