Evo crashing on FC2 all of a sudden

[Temlakos]

Well, it took me nearly an hour--and thirty-four RPM's--but I did get 
Evo 2.0.2 installed. (Well, one thing I had to do was to install a 
version of "yum" compatible with the "atrpms" repos. But I always like 
to have as many package managers on my system as possible--it makes it 
much easier to administer. Once I did that, I had to wait a lo-o-o-ong 
time to d/l the headers so that yum could resolve the dependencies.

But patience seems to pay.

Well! So when I *do* migrate to Fedora Core 3, I'll have taken a 
*crucial* step--migrating in advance from Evo 1.4.x to 2.0.x. Lots of 
changes!

Temlakos

PS: Thus far, I recommend the Evo upgrade to everyone. Only problem is: 
Who took down the old Summary page with the RSS feeds? I'm gonna miss that!

Temlakos

David Cary Hart wrote:

>On Sat, 2004-11-13 at 15:39 -0500, Dick Roth wrote:
>  
>
>>Woke up in the middle of a snow storm without power to my PC.  All is
>>now normal except that Evo 1.4.6, which was installed as part of the FC2
>>install keeps crashing...often.
>>    
>>
>
>The problem is usually associated with newer releases of bonobo or glibc
>that are no longer compatible. Here are some suggestions:
>
>1. Use yum on the development tree and upgrade to 2.02. This will solve
>all of the dependencies automatically. You can set up a
>separate /etc/devel.conf like:
>
>	[main]
>	cachedir=/var/cache/yum
>	debuglevel=2
>	logfile=/var/log/yum.log
>	pkgpolicy=newest
>	distroverpkg=fedora-release
>	gpgcheck=1
>	tolerant=1
>	exactarch=1
>
>	[freshrpm - devel]
>name=Fedora Linux $releasever - $basearch - fedora - development
>baseurl=http://ayo.freshrpms.net/fedora/linux/development/i386/core
>
>Then do "yum -c /etc/devel.conf update evolution"
>
>2. Upgrade to Fedora 3 which includes 2.02.
>
>3. Roll back your updates of glibc and libonobo.
>
>4. Find another mailer.
>
>
>  
>