Hi! evolution-exchange-2.12.1 is released with Gnome 2.20.1
2 things : 1) we _know_ that upstream releases new packages. In fact, there are mailing lists and an RSS feed for following just that. So _please_ no more 0-day bump requests. 2) since you're so keen to see those packages in portage, please try them on your own. Put the current ebuild in an overlay and bump it there. Just a quick note telling us "it builds and it works on $(arch)" is much more helpful. thanks
All right ... ebuld renaming for x86 and amd64 works fine here. can compile an use it.
Ebuild renaming works fine here, too. I also added a patch to the ebuild to fix a nasty bug where filters are not applied to Exchange incoming mail (see http://bugzilla.gnome.org/show_bug.cgi?id=444503).
Created attachment 136756 [details, diff] evolution-exchange-2.12.1-fix-filter.patch
Created attachment 136757 [details] evolution-exchange-2.12.1.ebuild The ebuild used with patch applied.
The bump doesn't basically contain anything else than translation updates, so I haven't rushed with this. Now I have a bump ready in local tree, but considering including this filtering patch with it. However without further information on the upstream bug I can not do this, because the upstream bug says that this patch is introducing race conditions or other problems, making it potentially crash a few times per day. Do you have any information on that? You posted the patches after this issue was raised in the upstream bug, afterall
I actually made this ebuild before this issue was raised - and didn't recheck the upstream bug before posting here :-( I have evolution-exchange running with this patch since almost one week now (non-stop) and it didn't crash so far. I think, however, we should wait until this issue is clarified by upstream.
It seems the fix for that filter stuff triggered a few other bugs that weren't hit before, based on that upstream bug. Meanwhile evolution-exchange-2.12.2 is in the tree now. Markus, feel free to open a new bug about the autofiltering problems. The initial issue of this bug is fixed, so marking as such now.
