[SyncEvolution] Syncing to Memotoo w SyncEvolution using test version 1:2.0.0-6.fc37
Max Pyziur
pyz at brama.com
Sun Mar 5 14:05:36 UTC 2023
On Sun, 5 Mar 2023, Patrick Ohly wrote:
> Max Pyziur <pyz at brama.com> writes:
>
>> On Sun, 5 Mar 2023, Patrick Ohly wrote:
>>
>>> Max Pyziur <pyz at brama.com> writes:
>>>> Then I ran:
>>>> $> syncevolution --run --sync refresh-from-local memotoo
>>>>
>>>> and it does a full update, not just the new/modified records.
>>>>
>>>> I ran it a second time, and again, it does a full update of each
>>>> record.
>>>
>>> The second time, did you also use "--sync refresh-from-local"?
>>
>> Yes. And rather than just updating changed and new records, it sent a full
>> updated of both the calendar and the addressbook.
>
> That's what it is meant to do:
>
> $ syncevolution --sync ?
> --sync
> Requests a certain synchronization mode when initiating a sync:
>
> two-way
> only send/receive changes since last sync
> slow
> exchange all items
> refresh-from-remote
> discard all local items and replace with
> the items on the peer
> refresh-from-local
> discard all items on the peer and replace
> with the local items
> one-way-from-remote
> transmit changes from peer
> one-way-from-local
> transmit local changes
> local-cache-slow (server only)
> mirror remote data locally, transferring all data
> local-cache-incremental (server only)
> mirror remote data locally, transferring only changes;
> falls back to local-cache-slow automatically if necessary
> disabled (or none)
> synchronization disabled
>
> What you want is probably "one-way-from-local"?
This is the the outpu that appears on my screen:
~> syncevolution --run --sync one-way-from-local memotoo
[INFO] memo: inactive
[INFO] todo: inactive
[INFO] addressbook: starting normal sync from client (peer is server)
[INFO] calendar: starting normal sync from client (peer is server)
[INFO] creating complete data backup of datastore addressbook before sync
(enabled with dumpData and needed for printChanges)
Local data changes to be applied during synchronization:
*** addressbook ***
no changes
[INFO] creating complete data backup of datastore calendar before sync
(enabled with dumpData and needed for printChanges)
*** calendar ***
no changes
[INFO] addressbook: started
[INFO] calendar: started
[INFO] addressbook: normal sync done successfully
[INFO] calendar: normal sync done successfully
[INFO] creating complete data backup after sync (enabled with dumpData and
needed for printChanges)
Synchronization successful.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| one-way-from-local, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 1518 before sync, 1518 after it |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| one-way-from-local, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 852 before sync, 852 after it |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Sun Mar 5 09:01:23 2023, duration 0:12min |
| synchronization completed successfully |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
Data modified locally during synchronization:
*** addressbook ***
no changes
*** calendar ***
no changes
I'll modify one record to see if that affects the output; one moment.
W/out echoing the full screen output, you can see that one record was
touched and updated remotely.
[INFO] creating complete data backup of datastore calendar before sync
(enabled with dumpData and needed for printChanges)
*** calendar ***
no changes
[INFO] addressbook: sent 1/1
[INFO] addressbook: started
[INFO] calendar: started
[INFO] addressbook: normal sync done successfully
[INFO] calendar: normal sync done successfully
[INFO] creating complete data backup after sync (enabled with dumpData and
needed for printChanges)
Synchronization successful.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| one-way-from-local, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 1518 before sync, 1518 after it |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| one-way-from-local, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 852 before sync, 852 after it |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Sun Mar 5 09:03:25 2023, duration 0:13min |
| synchronization completed successfully |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
Data modified locally during synchronization:
*** addressbook ***
no changes
*** calendar ***
no changes
>> One problem now is that on my phone (Samsung A52) for each time update the
>> data via the MemoToo app, my addressbook data is correct, but my in my
>> calendar I have multiple instances of the same event; one for each time I
>> downloaded/updated my phone data from Memotoo.
>
> I don't have experience with that. If the calendar in Memotoo is
> correct, then it's a sync problem between the phone and Memotoo.
I just notified Memotoo; here is the message that I sent:
Greetings,
My addressbook and calendar data originates using Evolution on my core
computer using Evolution on Fedora 37 Linux.
I sync this data to Memotoo using Syncevolution, a multi-platform app.
For the last few months, Syncevolution had a major bug, one that is only
being corrected now.
I can send my data to Memotoo via syncevolution, and it appears correctly.
When I download my data to my phone (Samsung A52) using Memotoo Sync, the
default Samsung Calendar App shows multiple instances of the same event,
one for each time that I have updated my phone data.
Before the last iteration I installed Astrid Tasks and the latest update
of Memotoo Sync. Yet, the Samsun Calendar problem continues.
I thought that it could be a flaw of Samsung's Calendar App; but I
downloaded other Calendar apps from Google Play, and the same problem
occurs.
fyi,
Max Pyziur
pyz at brama.com
More information about the SyncEvolution
mailing list