Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Sep 2012 18:00:33 GMT
From:      Understudy <understudy@understudy.net>
To:        gnome@FreeBSD.org
Subject:   Re: ports/171484: finance/gnucash looks for libogg.so.7 should look for libogg.so.8
Message-ID:  <201209191800.q8JI0Xqs060017@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/171484; it has been noted by GNATS.

From: Understudy <understudy@understudy.net>
To: Guido Falsi <madpilot@FreeBSD.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: ports/171484: finance/gnucash looks for libogg.so.7 should look
 for libogg.so.8
Date: Wed, 19 Sep 2012 13:53:06 -0400

 On 09/19/12 11:26, Guido Falsi wrote:
 > As gnucash was telling you here:
 >
 > [bhorne@Shibari:~, 09:29 AM, Sun Sep 09]>gnucash &
 > [1] 9489
 > [bhorne@Shibari:~, 09:31 AM, Sun Sep 09]>Shared object "libogg.so.7" not
 > found, required by "libbonoboui-2.so.0"
 > [1]+ Exit 1 gnucash
 >
 > it is libbonoboui-2.so.0 who is looking for an older version of
 > libogg.so.7.
 >
 > This is happening because libogg was subject to an shlib ABI version
 > bump. All ports on which it depends should be recompiled to avoid this.
 > In your case at least x11-toolkits/libbonoboui should be recompiled, but
 > once that is done the above error from gnucash will identify some more
 > most probably.
 >
 > Other ports too could show this problem.
 >
 > the full solution can be found in the 20120721 entry of the UPDATING
 > file:
 >
 > 20120721:
 >    AFFECTS: users of audio/libogg
 >    AUTHOR: naddy@FreeBSD.org
 >
 >    There is a new version of libogg (1.3.0) and the shared library version
 >    has been bumped (ogg.7 to ogg.8).  All ports that have an identifiable
 >    direct dependency on this library have had their PORTREVISIONs bumped.
 >    However, some ports that pull in the library indirectly may continue to
 >    look for the old version.  To ensure that all are updated, perform this
 >    step:
 >
 >    # portmaster -r libogg
 >    or
 >    # portupgrade -rf libogg
 >
 Hi,
 
 Your were correct. I have implemented.
 
 portmaster -r libogg
 
 
 This has corrected the issue.
 
 Please close this bug report.
 
 Sincerely,
 
 Brendhan
 
 portmaster -r libogg
 



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