Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 143889

Summary: gnome-extra/evolution-echange-2.6.2-r1 crashes on startup scanning of exchange folders
Product: Gentoo Linux Reporter: AJ Armstrong <aja>
Component: New packagesAssignee: GNOME Office (OBSOLETE) <gnome-office+disabled>
Status: RESOLVED FIXED    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374604
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: evolution-exchange/evolution-exchange-2.6.2-r3.ebuild
Patch to bump evolution-exchange to 2.6.2-r3
Patch to bump evolution-exchange to 2.6.2-r3

Description AJ Armstrong 2006-08-14 08:11:08 UTC
I was experiencing the same issue described in the debian bug #374604: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374604

As described there, this is resolveable by bumping the version of evolution-exchange to 2.6.3-r3.  I did so with an ebuild that applies the pertinent patch from debian (available at http://packages.debian.org/unstable/gnome/evolution-exchange)

I will attach the rough ebuild and patch to this bug report.  I assume a more elegant version bump is also possible, but this was a quick and dirty check to see if the problem went away.

Applying the patch from debian resolved the issue.
Comment 1 AJ Armstrong 2006-08-14 08:12:33 UTC
Created attachment 94238 [details]
evolution-exchange/evolution-exchange-2.6.2-r3.ebuild
Comment 2 AJ Armstrong 2006-08-14 08:13:15 UTC
Created attachment 94239 [details, diff]
Patch to bump evolution-exchange to 2.6.2-r3
Comment 3 AJ Armstrong 2006-08-14 08:14:53 UTC
Created attachment 94240 [details, diff]
Patch to bump evolution-exchange to 2.6.2-r3
Comment 4 Mart Raudsepp gentoo-dev 2007-07-18 22:28:00 UTC
Is this still a problem in the 2.8 or 2.10 series as in portage?
Comment 5 Peter Volkov (RETIRED) gentoo-dev 2007-08-30 15:34:20 UTC
Seems that this patch was incorporated before 2.8. Thus this bug is fixed in the currently stable evolution. Reopen, please, if I'm wrong.