cvs commit: ports/deskutils/basket Makefile ports/security/gnutls Makefile ports/security/dirmngr Makefile ports/security/libotr Makefile ports/security/libgcrypt Makefile ports/security/gnupg Makefile ports/security/gpgme Makefile ports/security/libksba ...

[Jeremy Messenger]

On Fri, 09 Mar 2007 15:41:45 -0600, Jean-Yves Lefort  
<jylefort at FreeBSD.org> wrote:

> On Fri, 09 Mar 2007 15:13:27 -0600
> "Jeremy Messenger" <mezz7 at cox.net> wrote:
>
>> On Fri, 09 Mar 2007 14:50:35 -0600, Jean-Yves Lefort
>> <jylefort at FreeBSD.org> wrote:
>>
>> > On Fri, 09 Mar 2007 13:29:20 -0600
>> > "Jeremy Messenger" <mezz7 at cox.net> wrote:
>> >
>> >> On Fri, 09 Mar 2007 12:31:11 -0600, Kent Stewart <kstewart at owt.com>
>> >> wrote:
>> >>
>> >> > On Thursday 08 March 2007 06:12, Jean-Yves Lefort wrote:
>> >> >> jylefort    2007-03-08 14:12:08 UTC
>> >> >>
>> >> >>   FreeBSD ports repository
>> >> >>
>> >> >>   Modified files:
>> >> >>     deskutils/basket     Makefile
>> >> >>     security/gnutls      Makefile
>> >> >>     security/dirmngr     Makefile
>> >> >>     security/libotr      Makefile
>> >> >>     security/libgcrypt   Makefile
>> >> >>     security/gnupg       Makefile
>> >> >>     security/gpgme       Makefile
>> >> >>     security/libksba     Makefile
>> >> >>     security/gnutls-devel Makefile
>> >> >>   Log:
>> >> >>   Track libgpg-error shlib version change.
>> >> >
>> >> > There were more than this. For example, kde's kmail no longer runs
>> >> > because it is looking for libgpg-error.so.3. If I look at the ports
>> >> > that use this library there must be 20-30 on my computer.
>> >>
>> >> In the past, I have requested to add in UPDATING so it will be need  
>> to
>> >> do
>> >> that again too.
>> >>
>> >> http://freebsd.rambler.ru/bsdmail/cvs-all_2006/msg37160.html
>> >>
>> >> portupgrade -rf libgpg-error-\*
>> >
>> > Ok I know what's going on. You need the -f because of the issue
>> > described in ports/104877. Otherwise a mere "portupgrade -a" or
>> > "portupgrade -r libgpg-error" would catch the revision bumps and
>> > rebuild the appropriate ports.
>>
>> The 'portupgrade -a or -r' will not catch it.
>
> I did not say "will", I said "would" (if 104877 was fixed).
>
>> The libsoup, evolution, buoh, and etc still need to be bump. These
>> ports don't have any of libgpg-error dependency in the Makefile.
>
> These indirect clients should not link against libgpg-error. They only
> do so because of a bug in libtool.
>
>> # ldd /usr/local/lib/libsoup-2.2.so.8 | grep libgpg-error
>>          libgpg-error.so.0 => /usr/local/lib/libgpg-error.so.0  
>> (0x28541000)
>> # ldd /usr/local/bin/buoh | grep libgpg-error
>>          libgpg-error.so.0 => /usr/local/lib/libgpg-error.so.0  
>> (0x28176000)
>> # ldd /usr/local/lib/evolution/2.10/components/libevolution-calendar.so  
>> |
>> grep libgpg-error
>>          libgpg-error.so.0 => /usr/local/lib/libgpg-error.so.0  
>> (0x297c3000)
>> [...goes on...]
>>
>> I sloved this problem by 'portmaster -r libgpg-error-\*'. So... Add
>> 'portupgrade -rf libgpg-error-\*' and 'portmaster -r libgpg-error-\*' in
>> UPDATING will taking care of it.
>
> I'd rather have 104877 fixed. Rebuilding most of your ports because a
> small library down the tree was updated is not acceptable.

The 104877 fix is not in ports tree right now, so I think we still need to  
put an entry in UPDATING for our users' sake.

Cheers,
Mezz

> --
> Jean-Yves Lefort
>
> jylefort at FreeBSD.org
> http://lefort.be.eu.org/


-- 
mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team  -  FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org
http://wiki.freebsd.org/multimedia  -  multimedia at FreeBSD.org