--- Gregor Hlawacek <gregor hlawacek gmx at> wrote: > On Fri, 2007-09-14 at 13:07 +0100, Matt Davey wrote: > > > > Looks like an instance of: > > > > http://bugzilla.gnome.org/show_bug.cgi?id=429423 > > > > > > > > which should be fixed by the recent commit for bug 201167: > > > > http://bugzilla.gnome.org/show_bug.cgi?id=201167 > > > > > > I tried to apply the patches to evolution 2.10.2 but failed for the > > > first one the second worked. I am not sure I don't completly understand > > > the corresponding messages if I have to also apply the first patch > > > (evo.patch). It is complaining about a large number of missing files. > > > > > > However, category syncing no works. Still nothing is synced from the > > > calendar to the pilot. The error stays the same > > > > Nathan and Tom are probably the authorities on this one. If possible, > > I'd suggest trying the recently released Evolution 2.11.92. I don't > > know whether all required patches were attached to bug 201167. > > I am close to trying this. However, I am currently finishing my PhD > Thesis and need a production ready system, I can live with occasional > crashes but data loss wouldn't be nice. > Can you comment on the stability? Matt's response seems correct, or at least it's worth a try. The 2 patches in that bug won't work for Evolution 2.10.2 (or anything before somewhere in Evolution 2.11). There are two possibilities: 1) Build evolution from svn - might or might not be difficult. If you're building Evolution already, it's probably not that bad, but Evolution 2.11.x requires new GTK and Gnome packages. If you don't have those, it will make it harder to do this. You'll also have to upgrade gtkhtml, libsoup, evolution-data-server, and any other evolution-related package (e.g. evolution-exchange or other add-ons). 2) Use a backport the patch to 2.10. I've attached one. While it seems to build for me, I won't say it will build for everyone or that it works - I suggest backing up your data before trying it (the backup conduit should work well for this - though you can always use pilot-xfer to guarantee it). The way I did the patch was to use diff to find the changes from evolution 2.10.2 to SVN HEAD in the conduits directory. I then applied the backport patch to evolution 2.10.2, modified configure.in (one other file that changed), and ran autoconf to regenerate `configure'. When I ran "make", it ran a few more steps than normal - this is OK, as it was running automake, autoconf, and their companion programs. The final (attached) patch should apply directly to evolution 2.10.2 and require no modifications beyond the application of the patch. Run `configure' again, and then make. When running make, the extra steps described above will be run. If you go the route of #2, please let the list know how the patch worked. If it does work as expected, then I'll post it to the bug so it can be applied as a backport for anyone who needs it. The reason creating a backport *should* be this easy is because the conduits are really separated from Evolution. The Evolution Calendar API doesn't change very often, so the conduits don't have to change the calls/structures that are used to access the Calendar API. Thanks, Nathan ____________________________________________________________________________________ Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting
Attachment:
backport_bug201167.patch.gz
Description: 1998645724-backport_bug201167.patch.gz