Evoluton 2.2.1 unarched but matching Ximian Connector (2.2.3) still is in ~x86. Evolution 2.2.1 will NOT work with Ximian Connector 2.0.x. Performing a system wide update will cause Evolution to be updated and Exchange support to brake. Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge -uv world 3. Access Exchange account in Evolution Actual Results: Unable to access Exchange account in Evolution. Received numerious errors about exchange backend crashing. Expected Results: Ximian Connector 2.2.3 should be updated same time as Evolution. I've been running an overlay with Ximian Connector 2.2.3 for some time now and and also been running the version in portage for 2 days without issue. Found no bugs in bugzilla for version 2.2.3.
thats all nice, but it is untested... and i can't test it.. so it'll just have to wait.
Just for all those people searching out there. The bug appeared to me as: "checking Evolution version... configure: error: Evolution development libraries not installed" when I tried re-emerging ximian-connector after my new Evolution had no Exchange connectivity. This is because the EVOLUTION_API_VERSION is coded in the ximian-connector ebuild as "2.0" so the pkg-config looks for evolution-shell-2.0 and can't find it because Evolution has been upgraded to 2.3. Only fix is to push 2.2.3 out to x86, until then all --update worlds will break Evolution <-> Exchange while Evolution is 2.2.x and ximian-connector is still 2.0.x.
Sorry, where I said "only fix" I meant that addressed to the maintainers. For users finding this, as Dave says add mail-client/ximian-connector to your /etc/portage/package.keywords file (or selectively mask all the Evolution stuff to prevent it from moving from 2.0 to 2.2 - blergh!)
no the 'right' fix would be to fix the older connector deps (which i admittedly forgot). The only thing i need here is some feedback on how the plugin performs to mark it stable, we can't test it.
(In reply to comment #4) > no the 'right' fix would be to fix the older connector deps (which i admittedly > forgot). > > The only thing i need here is some feedback on how the plugin performs to mark > it stable, we can't test it. > > This partciular ebuild builds/works for me at the office and on my mobile laptop without issue. Running it for 8 days.
tested by myself and a few others, its marked stable now.
Ok. Does this bug have to be reopened with every evolution update? At least, I hope there's a new ximian connector. Using webmail at work, for now.
the new package is called evolution-exchange.
*** Bug 120185 has been marked as a duplicate of this bug. ***
Doh. I should've picked up on that from the Debian rename :) Guess it is due to the purchasing of Ximian by Novell. Thanks.
