Package: multisync-tools Version: 0.92.0~svn355-2 Severity: important File: /usr/bin/msynctool
Somehow I still cannot write to the SyncML server (a Nokia E71 phone via bluetooth), although reading works (config attached). Anyway, there's an error during the sync, meaning that the two sides have diverged (record 1050 is now different on both sides). Yet, the subsequent sync does not consider that and pretends that everything is hunky dory. That should not be. lapse:~|master|.opensync-0.22/group1% msynctool --sync madduck Synchronizing group "madduck" Member 1 of type file-sync just connected received event dsession received contact dsession received note dsession Member 2 of type syncml-obex-client just connected All clients connected or error Received an entry 1050 with data of size 4 from member 1 (file-sync). Changetype MODIFIED Member 1 of type file-sync just sent all changes Received an reply to our Alert Received an reply to our Alert Received an reply to our Alert Going to receive 0 changes Going to receive 0 changes Going to receive 0 changes Member 2 of type syncml-obex-client just sent all changes All clients sent changes or error All conflicts have been reported Member 1 of type file-sync committed all changes. Received an reply to our sync Received an reply to our sync Received an reply to our sync Error writing entry 1050 to member 2 (syncml-obex-client): Unable to commit change. Error 415 Mapping Write Error: Unable to commit change. Error 415 Member 2 of type syncml-obex-client committed all changes. All clients have written Member 1 of type file-sync just disconnected Member 2 of type syncml-obex-client just disconnected All clients have disconnected The sync failed: Unable to write one or more objects Error while synchronizing: Unable to write one or more objects Second sync: lapse:~|master|.opensync-0.22/group1% msynctool --sync madduck Synchronizing group "madduck" Member 1 of type file-sync just connected received event dsession received contact dsession received note dsession Member 2 of type syncml-obex-client just connected All clients connected or error Member 1 of type file-sync just sent all changes Received an reply to our Alert Received an reply to our Alert Received an reply to our Alert Going to receive 0 changes Going to receive 0 changes Going to receive 0 changes Member 2 of type syncml-obex-client just sent all changes All clients sent changes or error Member 1 of type file-sync committed all changes. Member 1 of type file-sync just disconnected Received an reply to our sync Received an reply to our sync Received an reply to our sync Member 2 of type syncml-obex-client committed all changes. All clients have written Member 2 of type syncml-obex-client just disconnected All clients have disconnected The sync was successful -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages multisync-tools depends on: ii libc6 2.10.2-3 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.22.3-2 The GLib library of C routines ii libopensync0 0.22-4+b1 Synchronisation framework for emai multisync-tools recommends no packages. multisync-tools suggests no packages. -- no debconf information -- .''`. martin f. krafft <madd...@d.o> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systems
<?xml version="1.0"?> <config> <!-- (Only for bluetooth) The bluetooth address if the bluetooth mode is selected --> <bluetooth_address>00:21:FE:90:AC:31</bluetooth_address> <!-- (Only for bluetooth) The bluetooth channel to use. `sdptool browse $MAC` to search for the correct channel --> <bluetooth_channel>10</bluetooth_channel> <!-- (Only for USB) The usb interface number of the SYNCML-SYNC target. use syncml-obex-client -u (you will need access to the USB raw device) to find it. --> <interface>0</interface> <!-- The string that the plugin will use to identify itself. Some devices need a special string here. --> <identifier>PC Suite</identifier> <!-- The syncml version to use: 0 for 1.0, 1 for 1.1 and 2 for 1.2 --> <version>1</version> <!-- if the plugin should use wbxml --> <wbxml>1</wbxml> <!-- The username to use. Leave empty to not require a username --> <username></username> <!-- the password for the username --> <password></password> <!-- sets the connection type to use. 5 means obex over usb, 2 means obex over bluetooth --> <type>2</type> <!-- If wbxml is enabled, defines wether the wbxml should use string tables --> <usestringtable>0</usestringtable> <!-- Never send ADD command, but send REPLACE (not needed normally) --> <onlyreplace>0</onlyreplace> <!-- Workaround around for mobile phones which only use local timestamps and _no_ UTC timestamps! --> <onlyLocaltime>0</onlyLocaltime> <!-- Sets the maximum allowed size in bytes of incoming messages (some device need this option set). Example: 10000 --> <recvLimit>0</recvLimit> <maxObjSize>100000</maxObjSize> <!-- The name of the contacts db. Must be the same as the phones sends --> <contact_db>Contacts</contact_db> <!-- The name of the calendar db. Must be the same as the phones sends --> <calendar_db>Calendar</calendar_db> <!-- The name of the note db. Must be the same as the phones sends --> <note_db>Notes</note_db> </config>
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
