Gnucash fails to install: configure dbus-glib failure

[Bjorn Berg]

Yep I tried the "sudo port upgrade outdated" and after 3 hours of minor 
upgrades things fell apart, especially with gnome and lib... packages. 
The install would hang on > configuring dbus-lib... and give me an 
error. After it called dbus for the fourth time I shut it down.

Curiously when I rebooted my terminal prompt was preceded by "-bash: no 
job control in this shell". Oh well, if its fritzed we'll go back to 
Windows.

But I'm not giving up yet. I like the suggestion of "sudo port -f 
uninstall dbus"
So if the thing isn't totally fritzed I'm going to do that and if it 
works, I'll try uninstalling dbus-lib, too. Then I'll try installing 
them "sudo port install dbus", followed by another round of "sudo port 
upgrade outdated" for all those ports that failed to upgrade because of 
the out-of-date version of dbus.

Let's see, should be done by Friday I would think!!!

Bj

Randall Wood wrote:
>
> On 22 Apr 2007, at 18:11, Ryan Schmidt wrote:
>
>> On Apr 22, 2007, at 12:41, Randall Wood wrote:
>>
>>> On 22 Apr 2007, at 12:13, Bjorn Berg wrote:
>>>
>>>> So I'm new at this. Can I just type 'port uninstall dbus' on a 
>>>> command line? How do I find those programs that are affected by the 
>>>> newinstall, just run everything? Shouldn't this be a consideration 
>>>> in the release of a new version that looks like its capable of so 
>>>> much havoc?
>>>
>>> A simple "sudo port selfupdate ; sudo port outdated" should take 
>>> care of uninstalling and reinstalling most outdated versions of 
>>> software that depended on the older version of dbus.
>>
>> a) No, it won't: "sudo port outdated" will only show a list of ports 
>> that are outdated; it will not update them.
>
> Sorry. That should read "sudo port upgrade outdated"
>
>
>> b) That wasn't the question. The question was, once dbus has been 
>> upgraded, if it is an ABI-incompatible upgrade, how does one identify 
>> all ports that depend on dbus (whether or not they are outdated) so 
>> that they can be rebuilt? The answer is the the depsearch script in 
>> the wiki:
>>
>> http://trac.macosforge.org/projects/macports/wiki/ProblemHotlist#a2.Aportfailedtobuildupgradeorrunwithamessagereferringtolibintl.3.dylib 
>>
>>
>> Bjorn: sorry, MacPorts isn't smart enough to do this on its own. The 
>> port system does not track whether an upgrade is ABI-compatible or 
>> not. It just knows whether there is an upgrade to a port. It's up to 
>> you to confirm that everything still works after upgrading a port, 
>> and rebuild any dependencies as needed. The depsearch script above 
>> can help you identify what you need to do.
>>
>> You will, by the way, need "sudo port -f uninstall dbus", since 
>> otherwise MacPorts will complain that some other port depends on 
>> dbus. This may also be a way to determine which ports you need to 
>> rebuild, though I do not know if this will be the same list returned 
>> by depsearch.
>>
>
>
>
> Randall Wood
> rhwood at mac.com
> http://shyramblings.blogspot.com
>
> "The rules are simple: The ball is round. The game lasts 90 minutes. 
> All the
> rest is just philosophy."
>
>
>