You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(57) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(38) |
Feb
(42) |
Mar
(39) |
Apr
(59) |
May
(91) |
Jun
(56) |
Jul
(114) |
Aug
(151) |
Sep
(100) |
Oct
(64) |
Nov
(45) |
Dec
(28) |
| 2004 |
Jan
(62) |
Feb
(38) |
Mar
(65) |
Apr
(20) |
May
(58) |
Jun
(29) |
Jul
(25) |
Aug
(63) |
Sep
(23) |
Oct
(70) |
Nov
(14) |
Dec
(35) |
| 2005 |
Jan
(13) |
Feb
(11) |
Mar
(53) |
Apr
(24) |
May
(51) |
Jun
(25) |
Jul
(18) |
Aug
(24) |
Sep
(5) |
Oct
(18) |
Nov
(47) |
Dec
(17) |
| 2006 |
Jan
(24) |
Feb
(79) |
Mar
(45) |
Apr
(6) |
May
(11) |
Jun
(9) |
Jul
(17) |
Aug
(25) |
Sep
(26) |
Oct
(12) |
Nov
(40) |
Dec
(44) |
| 2007 |
Jan
(37) |
Feb
(25) |
Mar
(21) |
Apr
(40) |
May
(154) |
Jun
(50) |
Jul
(70) |
Aug
(21) |
Sep
(50) |
Oct
(75) |
Nov
(56) |
Dec
(49) |
| 2008 |
Jan
(201) |
Feb
(296) |
Mar
(240) |
Apr
(153) |
May
(185) |
Jun
(120) |
Jul
(216) |
Aug
(165) |
Sep
(73) |
Oct
(136) |
Nov
(85) |
Dec
(126) |
| 2009 |
Jan
(143) |
Feb
(139) |
Mar
(116) |
Apr
(68) |
May
(44) |
Jun
(87) |
Jul
(96) |
Aug
(73) |
Sep
(42) |
Oct
(34) |
Nov
(100) |
Dec
(95) |
| 2010 |
Jan
(38) |
Feb
(47) |
Mar
(22) |
Apr
(19) |
May
(100) |
Jun
(57) |
Jul
(16) |
Aug
(27) |
Sep
(18) |
Oct
(21) |
Nov
(13) |
Dec
(18) |
| 2011 |
Jan
(59) |
Feb
(43) |
Mar
(39) |
Apr
(10) |
May
(32) |
Jun
(2) |
Jul
(7) |
Aug
(6) |
Sep
(4) |
Oct
(8) |
Nov
(2) |
Dec
(2) |
| 2012 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
(2) |
| 2013 |
Jan
(3) |
Feb
|
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
(24) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
|
From: Gustavo <ghr...@gm...> - 2022-11-27 20:47:40
|
Hi guys Performing tests with Synce from PPA (from https://launchpad.net/~synce/+archive/ubuntu/ppa/?field.series_filter=xenial) in Ubuntu (also in Debian Buster) I find the following problem: Nov 25 16:28:46 xenial kernel: [ 6287.060196] ipaq 2-2:1.0: PocketPC PDA converter detected Nov 25 16:28:46 xenial kernel: [ 6287.064513] usb 2-2: PocketPC PDA converter now attached to ttyUSB0 ... Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : running as addon for device /dev/ttyUSB0 Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : GET IP LOCAL: 10.1.20.1 Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : GET IP REMOTE: 10.1.20.2 Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : calling pppd as: Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : ['/usr/sbin/pppd', '/dev/ttyUSB0', '115200', 'connect', '/usr/lib/synce-core/synce-serial-chat', '10.1.20.1:10.1.20.2', 'ms-dns', '10.1.20.1', 'linkname', 'synce-device0'] Nov 25 16:28:47 xenial pppd[3013]: pppd 2.4.7 started by root, uid 0 Nov 25 16:28:47 xenial pppd[3013]: Removed stale lock on ttyUSB0 (pid 2955) Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : successfully configured interface Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : signalling dccm for connection ... Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : signalling dccm with: Nov 25 16:28:47 xenial udev-synce-serial[2999] DEBUG : device-path=/devices/pci0000:00/0000:00:06.0/usb2/2-2/2-2:1.0/ttyUSB0/tty/ttyUSB0, device-ip=10.1.20.2, local-ip=10.1.20.1, rndis=False // So far, everything seems to work fine, but... // Failure in the call: // try: dccm_manager.DeviceConnected(device_path, device_ip, local_ip, rndis) except Exception, e: logger.critical("failed to signal device connect to dccm device manager %s: %s" % (DBUS_SYNCE_MANAGER_OBJPATH, e)) return False Nov 25 16:28:47 xenial dccm[950]: DEBUG: synce_device_manager_device_connected_cb: receieved device connected signal for /devices/pci0000:00/0000:00:06.0/usb2/2-2/2-2:1.0/ttyUSB0/tty/ttyUSB0 Nov 25 16:28:47 xenial dccm[950]: DEBUG: synce_device_manager_check_interface_cb: address not yet ready, failed to bind: Error binding to address: Cannot assign requested address Nov 25 16:37:12 xenial dccm[950]: message repeated 79887 times: [ DEBUG: synce_device_manager_check_interface_cb: address not yet ready, failed to bind: Error binding to address: Cannot assign requested address] The call to the dccm_manager.DeviceConnected object does not execute correctly or end in exception, it remains in a cyclical error. My skills in this matter go as far as this, can anyone help me? Another question I have is... Where is the function run_dccm (device_path, device_ip, local_ip, rndis) called? In previous versions the responsibility was the function Run_dccm, now I don't see where it is used, it is not imported in udev-synce-serial and signal_dccm_connect is not working for me. I would appreciate any help on this. |
|
From: Gustavo <ghr...@gm...> - 2022-11-03 20:40:12
|
Good afternoon guys My name is Gustavo, I am working with the Synce PPA sources to make a DEB version for the current Debian stable *"Bullseye"*. I am not a developer, my specialty is system administration. In the past I've been encouraged to make minor changes to Synce's Python source to adapt it to my needs (in Ubuntu 8.04 Hardy). Today, making an updated version for Debian is a major challenge for me. I am focused on five packages: *libmimedir*, *librra*, *librtfcomp *libraries along with *synce-core* and *synce-sync-engine*. For this purpose, I am using this post as a guide: https://www.linuxquestions.org/questions/linux-software-2/connection-linux-pda-windowsce-4175560071/#post5465293 I prepared the build system with pbuilder, and the result was something strange, unexpected. At the end of the operation, the output indicates that there are unsatisfied dependencies, but these packages are installed in the same or higher version $ sudo /usr/sbin/pbuilder build synce-sync-engine_0.16-0.1~0debian0~bullseye1.dsc (...) dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) python-setuptools python (>= 2.6.6-3) dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting But, APT says otherwise... # apt show debhelper Package: debhelper Version: 13.3.4 # apt show python-setuptools Package: python-setuptools Version: 44.1.1-1 # apt show python Package: python State: not a real (virtual) package N: Cannot select the candidate version of the python package since it has no candidates N: Different versions of the "python" package cannot be selected because it is purely virtual N: No package found $ sudo /usr/sbin/pbuilder build synce-core_0.17-0.1~0debian0~bullseye1.dsc (...) dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper (>= 5) libglib2.0-dev (>= 2.26.0) python (>> 2.6.6) python-all-dev (>> 2.6.6) python-pyrex (>= 0.9.6) quilt ppp libgudev-1.0-dev udev dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting But... # apt show debhelper Package: debhelper Version: 13.3.4 # apt show libglib2.0-dev Package: libglib2.0-dev Version: 2.66.8-1 # apt show python Package: python State: not a real (virtual) package N: Cannot select the candidate version of the python package since it has no candidates N: Different versions of the "python" package cannot be selected because it is purely virtual N: No package found # apt show python-all-dev Package: python-all-dev Version: 2.7.18-3 # apt show python-pyrex (NOT in Bullseye, download from Debian Buster repository) Package: python-pyrex Version: 0.9.9-1 # apt show quilt Package: quilt Version: 0.66-2.1 # apt show ppp Package: ppp Version: 2.4.9-1+1 # apt show libgudev-1.0-dev Package: libgudev-1.0-dev Version: 234-1 # apt show udev Package: udev Version: 247.3-7+deb11u1 Taking a look at the version of Python installed... # apt list --installed | grep ^python | grep stable | cut -d "/" -f 1 python-all-dev python-all python-apt-common python-dev-is-python2 python-is-python2 python-pkg-resources python-setuptools python2-dev python2-minimal python2.7-dev python2.7-minimal python2.7 python2 python3-apt python3-brlapi python3-cairo python3-certifi python3-chardet python3-cups python3-cupshelpers python3-dbus python3-debian python3-distro-info python3-distro python3-distutils python3-gi-cairo python3-gi python3-gpg python3-ibus-1.0 python3-idna python3-ldb python3-lib2to3 python3-libvoikko python3-louis python3-magic python3-mako python3-markupsafe python3-minimal python3-numpy python3-pkg-resources python3-pyatspi python3-pycurl python3-pyside2.qtcore python3-pyside2.qtgui python3-pyside2.qtwidgets python3-requests python3-six python3-smbc python3-software-properties python3-speechd python3-talloc python3-unidiff python3-uno python3-urllib3 python3-xdg python3.9-minimal python3.9 python3 *Any help will be very welcome!!!* Best regards to all |
|
From: gilga g. <gi...@ho...> - 2019-04-23 10:50:26
|
Thanks! Where is the log file? I've read it should be in /var/log/daemon.log but I see no file (https://sourceforge.net/p/synce/mailman/message/18587831/) I've even done a search from '/' and no file was found. My versions of all the programs for SynCE: $ pacman -Qs synce local/librtfcomp 1.3-2 SynCE librtfcomp library local/synce-core 0.17-4 provide a means of communication with a Windows CE device - libraries local/synce-kde 0.16-5 Provide a means of communication with a Windows CE device - KDE tools and integration local/synce-libmimedir 0.4-8 provide a means of communication with a Windows CE device - library that parses MIME Directory Profile. local/synce-rra 0.17-3 provide a means of communication with a Windows CE device - rra libraries for synce local/synce-sync-engine 0.16-3 SynCE sync-engine So it's synce-core 0.17-4 By the way, I know that 'dccm' is running: $ ps -eaf | grep dccm root 4365 1 0 Apr15 ? 00:00:00 /usr/lib/synce-core/dccm --log-level=6 susskind 31041 30707 0 11:58 pts/0 00:00:00 grep dccm On 22/04/2019 11:02, Arndt Kaiser wrote: Hi, dccm is the right one. Are there any log messages present in the journal? And which version / revision of dccm do you use? Cheers, Arndt Am 19.04.19 um 08:52 schrieb gilga gilga: Hi I' m on Arch Linux. I've installed *synce-core* (https://aur.archlinux.org/packages/synce-core/), *synce-kde*, and *sync-synce-sync-engine* as described in the Arch linux wiki for SynCE (https://wiki.archlinux.org/index.php/SynCE). My problem is at the first step, which is launching the `odccm` program. Firstly, it's `/dccm/`, not `/odccm/` which apparently must be launched: |/$ sudo pacman -Ql synce-core | grep dccm synce-core /etc/dbus-1/system.d/org.synce.dccm.conf synce-core /usr/lib/synce-core/dccm synce-core /usr/share/dbus-1/system-services/org.synce.dccm.service/ Then, I'm trying to launch dccm: |/|$ sudo /usr/lib/synce-core/dccm --log-level=6|/ But it returns, with no errors or confirmations about launching. I've tried also launching it with DBus but with the same result: /|$ sudo dbus-launch /usr/lib/synce-core/dccm |/|I could go with this (even if I don't know whether odccm is launched well). But when I finally launch the /synce-kpm/ GUI, my windows CE device (a GPS device) doesn't appear and the tabs are all greyed. (cf picture: https://i.imgur.com/UlYCSh6l.png) Thanks a lot in advance |/||/|| _______________________________________________ SynCE-Users mailing list Syn...@li...<mailto:Syn...@li...> https://lists.sourceforge.net/lists/listinfo/synce-users |
|
From: gilga g. <gi...@ho...> - 2019-04-19 07:08:28
|
Hi I' m on Arch Linux. I've installed synce-core (https://aur.archlinux.org/packages/synce-core/), synce-kde, and sync-synce-sync-engine as described in the Arch linux wiki for SynCE (https://wiki.archlinux.org/index.php/SynCE). My problem is at the first step, which is launching the `odccm` program. Firstly, it's `dccm`, not `odccm` which apparently must be launched: $ sudo pacman -Ql synce-core | grep dccm synce-core /etc/dbus-1/system.d/org.synce.dccm.conf synce-core /usr/lib/synce-core/dccm synce-core /usr/share/dbus-1/system-services/org.synce.dccm.service Then, I'm trying to launch dccm: $ sudo /usr/lib/synce-core/dccm --log-level=6 But it returns, with no errors or confirmations about launching. I've tried also launching it with DBus but with the same result: $ sudo dbus-launch /usr/lib/synce-core/dccm I could go with this (even if I don't know whether odccm is launched well). But when I finally launch the synce-kpm GUI, my windows CE device (a GPS device) doesn't appear and the tabs are all greyed. (cf picture: https://i.imgur.com/UlYCSh6l.png) Thanks a lot in advance |
|
From: Gustavo - <ghr...@gm...> - 2015-08-06 13:18:14
|
Hi Hunter I am finally coming up with a solution to sync my Motorola MC3x90 [ 3090 / 3190 / 32N0 ] Mobile Computer with my app on Ubuntu 14.04. Currently exists a way to install Synce from binary. In /etc/apt/sources.list add these lines: deb http://ppa.launchpad.net/synce/ppa/ubuntu trusty main deb-src http://ppa.launchpad.net/synce/ppa/ubuntu trusty main Execute: $ sudo apt-get update $ sudo apt-get install synce-sync-engine I connect the devices via ppp, and grant IP addresses using the options file: /etc/ppp/options.ttyUSB0 10.1.20.1:10.1.20.2 /etc/ppp/options.ttyUSB1 10.1.20.3:10.1.20.4 It requires making some simple changes to behave as one wishes. Anything at your disposal. |
|
From: Christian S. <sc...@sc...> - 2015-08-06 13:03:05
|
unsuscribe |
|
From: Gustavo - <ghr...@gm...> - 2015-08-06 12:50:51
|
Hi all, I downloaded libsynce, librapi2, librra and vdccm source, and tried to compile according to the howto at http://archive.is/www.synce.org "Building SynCE with Windows Mobile 2005 support from Subversion" at http://archive.is/nAqJ8 "SynceInstallation/Source" at http://archive.is/AeBc5 However, ** librra ** is failing to make with some strange error for me. $ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig/ $ ./configure $ make ... make[2]: Leaving directory `/var/tmp/synce/librra-0.11/src' Making all in man make[2]: Entering directory `/var/tmp/synce/librra-0.11/man' make[2]: No se hace nada para `all'. make[2]: Leaving directory `/var/tmp/synce/librra-0.11/man' Making all in python make[2]: Entering directory `/var/tmp/synce/librra-0.11/python' pyrexc ./pyrra.pyx -I../lib -o ./pyrra.c /var/tmp/synce/librra-0.11/python/./pyrra.pyx:51:2: Syntax error in C variable declaration make[2]: *** [pyrra.c] Error 1 make[2]: Leaving directory `/var/tmp/synce/librra-0.11/python' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/synce/librra-0.11' make: *** [all] Error 2 Code section: ---------------------------------------------------------------------------- ctypedef enum RRA_SyncMgrTypeEvent: SYNCMGR_TYPE_EVENT_UNCHANGED SYNCMGR_TYPE_EVENT_CHANGED SYNCMGR_TYPE_EVENT_DELETED ctypedef struct _RRA_Uint32Vector: pass ## line 51 ## RRA_SyncMgr * rra_syncmgr_new() ---------------------------------------------------------------------------- File pyrra.pyx is attached. I've already searched a lot on Google and no response so far Someone knows how to fix this? Any help would be greatly appreciated! |
|
From: Gustavo - <ghr...@gm...> - 2015-08-05 21:00:18
|
Hi all, I downloaded libsynce, librapi2, librra and vdccm source, and tried to compile according to the howto at http://archive.is/www.synce.org "Building SynCE with Windows Mobile 2005 support from Subversion" at http://archive.is/nAqJ8 "SynceInstallation/Source" at http://archive.is/AeBc5 However, ** librra ** is failing to make with some strange error for me. $ export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig/ $ ./configure $ make ... make[2]: Leaving directory `/var/tmp/synce/librra-0.11/src' Making all in man make[2]: Entering directory `/var/tmp/synce/librra-0.11/man' make[2]: No se hace nada para `all'. make[2]: Leaving directory `/var/tmp/synce/librra-0.11/man' Making all in python make[2]: Entering directory `/var/tmp/synce/librra-0.11/python' pyrexc ./pyrra.pyx -I../lib -o ./pyrra.c /var/tmp/synce/librra-0.11/python/./pyrra.pyx:51:2: Syntax error in C variable declaration make[2]: *** [pyrra.c] Error 1 make[2]: Leaving directory `/var/tmp/synce/librra-0.11/python' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/synce/librra-0.11' make: *** [all] Error 2 Code section: ---------------------------------------------------------------------------- ctypedef enum RRA_SyncMgrTypeEvent: SYNCMGR_TYPE_EVENT_UNCHANGED SYNCMGR_TYPE_EVENT_CHANGED SYNCMGR_TYPE_EVENT_DELETED ctypedef struct _RRA_Uint32Vector: pass ## line 51 ## RRA_SyncMgr * rra_syncmgr_new() ---------------------------------------------------------------------------- File pyrra.pyx is attached. I've already searched a lot on Google and no response so far Someone knows how to fix this? Any help would be greatly appreciated! |
|
From: William H. K. <whu...@gm...> - 2015-06-30 01:09:44
|
Hello, I would like to get synce up and running on a more modern OS, and I was wondering if there were any plans to keep this project going. This appears to be my best option, though I am at a loss because the sourceforge source repositories appear to be gone. Please let me know if there currently exists a way to install Synce on a newer operating system from source. Thanks, Hunter |
|
From: Mark E. <ma...@mp...> - 2013-07-29 14:11:49
|
Yep, that's right. It's finished building now, so give it a go. On Mon, 2013-07-29 at 14:43 +0200, Andrea Vai wrote: > Il giorno lun, 29/07/2013 alle 13.31 +0100, Mark Ellis ha scritto: > > I've spotted one problem, and uploaded a new version of > > libopensync-plugin-python, the 32 version has built and is ready, the 64 > > bit version is still waiting, so if you're 32 bit you can run an upgrade > > and try it now. > I am on x64, so I think I will have to wait/try until apt-get upgrade > shows libopensync-plugin-python in its output... > > ...am I right? > Thanks... and sorry for the (stupid) question > > Andrea > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > SynCE-Users mailing list > Syn...@li... > https://lists.sourceforge.net/lists/listinfo/synce-users |
|
From: Andrea V. <and...@un...> - 2013-07-29 13:08:36
|
Il giorno lun, 29/07/2013 alle 13.31 +0100, Mark Ellis ha scritto: > I've spotted one problem, and uploaded a new version of > libopensync-plugin-python, the 32 version has built and is ready, the 64 > bit version is still waiting, so if you're 32 bit you can run an upgrade > and try it now. I am on x64, so I think I will have to wait/try until apt-get upgrade shows libopensync-plugin-python in its output... ...am I right? Thanks... and sorry for the (stupid) question Andrea |
|
From: Mark E. <ma...@mp...> - 2013-07-29 12:31:38
|
On Mon, 2013-07-29 at 09:10 +0200, Andrea Vai wrote: > Il giorno ven, 26/07/2013 alle 10.12 +0100, Mark Ellis ha scritto: > > I mean the synce partnership and the opensync partnership always have to > > be in the same state, > Thank you for the explanation. > > > so yes you need to delete the synce partnership > > like that, but also > > > > osynctool --delgroup JJ2Evo > > > > Then recreate both. > > > > When you then try a sync, if it doesn't work, as well as the output of > > osynctool, send the file ~/.synce/sync-engine.log > So I have successfully delete and recreated both the synce and opensync partnerships, enabled sync for > todo items only, and synced with no items present at both sides. No > errors (and no items were respawned). > > To keep trace of successive steps, I issued the command osynctool --sync > JJ2Evo 2>&1 |tee Log_`date +"%Y%m%d_%H%M"`.txt and attach the logs. > Numbers at the beginning of the following lines identify (the time of) each log: > > Added element to PDA (Item title is "PDA1") > 0857 sync --> PDA1 got copied on Evo, but the output get an error: *** glibc detected *** osplugin: corrupted double-linked list: 0x0000000001ca8f00 *** > and I have to press ctrl+c to terminate the command. > Not sure what is causing this, we might have to eliminate some possibilities. > I tried other times to add/remove/modify and sync, and the error doesn't always appear, but I think it's better to have it never appear, isn't it? > > Attached: output log + sync-engine.log > I've spotted one problem, and uploaded a new version of libopensync-plugin-python, the 32 version has built and is ready, the 64 bit version is still waiting, so if you're 32 bit you can run an upgrade and try it now. Mark |
|
From: Andrea V. <and...@un...> - 2013-07-29 07:10:16
|
Il giorno ven, 26/07/2013 alle 10.12 +0100, Mark Ellis ha scritto: > I mean the synce partnership and the opensync partnership always have to > be in the same state, Thank you for the explanation. > so yes you need to delete the synce partnership > like that, but also > > osynctool --delgroup JJ2Evo > > Then recreate both. > > When you then try a sync, if it doesn't work, as well as the output of > osynctool, send the file ~/.synce/sync-engine.log So I have successfully delete and recreated both the synce and opensync partnerships, enabled sync for todo items only, and synced with no items present at both sides. No errors (and no items were respawned). To keep trace of successive steps, I issued the command osynctool --sync JJ2Evo 2>&1 |tee Log_`date +"%Y%m%d_%H%M"`.txt and attach the logs. Numbers at the beginning of the following lines identify (the time of) each log: Added element to PDA (Item title is "PDA1") 0857 sync --> PDA1 got copied on Evo, but the output get an error: *** glibc detected *** osplugin: corrupted double-linked list: 0x0000000001ca8f00 *** and I have to press ctrl+c to terminate the command. I tried other times to add/remove/modify and sync, and the error doesn't always appear, but I think it's better to have it never appear, isn't it? Attached: output log + sync-engine.log Thanks again, Andrea > > > Mark > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ SynCE-Users mailing list Syn...@li... https://lists.sourceforge.net/lists/listinfo/synce-users |
|
From: Mark E. <ma...@mp...> - 2013-07-26 09:13:01
|
On Fri, 2013-07-26 at 10:43 +0200, Andrea Vai wrote: > Il giorno ven, 26/07/2013 alle 09.28 +0100, Mark Ellis ha scritto: > > We shouldn't be getting the schema errors anymore, unless there are half > > completed items stuck in there. Did you change OS20 to OS30 in that > > file ? > > Yes, I did: > > andrea@andrea-desktop:~$ grep XML .synce/syncengine.conf.xml > OpensyncXMLFormat specifies the type of format conversion to use > in AirSync/XML (Use this for debugging or with the > - OS30 uses OpenSync 0.3x XML schemas. Set this if you are > <OpensyncXMLFormat>OS30</OpensyncXMLFormat> > > Ok. > > > The important thing first is to get rid of the schema errors, so check > > the version in that sync-engine config file. After that we'll need to > > remove the partnerships and start again. > > Ok so you confirm me that the XML file is correct, and I can remove the > partnership(s)? The plural here is not so clear to me, but am I correct > if I assume that removing the partnerships means using > synce-delete-partnership, and removing the only one listed there? > I mean the synce partnership and the opensync partnership always have to be in the same state, so yes you need to delete the synce partnership like that, but also osynctool --delgroup JJ2Evo Then recreate both. When you then try a sync, if it doesn't work, as well as the output of osynctool, send the file ~/.synce/sync-engine.log Mark |
|
From: Andrea V. <and...@un...> - 2013-07-26 08:43:24
|
Il giorno ven, 26/07/2013 alle 09.28 +0100, Mark Ellis ha scritto: > We shouldn't be getting the schema errors anymore, unless there are half > completed items stuck in there. Did you change OS20 to OS30 in that > file ? Yes, I did: andrea@andrea-desktop:~$ grep XML .synce/syncengine.conf.xml OpensyncXMLFormat specifies the type of format conversion to use in AirSync/XML (Use this for debugging or with the - OS30 uses OpenSync 0.3x XML schemas. Set this if you are <OpensyncXMLFormat>OS30</OpensyncXMLFormat> > The important thing first is to get rid of the schema errors, so check > the version in that sync-engine config file. After that we'll need to > remove the partnerships and start again. Ok so you confirm me that the XML file is correct, and I can remove the partnership(s)? The plural here is not so clear to me, but am I correct if I assume that removing the partnerships means using synce-delete-partnership, and removing the only one listed there? Thanks again Andrea |
|
From: Mark E. <ma...@mp...> - 2013-07-26 08:29:01
|
On Fri, 2013-07-26 at 08:42 +0200, Andrea Vai wrote: > Hi, > Il giorno gio, 25/07/2013 alle 19.50 +0100, Mark Ellis ha scritto: > > In /usr/share/doc/synce-sync-engine is a file > > called syncengine.conf.xml.gz, copy it to ~/.synce, unpack it, find the > > line > > > > <!-- <OpensyncXMLFormat>OS20</OpensyncXMLFormat> --> > > > > change it to > > > > <OpensyncXMLFormat>OS30</OpensyncXMLFormat> > > > > If you know XML you know what we did > yes, I know, and I have did it and tried again. > We shouldn't be getting the schema errors anymore, unless there are half completed items stuck in there. Did you change OS20 to OS30 in that file ? > Now something more works, but still without syncing properly. But first > of all, I expect that if I trigger a sync after one has been completed, > without adding/modifying/deleting any item, the engine does not find > anything more to sync. But instead, it seems that it has some memory of > the items already synced, and it considers (and also duplicates part of) > them. > It's because it's slow syncing after a failure, and getting in a mess. > I am currently doing the syncs with only tasks enabled, because I don't > have any important data there and I can delete them for testing > purposes. Good idea. > But, as you can see from the logs, even if I delete all the > items, the next sync re-creates all of them, or part of them, or > duplicates one of them. > > I attach three logs, concerning three successive syncs, without doing > any change on the items between the syncs, done in this way: > > - delete all items from PDA and from Evo. Now PDA contains 0 items, Evo > contains 0 items. > - sync (-->Log1.txt). Now PDA contains 0 items, evo contains 22 items. > - sync (-->Log2.txt). Now PDA still contains 0 items, evo contains 24 > items. > - sync (-->Log3.txt). Now PDA still contains 0 items, evo contains 26 > items. > > Member 1 is the PDA. Member 2 is Evo. > > An italian phrase appear in the log: > Unable to create todo: Impossibile creare l'oggetto di calendario: L'ID > dell'oggetto esiste già > > that means: > > Unable to create todo: Unable to create the calendar object: The ID of > the object already exists > > that also seems strange to me, because it mixes todo and event objects > in the same line, and because event objects are disabled (if I am > correct): Todo and event are both calendar objects in vcal, and in many other implementations, including evolution, just different types. Some of the slow syncing and duplication that happens is due to the fact that we sort of have 2 partnerships with synce, the opensync partnership, and the windows partnership, whereas with evolution all the partnership information is with opensync. When it works its ok, but when it breaks it gets messy. The important thing first is to get rid of the schema errors, so check the version in that sync-engine config file. After that we'll need to remove the partnerships and start again. > > andrea@andrea-desktop:~$ osynctool --showobjtypes JJ2Evo > Member 1 Objtypes: > Objtype contact: Disabled > conversion config: > Objtype event: Disabled > conversion config: > Objtype todo: Enabled > conversion config: > Member 2 Objtypes: > Objtype contact: Disabled > conversion config: VCARD_EXTENSION=Evolution > conversion config: VCARD_EXTENSION=Evolution > Objtype event: Disabled > conversion config: > Objtype todo: Enabled > conversion config: > Objtype note: Enabled > conversion config: > Objtypes for the group: > event: Disabled > todo: Enabled > contact: Disabled > > > > It seems also strange to me that the sync output complains about > something related to calendar (event, vcal) items, that are disabled, as > pointed out above. > > Thanks a lot for your kind help, > Best regards > Andrea > |
|
From: Andrea V. <and...@un...> - 2013-07-26 06:42:55
|
Hi, Il giorno gio, 25/07/2013 alle 19.50 +0100, Mark Ellis ha scritto: > In /usr/share/doc/synce-sync-engine is a file > called syncengine.conf.xml.gz, copy it to ~/.synce, unpack it, find the > line > > <!-- <OpensyncXMLFormat>OS20</OpensyncXMLFormat> --> > > change it to > > <OpensyncXMLFormat>OS30</OpensyncXMLFormat> > > If you know XML you know what we did yes, I know, and I have did it and tried again. Now something more works, but still without syncing properly. But first of all, I expect that if I trigger a sync after one has been completed, without adding/modifying/deleting any item, the engine does not find anything more to sync. But instead, it seems that it has some memory of the items already synced, and it considers (and also duplicates part of) them. I am currently doing the syncs with only tasks enabled, because I don't have any important data there and I can delete them for testing purposes. But, as you can see from the logs, even if I delete all the items, the next sync re-creates all of them, or part of them, or duplicates one of them. I attach three logs, concerning three successive syncs, without doing any change on the items between the syncs, done in this way: - delete all items from PDA and from Evo. Now PDA contains 0 items, Evo contains 0 items. - sync (-->Log1.txt). Now PDA contains 0 items, evo contains 22 items. - sync (-->Log2.txt). Now PDA still contains 0 items, evo contains 24 items. - sync (-->Log3.txt). Now PDA still contains 0 items, evo contains 26 items. Member 1 is the PDA. Member 2 is Evo. An italian phrase appear in the log: Unable to create todo: Impossibile creare l'oggetto di calendario: L'ID dell'oggetto esiste già that means: Unable to create todo: Unable to create the calendar object: The ID of the object already exists that also seems strange to me, because it mixes todo and event objects in the same line, and because event objects are disabled (if I am correct): andrea@andrea-desktop:~$ osynctool --showobjtypes JJ2Evo Member 1 Objtypes: Objtype contact: Disabled conversion config: Objtype event: Disabled conversion config: Objtype todo: Enabled conversion config: Member 2 Objtypes: Objtype contact: Disabled conversion config: VCARD_EXTENSION=Evolution conversion config: VCARD_EXTENSION=Evolution Objtype event: Disabled conversion config: Objtype todo: Enabled conversion config: Objtype note: Enabled conversion config: Objtypes for the group: event: Disabled todo: Enabled contact: Disabled It seems also strange to me that the sync output complains about something related to calendar (event, vcal) items, that are disabled, as pointed out above. Thanks a lot for your kind help, Best regards Andrea |
|
From: Mark E. <ma...@mp...> - 2013-07-25 18:51:25
|
On Thu, 2013-07-25 at 18:03 +0200, Andrea Vai wrote: > I installed libopensync-plugin-file, disabled contacts and event sync > (they are many and I prefer to make some tries with only tasks enabled), > created a new task in evo, and it does not seem to sync it. > > Attached output of: osynctool --sync JJ2Evo 2>&1 |tee Log.txt > > What to try next? > Doh, it's me being daft. In /usr/share/doc/synce-sync-engine is a file called syncengine.conf.xml.gz, copy it to ~/.synce, unpack it, find the line <!-- <OpensyncXMLFormat>OS20</OpensyncXMLFormat> --> change it to <OpensyncXMLFormat>OS30</OpensyncXMLFormat> If you know XML you know what we did, if you don't, we're uncommenting the line. Note the change from OS20 to OS30. Then try again. The default is still to format for old opensync, I must do something about that. Mark |
|
From: Andrea V. <and...@un...> - 2013-07-25 16:03:20
|
I installed libopensync-plugin-file, disabled contacts and event sync (they are many and I prefer to make some tries with only tasks enabled), created a new task in evo, and it does not seem to sync it. Attached output of: osynctool --sync JJ2Evo 2>&1 |tee Log.txt What to try next? Thanks very much for your help, Andrea |
|
From: Mark E. <ma...@mp...> - 2013-07-25 15:18:25
|
On Thu, 2013-07-25 at 16:59 +0200, Andrea Vai wrote: > Hi Mark (and the list), > I followed all your instructions and it seems to me that all the > configuration was made properly. However, the command osynctool --sync > groupname seems to sync nothing. > > The output of the command has many lines like > Not sure why this is all coming out .... > E: Element 'Type': This element is not expected. Expected is ( Content > ). > E: Element 'LastName': This element is not expected. Expected is one > of ( Additional, Prefix, Suffix ). > E: Element 'Encoding': This element is not expected. > E: Element 'Type': This element is not expected. Expected is ( Content > ). > E: Element 'Type': This element is not expected. Expected is ( Content > ). > E: Element 'LastName': This element is not expected. Expected is one > of ( Additional, Prefix, Suffix ). > E: Element 'Encoding': This element is not expected. > E: Element 'Type': This element is not expected. Expected is ( Content > ). > E: Element 'Type': This element is not expected. Expected is ( Content > ). > E: Element 'Encoding': This element is not expected. > E: Element 'Type': This element is not expected. Expected is ( Content > ). > > then, at the end, it asks me if I want to do the sync (y/N), I say Y and > it says that the user decided to not do the sync. > It says that there are 0 items to sync for each item-type. > > May I provide you some log? > > The only strange things during configuration were in the output of > osynctool --discover and osynctool --addmember, complaining about > missing "plain format": > the plain format plugin is in package libopensync-plugin-file install that and see what happens. > osynctool --addmember JJ2Evo evo3-sync > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > > .............................. > > osynctool --discover JJ2Evo 2 > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > ERROR: Unable to find plain format > EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain > format > Discovered Objtypes: > contact > Format: vcard21 > conversion config: VCARD_EXTENSION=Evolution > Format: vcard30 > conversion config: VCARD_EXTENSION=Evolution > event > Format: vevent20 > todo > Format: vtodo20 > note > Format: vjournal > > > ........................................... > > So, at the moment I am stuck with my WM device containing data, and no > data on Evolution. > > Thank you, > Andrea > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > SynCE-Users mailing list > Syn...@li... > https://lists.sourceforge.net/lists/listinfo/synce-users |
|
From: Andrea V. <and...@un...> - 2013-07-25 14:59:55
|
Hi Mark (and the list), I followed all your instructions and it seems to me that all the configuration was made properly. However, the command osynctool --sync groupname seems to sync nothing. The output of the command has many lines like E: Element 'Type': This element is not expected. Expected is ( Content ). E: Element 'LastName': This element is not expected. Expected is one of ( Additional, Prefix, Suffix ). E: Element 'Encoding': This element is not expected. E: Element 'Type': This element is not expected. Expected is ( Content ). E: Element 'Type': This element is not expected. Expected is ( Content ). E: Element 'LastName': This element is not expected. Expected is one of ( Additional, Prefix, Suffix ). E: Element 'Encoding': This element is not expected. E: Element 'Type': This element is not expected. Expected is ( Content ). E: Element 'Type': This element is not expected. Expected is ( Content ). E: Element 'Encoding': This element is not expected. E: Element 'Type': This element is not expected. Expected is ( Content ). then, at the end, it asks me if I want to do the sync (y/N), I say Y and it says that the user decided to not do the sync. It says that there are 0 items to sync for each item-type. May I provide you some log? The only strange things during configuration were in the output of osynctool --discover and osynctool --addmember, complaining about missing "plain format": osynctool --addmember JJ2Evo evo3-sync ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format .............................. osynctool --discover JJ2Evo 2 ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format ERROR: Unable to find plain format EXIT_ERROR: osync_module_get_conversion_info: Unable to find plain format Discovered Objtypes: contact Format: vcard21 conversion config: VCARD_EXTENSION=Evolution Format: vcard30 conversion config: VCARD_EXTENSION=Evolution event Format: vevent20 todo Format: vtodo20 note Format: vjournal ........................................... So, at the moment I am stuck with my WM device containing data, and no data on Evolution. Thank you, Andrea |
|
From: Mark E. <ma...@mp...> - 2013-07-25 10:27:43
|
On Thu, 2013-07-25 at 11:18 +0100, Mark Ellis wrote: > On Thu, 2013-07-25 at 09:14 +0200, Andrea Vai wrote: > > Thank you Mark, it's all clear to me and I am going to make the job. > > Just a couple of questions: > > > > Il giorno mer, 24/07/2013 alle 16.28 +0100, Mark Ellis ha scritto: > > > I'm making a presumption that you're using a WM6 device, and you don't > > > sync the device with anything other than synce. If that's not correct, > > > we'll need to change the process a bit. > > > > > > Assuming all your info is correct in evolution, if you then delete your > > > partnership in synce with the device connected, because that's the only > > > partnership associated with the data on the device, it'll delete it all, > > > giving you a blank slate. With a WM5 device, you need to delete it > > > manually. > > OK I am using a WM5 device, and I sync it only with synce. > > I am going to manually delete (actually, move to a safe place) all of my > > data from Evolution and have them synced from the WM5 device. > > > > > and from the synce development PPA you need > > > > > > opensync-plugin-synce-3x > > ok I downloaded and installed the .deb manually. > > > > > synce-sync-engine > > it seems to me that I already have synce-sync-engine installed, v. > > 0.15.1-0ubuntu0~ppa1~precise2. I still have > > http://ppa.launchpad.net/synce/ppa/ubuntu in my software repo's, do I > > need to keep it or to delete it? > > Keep that repo, but you do need the newer version of synce-sync-engine > in the devel repo to match the new plugin. I've decided to do a new > release over the next few days, so what you need will appear in the > normal repo shortly, but by all means carry on with those packages > manually. > > I'm also very shortly, in a few minutes, going to upload some new > opensync packages, I broke the existing ones with a timeout change, so > make sure you run an upgrade on them soon, probably this afternoon. > Ignore this last comment about opensync, I hadn't broken the packages in precise, only in raring. > > > > Thanks, again, > > Andrea > > > > > > ------------------------------------------------------------------------------ > > See everything from the browser to the database with AppDynamics > > Get end-to-end visibility with application monitoring from AppDynamics > > Isolate bottlenecks and diagnose root cause in seconds. > > Start your free trial of AppDynamics Pro today! > > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > _______________________________________________ > > SynCE-Users mailing list > > Syn...@li... > > https://lists.sourceforge.net/lists/listinfo/synce-users > |
|
From: Mark E. <ma...@mp...> - 2013-07-25 10:18:52
|
On Thu, 2013-07-25 at 09:14 +0200, Andrea Vai wrote: > Thank you Mark, it's all clear to me and I am going to make the job. > Just a couple of questions: > > Il giorno mer, 24/07/2013 alle 16.28 +0100, Mark Ellis ha scritto: > > I'm making a presumption that you're using a WM6 device, and you don't > > sync the device with anything other than synce. If that's not correct, > > we'll need to change the process a bit. > > > > Assuming all your info is correct in evolution, if you then delete your > > partnership in synce with the device connected, because that's the only > > partnership associated with the data on the device, it'll delete it all, > > giving you a blank slate. With a WM5 device, you need to delete it > > manually. > OK I am using a WM5 device, and I sync it only with synce. > I am going to manually delete (actually, move to a safe place) all of my > data from Evolution and have them synced from the WM5 device. > > > and from the synce development PPA you need > > > > opensync-plugin-synce-3x > ok I downloaded and installed the .deb manually. > > > synce-sync-engine > it seems to me that I already have synce-sync-engine installed, v. > 0.15.1-0ubuntu0~ppa1~precise2. I still have > http://ppa.launchpad.net/synce/ppa/ubuntu in my software repo's, do I > need to keep it or to delete it? Keep that repo, but you do need the newer version of synce-sync-engine in the devel repo to match the new plugin. I've decided to do a new release over the next few days, so what you need will appear in the normal repo shortly, but by all means carry on with those packages manually. I'm also very shortly, in a few minutes, going to upload some new opensync packages, I broke the existing ones with a timeout change, so make sure you run an upgrade on them soon, probably this afternoon. > > Thanks, again, > Andrea > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > SynCE-Users mailing list > Syn...@li... > https://lists.sourceforge.net/lists/listinfo/synce-users |
|
From: Andrea V. <and...@un...> - 2013-07-25 07:45:13
|
Thank you Mark, it's all clear to me and I am going to make the job. Just a couple of questions: Il giorno mer, 24/07/2013 alle 16.28 +0100, Mark Ellis ha scritto: > I'm making a presumption that you're using a WM6 device, and you don't > sync the device with anything other than synce. If that's not correct, > we'll need to change the process a bit. > > Assuming all your info is correct in evolution, if you then delete your > partnership in synce with the device connected, because that's the only > partnership associated with the data on the device, it'll delete it all, > giving you a blank slate. With a WM5 device, you need to delete it > manually. OK I am using a WM5 device, and I sync it only with synce. I am going to manually delete (actually, move to a safe place) all of my data from Evolution and have them synced from the WM5 device. > and from the synce development PPA you need > > opensync-plugin-synce-3x ok I downloaded and installed the .deb manually. > synce-sync-engine it seems to me that I already have synce-sync-engine installed, v. 0.15.1-0ubuntu0~ppa1~precise2. I still have http://ppa.launchpad.net/synce/ppa/ubuntu in my software repo's, do I need to keep it or to delete it? Thanks, again, Andrea |
|
From: Mark E. <ma...@mp...> - 2013-07-24 15:28:52
|
On Wed, 2013-07-24 at 14:59 +0200, Andrea Vai wrote: > Il giorno mer, 24/07/2013 alle 12.56 +0100, Mark Ellis ha scritto: > > > > > I cant remember for certain, but I think it was something that changed > > > > in evolution around that time that messed around with opensync, > > > > something to do with how it reported changes. > > > > > > > > You could set up another sync group to confirm that, using evolution and > > > > file sync, but I'm reasonably confident I'm remembering it right. > > > I understand this, but I don't know exactly how to confirm that by using > > > a file sync group... > > > > you just set up a new msynctool sync group with > > evo2-sync and file-sync as members, sync it, and then see if any changes > > to the evolution data after that will sync without a slow sync. > > ok, so I did it but encountered a problem: > > Received an entry 20130530T075617Z-4883-1000-1-322@andrea-desktop with data of size 8 from member 2 (evo2-sync). Changetype ADDED > [many many many others...] > Received an entry 20130530T075616Z-4883-1000-1-163@andrea-desktop with data of size 8 from member 2 (evo2-sync). Changetype ADDED > Member 2 of type evo2-sync had an error while getting changes: Broken Pipe > Member 2 of type evo2-sync had an error while disconnecting: Broken Pipe > Member 1 of type file-sync just sent all changes > Member 1 of type file-sync just disconnected > All clients have disconnected > The sync failed: Unable to read from one of the members > Error while synchronizing: Unable to read from one of the members > > Obviously, I don't really need this problem to be solved. So, if you need me to do something else, to help you to understand anything, let me know. Otherwise, I would leave this problem unsolved and upgrade to the new opensync. > Yep, that looks familiar, I'd say there's no life left in that version. > > On the other > > hand, if you spot a data transfer problem, i'm more than happy to try to > > fix it. > > Ok, this makes me very happy, too :-) > > > If you do want to go this path, you'll also have to start your syncing > > from scratch, because the new opensync does it in a totally different > > way, but I can talk you through that. > > By saying "from scratch" do you mean that if I don't start with a side of the partnership empty of data, all the data would be duplicated? > Is there any other precaution I need to use in order to have it syncing correctly? > Yes, that's correct. We'll be using a new partnership, so it'll happily duplicate everything. I'm making a presumption that you're using a WM6 device, and you don't sync the device with anything other than synce. If that's not correct, we'll need to change the process a bit. Assuming all your info is correct in evolution, if you then delete your partnership in synce with the device connected, because that's the only partnership associated with the data on the device, it'll delete it all, giving you a blank slate. With a WM5 device, you need to delete it manually. Then create a new partnership with the device as normal. The opensync stuff has changed a bit. You use osynctool instead of msynctool. From the opensync PPA, install libopensync1 libopensync-plugin-evolution3 libopensync-plugin-vformat libopensync-plugin-xmlformat libopensync-plugin-python and from the synce development PPA you need opensync-plugin-synce-3x synce-sync-engine osynctool --addgroup groupname osynctool --addmember groupname evo3-sync osynctool --addmember groupname synce-sync osynctool --configure groupname 1 That last command gives you the default evo3-sync configuration, you should be ok just to save it and exit. synce-sync doesn't have a configuration. osynctool --discover groupname 1 osynctool --discover groupname 2 osynctool --sync groupname That's the general idea. |