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