opensync-users — The place to get help for the OpenSync project

Re: [Opensync-users] Compilation error in plugins/syncml

[Michael B. <mic...@cm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason Grant wrote:
> 
> I get the compilation error shown below when building the syncml plugin
> off head (against the libsyncml off head).
> 
> I cannot see the definition of SmlBool or SmlError in any of the checked
> out source - hence the error.

You have to checkout branches/libsyncml-0.5.x and not trunk.

Best regards

Michael
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkptyPkACgkQ2L0ZGCAwWqse6ACgqCHMJ+BjsXXQVUIUe0XTuhDc
luYAoKT2bJAMGoYk+4y+R+JiaGkpP0Or
=5jNJ
-----END PGP SIGNATURE-----

[Opensync-users] Compilation error in plugins/syncml

[Jason G. <exp...@lo...>]

Hello,

I get the compilation error shown below when building the syncml plugin
off head (against the libsyncml off head).

I cannot see the definition of SmlBool or SmlError in any of the checked
out source - hence the error.

Thanks for any tips,

J.


-- The C compiler identification is GNU
-- Check for working C compiler: /usr/lib/ccache/gcc
-- Check for working C compiler: /usr/lib/ccache/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- checking for one of the modules 'libopensync;>=0.37'
--   found libopensync, version 0.39-snapshot
-- checking for one of the modules 'glib-2.0'
--   found glib-2.0, version 2.20.1
-- Found GLib2: glib-2.0 /usr/include/glib-2.0;/usr/lib/glib-2.0/include
-- Looking for include files HAVE_GLIB_GREGEX_H
-- Looking for include files HAVE_GLIB_GREGEX_H - found
-- checking for one of the modules 'libxml-2.0'
--   found libxml-2.0, version 2.7.3
-- checking for one of the modules 'libsyncml-1.0>=0.5.0'
--   found libsyncml-1.0, version 0.5.4
-- Configuring done
-- Generating done
-- Build files have been written
to: /home/jas/opensync-head/build/syncml
Scanning dependencies of target syncml-plugin
[ 10%] Building C object
src/CMakeFiles/syncml-plugin.dir/syncml_plugin.o
In file included
from /home/jas/opensync-head/src/syncml/src/syncml_plugin.c:24:
/home/jas/opensync-head/src/syncml/src/syncml_common.h:87: error:
expected specifier-qualifier-list before ‘SmlBool’
/home/jas/opensync-head/src/syncml/src/syncml_common.h:186: error:
expected declaration specifiers or ‘...’ before ‘SmlError’
make[2]: *** [src/CMakeFiles/syncml-plugin.dir/syncml_plugin.o] Error 1
make[1]: *** [src/CMakeFiles/syncml-plugin.dir/all] Error 2
make: *** [all] Error 2
[ 10%] Building C object
src/CMakeFiles/syncml-plugin.dir/syncml_plugin.o
In file included
from /home/jas/opensync-head/src/syncml/src/syncml_plugin.c:24:
/home/jas/opensync-head/src/syncml/src/syncml_common.h:87: error:
expected specifier-qualifier-list before ‘SmlBool’
/home/jas/opensync-head/src/syncml/src/syncml_common.h:186: error:
expected declaration specifiers or ‘...’ before ‘SmlError’
make[2]: *** [src/CMakeFiles/syncml-plugin.dir/syncml_plugin.o] Error 1
make[1]: *** [src/CMakeFiles/syncml-plugin.dir/all] Error 2
make: *** [all] Error 2

Re: [Opensync-users] error building multisync-gui

[Christian H. <Chr...@co...>]

freeslkr schrieb:
> I checked out the latest svn of multisync-gui from
> http://svn.opensync.org/multisync/trunk-gui. (Is this the correct repo?)
> I get the following errors while building, but I don't see anything wrong
> with msync_group.h.

This is caused by http://www.opensync.org/changeset/5407
There are some hints on how to change it.

Christian
--
Christian Hilgers                  |ConSol*
Tel.   +49.2102.994-423            |Consulting&Solutions Software GmbH
Fax    +49.2102.994-411            |Berliner Str. 101, 40880 Ratingen
email: Chr...@co... |WWW: http://www.consol.de

[Opensync-users] Nokia 6220 classic

[turing79it <m.r...@gm...>]

Hi all.

I just unpacked my new 6220, which I was confident would work with opensync
because of this pages:

https://help.ubuntu.com/community/NokiaEvolutionSyncing?action=show
http://article.gmane.org/gmane.comp.misc.opensync.user/2865

Nonetheless, I cannot get it to work neither with SyncML nor with gnokii.

Anybody can help me with some pointers/instructions?

Thanks!

M.
-- 
View this message in context: http://www.nabble.com/Nokia-6220-classic-tp24464758p24464758.html
Sent from the Opensync - User mailing list archive at Nabble.com.

Re: [Opensync-users] Should I use opensync 0.22 or trunk version?

[Jurian S. <sub...@ju...>]

Hi all,
I have been looking in some (temporary) alternatives for opensync. Currently a 
student is doing a project for GSoC and working on a sync client for Akonadi 
based on libsyncml.

Though the project wouldn't be finished before September, it's still worth 
looking into it. You might sync your phone (if you're using Akonadi) with this 
client soon.

See the website for more info: http://saschpe.wordpress.com

Regards, Jurian
Soflomo.com

Op Tuesday 07 July 2009 09:16:33 schreef Bjoern Ricks:
> As I wrote many many times to the list we are very sorry that we haven't
> finished a new version since month. But and that is the big problem of
> opensync we are only two developers currently and we have both full time
> jobs besides opensync. I met Daniel at the Linuxtag in Berlin and we
> discussed the last open tickets for 0.39. We are sure that we can fix
> that tickets but we can't promise any date when it will be finished.
>
> Again I am very sorry that the development stagnated for such a long time!
>
>
> Regards
> Bjoern

[Opensync-users] opensync at FreeBSD doesn't see python plugins

[Roman P. <rp...@tn...>]

I've installed opensync 0.22 on FreeBSD. Together I've installed python plugin. The plugins dir looks as follows:

[usr1@bimbo /usr/local/lib/opensync/plugins]$ ls -al
total 82
-rwxr-xr-x  1 root  wheel   1156  7 Jan 10:19 file_sync.la
-rwxr-xr-x  1 root  wheel  18691  7 Jan 10:19 file_sync.so
-rwxr-xr-x  1 root  wheel   1260  5 Jan 11:15 python_module.la
-rwxr-xr-x  1 root  wheel  13727  5 Jan 11:15 python_module.so
-rwxr-xr-x  1 root  wheel   1302  7 Jan 10:20 sunbird_sync.la
-rwxr-xr-x  1 root  wheel  38004  7 Jan 10:20 sunbird_sync.so
drwxr-xr-x  2 root  wheel    512  7 Jan 10:11 .
drwxr-xr-x  5 root  wheel    512  6 Jan 07:57 ..

There are two python plugins in the python-plugins dir as well:


[usr1@bimbo /usr/local/lib/opensync/python-plugins]$ ls -al
total 26
-r--r--r--  1 root  wheel  1100  5 Jan 11:15 sample.py
-r-xr-xr-x  1 root  wheel  9214  7 Jan 10:22 synce-opensync-plugin.py

But opensync dosn't see theese plugins:
$ msynctool --listplugins
Available plugins:
sunbird-sync
file-sync

Any suggestion how to debug it?

Thank you,
--
Roman

Re: [Opensync-users] Should I use opensync 0.22 or trunk version?

[Bjoern R. <bjo...@go...>]

As I wrote many many times to the list we are very sorry that we haven't
finished a new version since month. But and that is the big problem of
opensync we are only two developers currently and we have both full time
jobs besides opensync. I met Daniel at the Linuxtag in Berlin and we
discussed the last open tickets for 0.39. We are sure that we can fix
that tickets but we can't promise any date when it will be finished.

Again I am very sorry that the development stagnated for such a long time!


Regards
Bjoern

Re: [Opensync-users] Should I use opensync 0.22 or trunk version?

[Joe C. <joe...@gm...>]

Bjoern Ricks wrote:
> Hi Joe,

Hi Bjoern,

> opensync 0.22 is the latest stable version but it is really really old,
> has many bugs and shortcomings. We are currently trying to release
> opensync 0.39 in the next weeks which should be something like a beta
> for the next stable release. We aren't able to schedule a release date
> because it depends on the work load of the developers.

I've been waiting for weeks. Would you tell me when the opensync 0.39
will be released?
Thanks.

> Regards,
> Bjoern

Regards,
Joe.

[Opensync-users] [repost] Misconfiguration, not supported, or bugs?

[Jason G. <exp...@lo...>]

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

Re: [Opensync-users] Should I use opensync 0.22 or trunk version?

[Bjoern R. <bjo...@go...>]

Hi Joe,

opensync 0.22 is the latest stable version but it is really really old,
has many bugs and shortcomings. We are currently trying to release
opensync 0.39 in the next weeks which should be something like a beta
for the next stable release. We aren't able to schedule a release date
because it depends on the work load of the developers.

Therefore you should try to use 0.22 first and afterwards if you
couldn't sync your phone successfully you can try trunk. BUT please
always backup all your data first. With trunk it is always possible to
loose your data.
If you want to use opensync together with syncml you have to install
libsyncml (with activated obex and http support), of course opensync and
the opensync syncml plugin which you can find at
http://svn.opensync.org/plugins/syncml/ To sync your file with another
peer you probably need an additional plugin like file-sync.

Regards,
Bjoern
> Hello,
>
> I'm wondering I should use opensync 0.22 or trunk version to test sync
> via my cell phone.
> opensync 0.22 works fine with Nokia N73, but trunk version osynctool
> has some problem.
> For example:
>
> # ./osynctool --listplugin
> Available plugins:
>
> I did install libopensync and libsyncml. It seems that libsyncml
> doesn't include syncml-obex-client
> and syncml-http-client.
>
> Regards,
> Joe.
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing 
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users
>   


-- 
/Bjoern Ricks

[Opensync-users] Should I use opensync 0.22 or trunk version?

[Joe C. <joe...@gm...>]

Hello,

I'm wondering I should use opensync 0.22 or trunk version to test sync
via my cell phone.
opensync 0.22 works fine with Nokia N73, but trunk version osynctool
has some problem.
For example:

# ./osynctool --listplugin
Available plugins:

I did install libopensync and libsyncml. It seems that libsyncml
doesn't include syncml-obex-client
and syncml-http-client.

Regards,
Joe.

[Opensync-users] error building multisync-gui

[freeslkr <fre...@ma...>]

I checked out the latest svn of multisync-gui from
http://svn.opensync.org/multisync/trunk-gui. (Is this the correct repo?)
I get the following errors while building, but I don't see anything wrong
with msync_group.h.

  Scanning dependencies of target multisyncgui
  [ 14%] Building C object src/CMakeFiles/multisyncgui.dir/plugins/msync_default.o
  In file included from /home/dev/Cache/cvs/opensync/multisync/src/plugins/../multisync.h:33,
                 from /home/dev/Cache/cvs/opensync/multisync/src/plugins/msync_default.c:1:
  /home/dev/Cache/cvs/opensync/multisync/src/plugins/../msync_group.h:44: error: expected ‘)’ before ‘*’ token
  /home/dev/Cache/cvs/opensync/multisync/src/plugins/../msync_group.h:45: error: expected ‘)’ before ‘*’ token
  /home/dev/Cache/cvs/opensync/multisync/src/plugins/../msync_group.h:46: error: expected ‘)’ before ‘*’ token
  make[2]: *** [src/CMakeFiles/multisyncgui.dir/plugins/msync_default.o] Error 1
  make[1]: *** [src/CMakeFiles/multisyncgui.dir/all] Error 2
  make: *** [all] Error 2

Any help will be appreciated.

Re: [Opensync-users] Nokia N73 fail to sync

[Joe C. <joe...@gm...>]

Joe Culler wrote:
> Michael Bell  wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi Joe,
>>
>> Joe Culler wrote:
>>>
>>> I downloaded libsyncml via svn trunk. When I connected
>>> N73, it shows:
>>>
>>> # syncml-ds-tool -u
>>> Found 2 USB OBEX interfaces
>>> Interface 0:
>>>         Manufacturer: Nokia
>>>         Product: Nokia N73
>>>         Interface description: SYNCML-SYNC
>>> Interface 1:
>>>         Manufacturer: Nokia
>>>         Product: Nokia N73
>>>         Interface description: PC Suite Services
>>> Use '-u interface_number' to connect
>>>
>>> # syncml-ds-tool -u 1 --identifier "PC Suite" --sync text/x-vcard
>>> Contacts
>>> ** Message: ERROR: An internal misconfiguration was detected. The OBEX
>>> client cannot connect to the configured device or resource (Not found
>>> - 0x44).
>>>
>>> Does anyone know how to solve it? Thanks.
>>
>> - -u 0 is the correct interface. You must synchronize with SYNCML-SYNC.
>
> Thanks for the quick reply. I use 0 instead of 1, I got:
>
> # syncml-ds-tool -u 0 --identifier "PC Suite" --sync text/x-vcard
> Contacts
> ** Message: ERROR: An internal I/O error occured. Unknown response (0x4f)

Did I miss something? Thanks.

>> Best regards
>>
>> Michael
>> - --
>> ___________________________________________________________________
>>
>> Michael Bell                        Humboldt-Universitaet zu Berlin
>>
>> Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
>> Fax:  +49 (0)30-2093 2704           Unter den Linden 6
>> mic...@cm...       D-10099 Berlin
>> ___________________________________________________________________
>>
>> PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iEYEARECAAYFAkouH9cACgkQ2L0ZGCAwWquaZACcDsIr3n0SBXqp2WakEW/pSoZH
>> bcUAn2TRFAP3++Nl1WKUoaQytolDZs8t
>> =c4DP
>> -----END PGP SIGNATURE-----
>
> Regards,
> Joe.
>

Re: [Opensync-users] synchronisation takes too long?

[Frisco <ope...@bi...>]

Frisco schrieb:
> Hi,
> 
...
> I try to sync my Nokia 5140i, contacts and calendar.
> 
> Connection works fine with the gnokii plugin (and gnokii on the command
> line).
> 
> I can easily sync my contacts and calendar from the phone to kontact
> (kadressbook/korganizer), but I don't manage to write my contacts to the
> phone.

Unfortunatly this is still the fact, but I managed to get msynctool at 
the commandline working (installed the wrong package, multisync-tools 
contains the 0.22 version of msynctool. With msynctool 0.38 I can't get 
the right plugins in Debian due to conflicts of depending packages).

Nevertheless, I can now provide better debug information from the 
commanline, maybe one of the experts has an idea why my contacts are not 
written to my phone?

frisco@linux:~$ msynctool --showgroup gnokii-evolution
Groupname: gnokii-evolution
Member 1: gnokii-sync
         Configuration : <config>
   <connection>serial</connection>
   <port>/dev/ttyUSB0</port>
   <model>5140i</model>
</config>

Member 2: evo2-sync
         Configuration : <?xml version="1.0"?>
<config>
   <address_path>default</address_path>
   <calendar_path/>
   <tasks_path/>
</config>


frisco@linux:~$ msynctool --sync gnokii-evolution --conflict 2
Synchronizing group "gnokii-evolution"
The previous synchronization was unclean. Slow-syncing
GConf Error: Failed to contact configuration server; some possible 
causes are that you need to enable TCP/IP networking for ORBit, or you 
have stale NFS locks due to a system crash. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed 
to get connection to session: Failed to connect to socket 
/tmp/dbus-4wWVON9BEg: Connection refused)
GConf Error: Failed to contact configuration server; some possible 
causes are that you need to enable TCP/IP networking for ORBit, or you 
have stale NFS locks due to a system crash. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed 
to get connection to session: Failed to connect to socket 
/tmp/dbus-4wWVON9BEg: Connection refused)
GConf Error: Failed to contact configuration server; some possible 
causes are that you need to enable TCP/IP networking for ORBit, or you 
have stale NFS locks due to a system crash. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed 
to get connection to session: Failed to connect to socket 
/tmp/dbus-4wWVON9BEg: Connection refused)
GConf Error: Failed to contact configuration server; some possible 
causes are that you need to enable TCP/IP networking for ORBit, or you 
have stale NFS locks due to a system crash. See 
http://projects.gnome.org/gconf/ for information. (Details -  1: Failed 
to get connection to session: Failed to connect to socket 
/tmp/dbus-4wWVON9BEg: Connection refused)
Serial port speed 0 not supported!
Member 2 of type evo2-sync just connected
Member 1 of type gnokii-sync just connected
All clients connected or error
Received an entry pas-id-4A2D1BFD00000036 with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFD0000004D with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFD0000000E with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFD0000001A with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFE000000AD with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFD00000017 with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFE00000092 with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFD00000047 with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFE00000084 with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Received an entry pas-id-4A2D1BFE0000009D with data of size 4 from 
member 2 (evo2-sync). Changetype ADDED
Member 2 of type evo2-sync just sent all changes
Received an entry gnokii-contact-ME-1 with data of size 4 from member 1 
(gnokii-sync). Changetype ADDED
Member 1 of type gnokii-sync just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 2 of type evo2-sync committed all changes.
***** data.number "sac...@gm..."
strlen 15
***** j 30 count 148
***** GN_PHONEBOOK_ENTRY_MAX_LENGTH - count 840 count 184
Error writing entry pas-id-4A2D1BFD00000036 to member 1 (gnokii-sync): 
Unable to write contact.
Mapping Write Error: Unable to write contact.
***** data.number "http://www.tnt.de"
strlen 17
***** j 34 count 146
***** GN_PHONEBOOK_ENTRY_MAX_LENGTH - count 838 count 186
***** data.number "Ale...@tn..."
strlen 24
***** j 48 count 186
***** GN_PHONEBOOK_ENTRY_MAX_LENGTH - count 784 count 240
Error writing entry pas-id-4A2D1BFD0000000E to member 1 (gnokii-sync): 
Unable to write contact.
Mapping Write Error: Unable to write contact.

Cheers,
Andre



-- 
Personal weblog and more: http://bischof.homelinux.net

Stilblüten aus Schreiben von Versicherungsnehmern:
Ich brauche keine Lebensversicherung. Ich möchte, daß alle richtig
traurig sind, wenn ich einmal sterbe.

Re: [Opensync-users] Nokia N73 fail to sync

[Joe C. <joe...@gm...>]

Michael Bell  wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Joe,
>
> Joe Culler wrote:
>>
>> I downloaded libsyncml via svn trunk. When I connected
>> N73, it shows:
>>
>> # syncml-ds-tool -u
>> Found 2 USB OBEX interfaces
>> Interface 0:
>>         Manufacturer: Nokia
>>         Product: Nokia N73
>>         Interface description: SYNCML-SYNC
>> Interface 1:
>>         Manufacturer: Nokia
>>         Product: Nokia N73
>>         Interface description: PC Suite Services
>> Use '-u interface_number' to connect
>>
>> # syncml-ds-tool -u 1 --identifier "PC Suite" --sync text/x-vcard
>> Contacts
>> ** Message: ERROR: An internal misconfiguration was detected. The OBEX
>> client cannot connect to the configured device or resource (Not found
>> - 0x44).
>>
>> Does anyone know how to solve it? Thanks.
>
> - -u 0 is the correct interface. You must synchronize with SYNCML-SYNC.

Thanks for the quick reply. I use 0 instead of 1, I got:

# syncml-ds-tool -u 0 --identifier "PC Suite" --sync text/x-vcard
Contacts
** Message: ERROR: An internal I/O error occured. Unknown response (0x4f)

> Best regards
>
> Michael
> - --
> ___________________________________________________________________
>
> Michael Bell                        Humboldt-Universitaet zu Berlin
>
> Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
> Fax:  +49 (0)30-2093 2704           Unter den Linden 6
> mic...@cm...       D-10099 Berlin
> ___________________________________________________________________
>
> PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkouH9cACgkQ2L0ZGCAwWquaZACcDsIr3n0SBXqp2WakEW/pSoZH
> bcUAn2TRFAP3++Nl1WKUoaQytolDZs8t
> =c4DP
> -----END PGP SIGNATURE-----

Regards,
Joe.

Re: [Opensync-users] Nokia N73 fail to sync

[Michael B. <mic...@cm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Joe,

Joe Culler wrote:
> 
> I downloaded libsyncml via svn trunk. When I connected
> N73, it shows:
> 
> # syncml-ds-tool -u
> Found 2 USB OBEX interfaces
> Interface 0:
>         Manufacturer: Nokia
>         Product: Nokia N73
>         Interface description: SYNCML-SYNC
> Interface 1:
>         Manufacturer: Nokia
>         Product: Nokia N73
>         Interface description: PC Suite Services
> Use '-u interface_number' to connect
> 
> # syncml-ds-tool -u 1 --identifier "PC Suite" --sync text/x-vcard
> Contacts
> ** Message: ERROR: An internal misconfiguration was detected. The OBEX
> client cannot connect to the configured device or resource (Not found
> - 0x44).
> 
> Does anyone know how to solve it? Thanks.

- -u 0 is the correct interface. You must synchronize with SYNCML-SYNC.

Best regards

Michael
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkouH9cACgkQ2L0ZGCAwWquaZACcDsIr3n0SBXqp2WakEW/pSoZH
bcUAn2TRFAP3++Nl1WKUoaQytolDZs8t
=c4DP
-----END PGP SIGNATURE-----

[Opensync-users] Nokia N73 fail to sync

[Joe C. <joe...@gm...>]

Hello,

I downloaded libsyncml via svn trunk. When I connected
N73, it shows:

# syncml-ds-tool -u
Found 2 USB OBEX interfaces
Interface 0:
        Manufacturer: Nokia
        Product: Nokia N73
        Interface description: SYNCML-SYNC
Interface 1:
        Manufacturer: Nokia
        Product: Nokia N73
        Interface description: PC Suite Services
Use '-u interface_number' to connect

# syncml-ds-tool -u 1 --identifier "PC Suite" --sync text/x-vcard
Contacts
** Message: ERROR: An internal misconfiguration was detected. The OBEX
client cannot connect to the configured device or resource (Not found
- 0x44).

Does anyone know how to solve it? Thanks.

Regards,
Joe.

[Opensync-users] synchronisation takes too long?

[Frisco <ope...@bi...>]

Hi,

sorry for possible cross-posting, but I don't know whether the problem
is with gnokii or with opensync  :(

I try to sync my Nokia 5140i, contacts and calendar.

Connection works fine with the gnokii plugin (and gnokii on the command
line).

I can easily sync my contacts and calendar from the phone to kontact
(kadressbook/korganizer), but I don't manage to write my contacts to the
phone.

I deleted all contacts on the phone (internal memory), with a sync-pair
gnokii-sync <-> kdepim-sync I got 2 entries written to the phone after
approximatly 3 hours.

Something seems to be working, as I can see in multisync0.90 that the
buttons remain grey after starting the sync.

multisync0.90 says furthermore:

gnokii-sync: Sent all changes
kdepim-sync: Sent all changes.

184 entries received.
All conflicts have been reported.
(Buttons still grey).

The process-lists shows three active tasks:

frisco    6102  3.0  0.6 208892 27016 ?        Sl   16:14   1:29  \_
/usr/bin/multisync0.90
frisco    6507  1.3  0.1  51968  5612 ?        Sl   16:23   0:32  |   \_
/usr/lib/opensync/osplugin /home/frisco/.opensync-0.22/group7 1
frisco    6512  2.1  0.1  67240  7720 ?        Sl   16:23   0:51  |   \_
/usr/lib/opensync/osplugin /home/frisco/.opensync-0.22/group7 2

I can watch them working in top too.

I use:
root@linux:/lost+found# dpkg -l *sync* |grep ^ii
ii  kitchensync                                    4:3.5.9-5
             Synchronization framework
ii  ksync                                          4:3.5.5.dfsg.1-6
             KDE Sync
ii  libasyncns0                                    0.3-1
             Asyncronous name service query library
ii  libmultisync-plugin-backup                     0.82-8.2
             Backup plug for MultiSync
ii  libmultisync-plugin-evolution                  0.82-8.2
             Ximian Evolution plugin for MultiSync
ii  libmultisync-plugin-irmc                       0.82-8.2
             IrMc Mobile plugin for MultiSync
ii  libmultisync-plugin-irmc-bluetooth             0.82-8.2
             Adds Bluetooth support to the IrMC plugin
ii  libopensync0                                   0.22-2
             Synchronisation framework for email/pdas/and
ii  libopensync1exp6                               0.38-1
             Synchronisation framework for email/pdas/and
ii  libpisync1                                     0.12.3-11
             synchronization library for PalmOS devices
ii  msynctool                                      0.38-2
             Commandline interface for OpenSync
ii  multisync                                      0.82-8.2
             A program to synchronize PIM data
ii  multisync0.90                                  0.92.0~svn355-1
             PIM Synchronization Tool
ii  opensync-format-vformat                        0.38-1
             Opensync vformat plugin
ii  opensync-plugin-evolution                      0.22-2+b1
             Evolution plugin for opensync
ii  opensync-plugin-file                           0.22-2
             Opensync file plugin
ii  opensync-plugin-gnokii                         0.22-1+b1
             Opensync gnokii plugin
ii  opensync-plugin-google-calendar                0.22-6
             Opensync Google Calendar plugin
ii  opensync-plugin-iceowl                         0.22-3
             Opensync Mozilla Calendar(Iceowl) plugin
ii  opensync-plugin-irmc                           0.22-3
             IrMC plugin for opensync
ii  opensync-plugin-kdepim                         0.22-4
             KDE plugin for opensync
ii  opensync-plugin-sunbird                        0.22-3
             Opensync Mozilla Calendar(Iceowl) plugin


There seem to be opensync 0.22 and 0.38 installed (under Debian
testing), could that cause conflicts?

I noticed that multisync0.90 writes to .opensync-0.22/ (see process list
above), if I try to use msynctool, it tries to use .opensync/, but
complains about no available plugins, thus I use multisync0.90.

I read a lot docs about gnokii and opensync/multisync, but couldn't
solve the problem on my own - it would be great if anyone could give me
a hint, any help is very appreciated!

Cheers,
Andre

[Opensync-users] libsyncml 0.5.4

[Michael B. <mic...@cm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

libsyncml 0.5.4 release notes

Download: https://sourceforge.net/project/showfiles.php?group_id=25311

Minor Changes
=============

  - All header files of the high level API are missing
    the extern "C" declarations for C++ (ticket #240).
    The patch was supplied by Sascha Peilicke.

A special thanks goes to Sascha Peilicke who fixed the C++ issue.

Best regards

Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkonmCEACgkQ2L0ZGCAwWquv/gCg6I37KTizQCjiycEWhuNitXiX
snQAn2kPnfol6fYqlyyz3fTrT2hb+Mcl
=gOqv
-----END PGP SIGNATURE-----

[Opensync-users] "Bad Characters" == non-ASCIIcharacters?

[Dotan C. <dot...@gm...>]

My native language is not represented in ASCII. I am considering
replacing my Nokia 6288 with an N95 and hopefully I will be able to
sync it with Kontact (KDE PIM). However, I noticed on this page that
the user had problems with "bad characters":
http://www.opensync.org/wiki/releases/0.2x/Nokia_N95

Is the definition of "bad characters" non-ASCII? Can opensync sync
non-ASCII languages?

Thanks!

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il

[Opensync-users] Schemas validity error when syncing todos

[Jason G. <exp...@lo...>]

Hello again,

I'm also unable to sync todos between obex->file with my Nokia 6300.
Resources sections are shown at [1] and [2] below.  I get a lot of 

"Schemas validity error"

as shown in [3].  

Is there anything I can do to permit the sync (e.g. can I somehow map
"NEEDS ACTION" to "NEEDS-ACTION"?

J.

-----------------------
[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.

[Opensync-users] "Unable to find conversion" for {obex, memo} -> {file, file}

[Jason G. <exp...@lo...>]

Hello,

I've built opensync off svn head, and am trying to sync memos with my
Nokia 6300, using obex->file.  Alas, I get:

"ERROR: Unable to find conversion path"

and so I am trying to rule out a problem with my configuration.

Do the resource entries below look OK?

Thanks for any tips:

J.

-----------------------
[1] Extract from obex config
-----------------------
  <Resources>
    <Resource>
      <Enabled>1</Enabled>
      <Formats>
        <Format>
          <Name>memo</Name>
        </Format>
      </Formats>
      <Name>Notes</Name>
      <ObjType>note</ObjType>
    </Resource>
  </Resources>

-----------------------
[2] 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>

-----------------------
[3] 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

Re: [Opensync-users] wbxml from svn head does not build

[Jason G. <exp...@lo...>]

On Wed, 2009-06-03 at 16:10 +0200, Michael Bell wrote:
> It looks like your svn client does not checkout the svn:externals.

Ah, thanks Michael,

FYI, an svn co results in the untrusted cert message below.  I must have
inadvertently rejected this.

Cheers,

J.

----------------------------------

svn co http://svn.opensync.org/libwbxml/wbxml2/trunk

....

Fetching external item into 'trunk/cmake'
Error validating server certificate for 'https://svn.opensync.org:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: milliways.cynapses.org
 - Valid: from Sun, 22 Feb 2009 13:56:41 GMT until Tue, 22 Feb 2011
13:56:41 GMT
 - Issuer: http://www.cacert.org, Root CA
 - Fingerprint:
f0:59:d4:c8:34:61:57:8d:16:de:2f:0e:31:76:a9:50:10:b9:a5:2b
(R)eject, accept (t)emporarily or accept (p)ermanently? 

Re: [Opensync-users] wbxml from svn head does not build

[Michael B. <mic...@cm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jason,

Jason Grant wrote:
> 
> I cannot build from a clean checkout of wbxml from svn head.
> 
> I get the output at [1] below.  It is complaining about the absence of
> AddDocumentation and MacroEnsureOutOfSourceBuild.  I noticed these in my
> checkout of opensync, and if I copy these into my wbxml source folder
> under cmake/modules, the build goes a little further, but fails as per
> [2] below.  In that case it is also complaining about missing resources
> (perl and shell scripts), so I am wonder if more is missing from svn
> than just the cmake/modules files.

It looks like your svn client does not checkout the svn:externals.

svn propget svn:externals

cmake https://svn.opensync.org/branches/3rd-party-cmake-modules
tests https://svn.opensync.org/libwbxml/wbxmlTestSuite/trunk

Best regards

Michael
- --
___________________________________________________________________

Michael Bell                        Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482           ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704           Unter den Linden 6
mic...@cm...       D-10099 Berlin
___________________________________________________________________

PGP Fingerprint: 09E4 3D29 4156 2774 0F2C  C643 D8BD 1918 2030 5AAB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkomhEMACgkQ2L0ZGCAwWqs7agCg06pnI6VKZXd0+SG3PpDWSV4i
k+AAoMvdjVQ4BlEvKPdvA/HVT9bdGylD
=HwJs
-----END PGP SIGNATURE-----

[Opensync-users] wbxml from svn head does not build

[Jason G. <exp...@lo...>]

Hello.

I cannot build from a clean checkout of wbxml from svn head.

I get the output at [1] below.  It is complaining about the absence of
AddDocumentation and MacroEnsureOutOfSourceBuild.  I noticed these in my
checkout of opensync, and if I copy these into my wbxml source folder
under cmake/modules, the build goes a little further, but fails as per
[2] below.  In that case it is also complaining about missing resources
(perl and shell scripts), so I am wonder if more is missing from svn
than just the cmake/modules files.

Thanks for any guidance or independent confirmation that a clean
checkout of svn head is not broken.

J.


----------------------------------------------
[1] Clean checkout
----------------------------------------------
[jas@talby wbxml2]$ cmake
-DCMAKE_INSTALL_PREFIX=/home/jas/opensync-head/install /home/jas/opensync-head/wbxml2
-- The C compiler identification is GNU
-- Check for working C compiler: /usr/lib/ccache/gcc
-- Check for working C compiler: /usr/lib/ccache/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
CMake Error at CMakeLists.txt:57 (INCLUDE):
  include could not find load file:

    AddDocumentation


-- Looking for include files HAVE_LIMITS_H
-- Looking for include files HAVE_LIMITS_H - found
-- Looking for include files HAVE_CTYPE_H
-- Looking for include files HAVE_CTYPE_H - found
-- Looking for include files HAVE_STDLIB_H
-- Looking for include files HAVE_STDLIB_H - found
-- Looking for include files HAVE_STDIO_H
-- Looking for include files HAVE_STDIO_H - found
-- Looking for include files HAVE_STDARG_H
-- Looking for include files HAVE_STDARG_H - found
-- Looking for include files HAVE_ASSERT_H
-- Looking for include files HAVE_ASSERT_H - found
CMake Error at CMakeLists.txt:67 (INCLUDE):
  include could not find load file:

    MacroEnsureOutOfSourceBuild


CMake Error at CMakeLists.txt:68 (MACRO_ENSURE_OUT_OF_SOURCE_BUILD):
  Unknown CMake command "MACRO_ENSURE_OUT_OF_SOURCE_BUILD".


-- Configuring incomplete, errors occurred!


I'm unable to build wbxml off svn head, and based on the fix I found, I
suspect that svn is incomplete.

----------------------------------------------
[2] After cmake/modules has been copied from opensync into wbxml
----------------------------------------------
[jas@talby wbxml2]$ cmake
-DCMAKE_INSTALL_PREFIX=/home/jas/opensync-head/install /home/jas/opensync-head/wbxml2
-- Found Expat: /usr/lib/libexpat.so
-- checking for one of the modules 'check'
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Looking for getopt
-- Looking for getopt - found
-- ==================================================
-- verbose mode                                 OFF
-- POSIX getopt                                 ON
-- unit tests                                   OFF
-- perl binary (test generated XML)             ON
-- diff binary (test generated XML)             ON
-- enable string tables                         ON
-- enable WML support                           ON
-- enable WTA support                           ON
-- enable SI support                            ON
-- enable SL support                            ON
-- enable CO support                            ON
-- enable PROV support                          ON
-- enable EMN support                           ON
-- enable DRMREL support                        ON
-- enable OTA_SETTINGS support                  ON
-- enable SYNCML support                        ON
-- enable WV support                            ON
-- enable AIRSYNC support                       ON
-- build dynamic documentation                  OFF
-- install documentation                        ON
CMake Error: File /home/jas/opensync-head/wbxml2/tests/launchTests.sh
does not exist.
CMake Error at CMakeLists.txt:248 (CONFIGURE_FILE):
  configure_file Problem configuring file


CMake Error: File /home/jas/opensync-head/wbxml2/tests/normalize_xml.pl
does not exist.
CMake Error at CMakeLists.txt:249 (CONFIGURE_FILE):
  configure_file Problem configuring file


-- Configuring incomplete, errors occurred!