Re: [Opensync-devel] Patch for evolution plugin

[Nicolas <pr...@fr...>]

Le samedi 02 juillet 2011 à 19:03 +0100, Ian Martin a écrit :
> Hi,
> 
> On 2 July 2011 16:42, Nicolas <pr...@fr...> wrote:
> > Le samedi 02 juillet 2011 à 12:27 +0200, Daniel Gollub a écrit :
> >> Hi Nicolas,
> >>
> >> On Saturday, July 02, 2011 08:06:40 am Nicolas wrote:
> >> > With this patch, it works with new Evolution release 2.32 and higher.
> >>
> >> Could you explain which change was exactly required to get it working again for 2.32? It's hard
> >> for me to distinguish the diff between the new feature and the required change to make it work.
> >
> > It's an old patch ; that I have forgotten to send you.
> >
> > It's the API that is different with 2.32 :
> 
> The current code seems to work fine for me with 2.32
> 
> > With this modification, opensync can find the good address book ;
> > otherwise it finds nothing.
> >
> >
> >> > Moreover, I have added an option to be able to choose the evolution
> >> > addressbook, calendar, tasks or memo  to sync.
> >> [...]
> 
> I don't think this patch does anything new. The plugin has been able
> to choose addressbook/calendar by name or uri for a while.
> 
> The <url></url> field can be one of 3 options
> 1) "default" is a special value that opens the default
> addressbook/calendar, etc (you can set an item as the default using
> evolution)
> 2) A uri such as "local:system" or google://example@gmail.com
> 3) The name of the addressbook/calendar, etc
> 
> This is why the uri is also compared to the name in the second strcmp
> in evo2_find_source:
>  if (!strcmp(e_source_peek_name(source), uri))
> 
> Using this method has it's problems if you name an entry "default" or
> "local:system", so perhaps the <url> field should be an option of:
> <default />
> <url></url>
> <name></name>
> to avoid mismatches but the current method seems simple to use.
> 
> There are some short bad docs on the wiki at
> http://www.opensync.org/wiki/trunk/syncing/evolution
> 
> Hope that makes sense,
> 
> Ian

I have just updated my distribution (debian sid), and now I have the
same issue for calendar :

(process:13301): libecal-WARNING **: Cannot get cal from factory:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.evolution.dataserver.Calendar0 was not provided by
any .service files
event sink of member 1 of type evo2-sync had an error: Failed to create
new calendar

(process:13301): libecal-WARNING **: Cannot get cal from factory:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.evolution.dataserver.Calendar0 was not provided by
any .service files
todo sink of member 1 of type evo2-sync had an error: Failed to create
new calendar

(process:13301): libebook-WARNING **: e-book.c:3255: cannot get book
from factory: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The
name org.gnome.evolution.dataserver.AddressBook0 was not provided by
any .service files
contact sink of member 1 of type evo2-sync had an error: Failed to alloc
new addressbook: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
The name org.gnome.evolution.dataserver.AddressBook0 was not provided by
any .service files

(process:13301): libecal-WARNING **: Cannot get cal from factory:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.evolution.dataserver.Calendar0 was not provided by
any .service files
note sink of member 1 of type evo2-sync had an error: Failed to create
new calendar


Error Summary:
NEXT ERROR: "No objtypes left without error. Aborting"
NEXT ERROR: "At least one sink_engine failed while connecting"
NEXT ERROR: "At least one sink_engine failed while connecting"
NEXT ERROR: "At least one sink_engine failed while connecting"
NEXT ERROR: "At least one sink_engine failed while connecting"
ROOT CAUSE: "Failed to create new calendar"


Regards,

Nicolas