|
From: Jason G. <exp...@lo...> - 2009-06-16 05:20:53
|
Hello,
Just a repost after getting no responses to my queries of the 4th.
Hoping that re-phrasing might help.
I suspect that opensync (head) should allow me to sync memos and todos
over file <--> obex, but I am getting errors. I am trying to establish:
(1) whether I have misconfigured the plugins
(2) whether this functionality is supported on head
If my config is OK and the functionality should be supported, I will do
some troubleshooting & raise bug reports.
When I sync memos, I get the "ERROR: Unable to find conversion path".
When I sync todos, I get "Schemas validity error".
Relevant config and output below sections below.
Thanks for any tips.
Jason.
---------------------------------------------------
This section shows how I have configured sync of todos.
[3] shows the error messages that I get.
---------------------------------------------------
-----------------------
[1] Extract from obex config
-----------------------
<Resources>
<Resource>
<Enabled>1</Enabled>
<Formats>
<Format>
<Name>vtodo10</Name>
</Format>
</Formats>
<Name>Tasks</Name>
<ObjType>todo</ObjType>
</Resource>
</Resources>
-----------------------
[2] Extract from file config
-----------------------
<Resources>
<Resource>
<Enabled>1</Enabled>
<Formats>
<Format>
<Name>file</Name>
</Format>
</Formats>
<ObjType>todo</ObjType>
<Path>/home/jas/opensync-head/data/obex-file-todo</Path>
</Resource>
</Resources>
-----------------------
[3] Error message when syncing
-----------------------
[jas@talby opensync-head]$ ot --sync obex-file-todo
Synchronizing group "obex-file-todo"
The previous synchronization was unclean. Slow-syncing
todo sink of member 2 of type file-sync just connected
Main sink of member 2 of type file-sync just connected
Main sink of member 1 of type syncml-obex-client just connected
todo sink of member 1 of type syncml-obex-client just connected
All clients connected or error
Main sink of member 1 of type syncml-obex-client just sent all changes
todo sink of member 2 of type file-sync just sent all changes
Main sink of member 2 of type file-sync just sent all changes
** Message: The proprietary text/x-vcard property X-NICKNAME is not
supported.
** Message: The proprietary text/x-vcard property X-SIP is not
supported.
** Message: The proprietary text/x-vcard property X-WV-ID is not
supported.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element AlarmAudio: Schemas validity error : Element 'AlarmAudio': This
element is not expected. Expected is one of ( Alarm, Attach, Attendee,
CalendarScale, Categories, Class, Comment, Completed, Contact,
Created ).
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element DateEnd: Schemas validity error : Element 'DateEnd': This
element is not expected. Expected is one of ( Alarm, Attach, Attendee,
CalendarScale, Categories, Class, Comment, Completed, Contact,
Created ).
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element Content: Schemas validity error : Element 'Content': [facet
'enumeration'] The value 'NEEDS ACTION' is not an element of the set
{'NEEDS-ACTION', 'COMPLETED', 'IN-PROCESS', 'CANCELLED'}.
element Content: Schemas validity error : Element 'Content': 'NEEDS
ACTION' is not a valid value of the atomic type 'TodoStatusValue'.
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
element AlarmAudio: Schemas validity error : Element 'AlarmAudio': This
element is not expected. Expected is one of ( Alarm, Attach, Attendee,
CalendarScale, Categories, Class, Comment, Completed, Contact,
Created ).
Main sink of member 1 of type syncml-obex-client had an error: XMLFormat
validation failed.
todo sink of member 1 of type syncml-obex-client just sent all changes
All clients sent changes or error
All changes got mapped
All conflicts have been reported
All changes got multiplied
All changes got prepared for write
Synchronization Forecast Summary:
ObjType: todo
Member 2: Adding(0) Modifying(0) Deleting(0)
Member 1: Adding(0) Modifying(0) Deleting(0)
No modifications of any Member. Continuing.
todo sink of member 2 of type file-sync committed all changes.
Main sink of member 2 of type file-sync committed all changes.
Main sink of member 1 of type syncml-obex-client committed all changes.
todo sink of member 1 of type syncml-obex-client committed all changes.
All clients have written
todo sink of member 1 of type syncml-obex-client reported sync done.
Main sink of member 1 of type syncml-obex-client reported sync done.
todo sink of member 2 of type file-sync reported sync done.
Main sink of member 2 of type file-sync reported sync done.
All clients reported sync done
todo sink of member 2 of type file-sync just disconnected
Main sink of member 2 of type file-sync just disconnected
todo sink of member 1 of type syncml-obex-client just disconnected
Main sink of member 1 of type syncml-obex-client just disconnected
All clients have disconnected
ERROR: XMLFormat validation failed.
---------------------------------------------------
This section shows how I have configured memo syncing.
[6] shows the error messages that I get.
---------------------------------------------------
-----------------------
[4] Extract from obex config
-----------------------
<Resources>
<Resource>
<Enabled>1</Enabled>
<Formats>
<Format>
<Name>memo</Name>
</Format>
</Formats>
<Name>Notes</Name>
<ObjType>note</ObjType>
</Resource>
</Resources>
-----------------------
[5] Extract from file config
-----------------------
<Resources>
<Resource>
<Enabled>1</Enabled>
<Formats>
<Format>
<Name>file</Name>
</Format>
</Formats>
<ObjType>note</ObjType>
<Path>/home/jas/opensync-head/data/obex-file-memo</Path>
</Resource>
</Resources>
-----------------------
[6] Error message when syncing
-----------------------
[jas@talby opensync-head]$ /home/jas/opensync-head/install/bin/osynctool
--configdir /home/jas/opensync-head/config --sync obex-file-memo
Synchronizing group "obex-file-memo"
note sink of member 2 of type file-sync just connected
Main sink of member 2 of type file-sync just connected
Main sink of member 1 of type syncml-obex-client just connected
note sink of member 1 of type syncml-obex-client just connected
All clients connected or error
Main sink of member 1 of type syncml-obex-client just sent all changes
note sink of member 2 of type file-sync just sent all changes
Main sink of member 2 of type file-sync just sent all changes
** Message: The proprietary text/x-vcard property X-NICKNAME is not
supported.
** Message: The proprietary text/x-vcard property X-SIP is not
supported.
** Message: The proprietary text/x-vcard property X-WV-ID is not
supported.
Main sink of member 1 of type syncml-obex-client had an error: Unable to
find conversion path
Main sink of member 1 of type syncml-obex-client had an error: Unable to
find conversion path
Main sink of member 1 of type syncml-obex-client had an error: Unable to
find conversion path
Main sink of member 1 of type syncml-obex-client had an error: Unable to
find conversion path
Main sink of member 1 of type syncml-obex-client had an error: Unable to
find conversion path
Main sink of member 1 of type syncml-obex-client had an error: Unable to
find conversion path
Main sink of member 1 of type syncml-obex-client had an error: Unable to
find conversion path
Main sink of member 1 of type syncml-obex-client had an error: Unable to
find conversion path
note sink of member 1 of type syncml-obex-client just sent all changes
All clients sent changes or error
All changes got mapped
All conflicts have been reported
All changes got multiplied
All changes got prepared for write
Synchronization Forecast Summary:
ObjType: note
Member 2: Adding(0) Modifying(0) Deleting(0)
Member 1: Adding(0) Modifying(0) Deleting(0)
No modifications of any Member. Continuing.
note sink of member 2 of type file-sync committed all changes.
Main sink of member 2 of type file-sync committed all changes.
Main sink of member 1 of type syncml-obex-client committed all changes.
note sink of member 1 of type syncml-obex-client committed all changes.
All clients have written
note sink of member 1 of type syncml-obex-client reported sync done.
Main sink of member 1 of type syncml-obex-client reported sync done.
note sink of member 2 of type file-sync reported sync done.
Main sink of member 2 of type file-sync reported sync done.
All clients reported sync done
note sink of member 2 of type file-sync just disconnected
Main sink of member 2 of type file-sync just disconnected
note sink of member 1 of type syncml-obex-client just disconnected
Main sink of member 1 of type syncml-obex-client just disconnected
All clients have disconnected
ERROR: Unable to find conversion path
|