Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 138104 - Request to bump to evolution 2.6.2
Summary: Request to bump to evolution 2.6.2
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-26 13:35 UTC by Aaron Stone
Modified: 2006-06-29 09:29 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Stone 2006-06-26 13:35:56 UTC 
Hi folks,

I'd appreciate a version bump on the evolution ebuild to evolution 2.6.2. It is significantly more stable than 2.6.1, and with a bit of positive feedback, might be ready to replace 2.4.x as the non ~ version.

Thanks!
Comment 1 Kayne K 2006-06-27 12:51:09 UTC 
Ditto.. having issues with exchange client 2.6.1 pulling calendar events. :( Maybe a bump would fix it...
Comment 2 Kayne K 2006-06-27 13:03:33 UTC 
(evolution-2.6:14924): libecal-WARNING **: e-cal.c:288: Unexpected response

This is what I've noticed....  Couldnt find anything else around about this...
Comment 3 Gilles Dartiguelongue (RETIRED) gentoo-dev 2006-06-28 19:52:43 UTC 
I have problem emerging evolution-2.6.2 with --as-needed, it fails while building contact book
Comment 4 Daniel Gryniewicz (RETIRED) gentoo-dev 2006-06-29 08:28:55 UTC 
2.6.2 is in the tree.

Please open a separate --as-needed bug.
Comment 5 Kayne K 2006-06-29 09:29:08 UTC 
    Personally,  I've come to assume that my Unexpected Response is now a problem with our Public Folders having a calendar called "Calendar" and my private Exchange calendar conflicting.  Unfortunately, I cannot confirm this as I do not have access to change the exchange server.  

    If so, It would seem that this is an upstream issue.  2.6.2 didnt seem to correct this. :(