Patrick Ohly | 15 Sep 17:19 2014
Picon

SyncEvolution 1.4.99.4

About 1.4.99.4
==============

This is the first release candidate for 1.5. No further changes are
planned except for fixing yet-to-be-discovered bugs - so find them
now! :-)

One focus in this release was on minimizing CPU consumption and disk
writes. The most common case, a two-way sync with no changes on either
side, no longer rewrites any meta data files. CPU consumption during
local sync was reduced to one third by exchanging messages via shared
memory instead of internal D-Bus. Redundant vCard decode/encode on the
sending side of PBAP and too agressive flushing of meta data during a
normal sync were removed. Altogether, sending 1000 contacts with photo
data in a refresh-from-server local sync takes only one sixth of the
CPU cycles compared to 1.3.99.3 (measured with valgrind's callgrind on
x86_64).

Based on community feedback and discussions, the terminology used in
SyncEvolution for configuration, local sync and database access was
revised. Some usability issues with setting up access to databases
were addressed. For Google, the obsolete SyncML config template was
removed and CalDAV/CardDAV were merged into a single "Google"
template.

Using Google Calendar/Contacts with OAuth2 authentication on a
headless server becomes a bit easier: it is possible to set up access
on one system with a GUI using either gSSO or GNOME Online Accounts,
then take the OAuth2 refresh token and use it in SyncEvolution on a
different system. See
(Continue reading)

Patrick Ohly | 4 Sep 17:20 2014
Picon

Re: Google CalDAV sync

On Sun, 2014-08-31 at 15:45 -0700, Todd Wilson wrote:

> On Fri, Jul 11, 2014 at 12:02 PM, Todd Wilson <twilson@...>
> wrote:

>         Thanks for this assessment. I appreciate the effort you've put
>         into getting me to this point. At least I can continue to use
>         SE to back-up my Zimbra calendar, which is what I've been
>         doing. And I'll see if I can run the database tests you asked
>         me for previously.
>          
>                 I reported all of that too Google engineers and was
>                 told that they are
>                 working on it. It might not be fixed next week, but it
>                 shouldn't take
>                 months or years either (as in the past). I'll keep an
>                 eye on this.

I checked again and the biggest issue on the server, not being able to
update individual events in a meeting series, is now fixed. The
remaining issues are lack of support for removing individual events from
such a series (one can only remove the entire series, removing some has
no effect) and all-day recurrence exceptions (RECURRENCE-ID gets mangled
- this case should be rare in practice).

The removal issue does not affect "refresh-from-local" syncs, only
two-way syncs where individual items were removed. So again, this should
not be an issue in practice.

Overall it seems that Google CaldDAV now can also be used in two-way
(Continue reading)

NeonJohn | 27 Aug 04:58 2014

SyncML update


SyncML is a commercial app for Android that comes as close to the old
Palm Pilot experience as I could ever expect.  I loathe commercial,
closed source software but in this case I had no choice.

So I bought it from the Play store.  As you may recall, it took quit a
bit of work to get my configuration running.  The guy behind the SyncML,
Beat Forster was incredibly helpful in getting his side to work.

My database are large and old, dating back to my first Palm Pilot days.
 Around 800 contacts and 1500 calendar events.  I keep my journal and my
expenses in the calendar so it grows rapidly.

SyncML got the job done but was sloooow.  Over 5 minutes for a sync.
Needless to say I didn't use the AutoSync feature!

An update became available and I let it install.  Everything came to a
halt.  The application seemed to lock up.  After rebooting the phone and
a few other things, I contacted Beat again.

Turns out the upgrade had a major improvement in that it now cleans up
the datasets as much as possible, eliminating duplicates, removing
illegal characters from fields and so on.  The problem was his first
algorithm was sloooow.

Beat suggested that start a sync and just let it run.  I did so.  5
hours later,the cleanup finished.  SyncEvolution had long since timed
out (default is 5 minutes) so the sync didn't complete.  The second time
through it took only about an hour but SyncEvolution had again timed out
so the actual sync didn't happen.
(Continue reading)

Johannes Meier | 23 Aug 16:58 2014
Picon

Can't get syncevolution to work with korganizer

Hi, I'm in the process of migrating an aging but perfectly working setup of iCal
/ Sony-Ericsson k610i / OSX 10.5  to korganizer / k610i / Ubuntu 14.03 LTS.
However, syncevolution does not seem to find akonadi.

==end goal==

In the end goal, I want to synchronize the logical union of 10 icalendar files
(managed by korganizer on Ubuntu, some 3000 events in total), one of which is
Google calendar, over Bluetooth with the phone. The phone is actually a
Sony-Ericsson k510i with a Feisar plugin
(http://www.feisar.com/isync_notes.php), but it works reliably with iCal just
like a k610i. There is no internet (and no direct sync with Google) on the
phone for several reasons.

==current goal==

As an intermediate milestone, I'd like to sync one of korganizer's icalendars
with the phone.

==steps done==

Ubuntu uses the dpkg sources provided by Canonical.

So far, I've successfully paired the phone with the computer, and I transferred 
its calendar data into evolution (unidirectionally) with the legacy sonyericsson
backend.

Things came crashing down when I tried to make syncevolution talk to akonadi, as
per https://syncevolution.org/wiki/kde-akonadi

(Continue reading)

Daniel CLEMENT | 19 Aug 08:28 2014
Picon

Trying to replace Funambol with OVI

Hello list members,

As of August the Funambol client ceased working on my phone (Nokia E72)
(Syncevolution is OK). I guess Funambol are dropping Symbian support and
I was looking for a substitute.

Nokia OVI works fine on the phone, but it gives me an error in
Syncevolution (1.4.1 Debian):

[INFO] SoupTransport Failure:
https://sync.ovi.com/services/syncml?s=24ba5a5069604888b8e05bf3eae5c8ec&srv_id=001 via
libsoup: Gone

then it times out.

Can that be solved, or has OVI become incompatible?

I'd prefer OVI over others because it has schedule capability on the
phone (like Funambol had, and unlike other manually-setup syncs).

TIA - best regards,
--

-- 
Daniel CLEMENT
Patrick Ohly | 18 Aug 15:50 2014
Picon

Re: Memotoo note syncing using iCalendar 2.0

On Mon, 2014-08-04 at 11:24 +0200, Thomas Pequet wrote:
> Ok I think it is OK now the modification will be get.
> Is it OK now ?
> If not send me again the link of logs

Sorry for the late reply, I was on vacation. No, it's still broken:

https://nightly.syncevolution.org/2014-08-18-01-43_testing-amd64_memotoo/testing-amd64/39-memotoo/Client_Sync_eds_memo_testUpdate.log.html

--

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
Patrick Ohly | 18 Aug 15:47 2014
Picon

Re: Setup of SyncML to WebDAV synchronization bridge: Problem with SSLVerifyServer switch in configuration command

Hello!

To summarize the thread from earlier this year, there were three
problems with using SabreDAV:
     1. configuring with SSL verification turned off
     2. actually finding the right URL for the address book collection
     3. creating events (possibly related to not using the right URL)

On Mon, 2014-08-18 at 15:02 +0200, Helge Kraak wrote:
> #######
> 
> 
> When I apply as third command (no addressbook at the end of the
> command)
> syncevolution --configure SSLVerifyServer=False
> --template SyncEvolution_Client --sync-property
> remoteDeviceId=ST23K3J5I4JX username=admin
> password=admin --source-property addressbook/uri=addressbook
>  sync=two-way Palm-TH55 <at> webdav 
> 
> IT RETURNS
> 
> 
> [INFO] addressbook: okay
> [INFO] calendar: looking for databases...
> [INFO] calendar: backend failed: error code from SyncEvolution
> authorization failed (remote, status 401): calendar: syncURL not
> configured and username admin does not contain a domain
> [INFO] memo: looking for databases...
> [INFO] memo: backend failed: error code from SyncEvolution
(Continue reading)

Balakrishna, Sandesh | 18 Aug 11:53 2014

API specification

Hi,

 

I am new to SyncEvolution. I am trying to make simple application which uses syncevolution for synchronizing all contacts.

 

But I could not find any API specification, for using syncevolution. Could you please help me in finding API specification.

 

I tried with test code available at syncevolution-1.4\syncevolution-1.4\test but I could not find API of syncevolution.

 

Please help me.

 

Thanks and Regards

Sandesh,

Ph: 9164682461

 

_______________________________________________
SyncEvolution mailing list
SyncEvolution@...
https://lists.syncevolution.org/mailman/listinfo/syncevolution
NeonJohn | 29 Jul 14:32 2014

Best way to start the server


Hi all,

I have SyncEvolution and my DroidX happily chatting with each other but
now I have another question.  How to start the server automatically at
boot time.

I made an /etc/rc.d script that started the server just fine but it
starts the server in the root context.  I found that out by watching
SyncML on my Droid delete everything because, of course, there are no
Evolution databases for root.

I tried starting it using Gnome's start-up tasks options.  That also
started the server but it could not access access tasks nor notes
(access denied).

So now I start it manually after reboot with

nohup sudo syncevo-http-server -d http://localhost:9000/syncevolution &

Which works perfectly but requires me to remember to do it each time I boot.

Any suggestions on how to automate this?

Thanks,
John

--

-- 
John DeArmond
Tellico Plains, Occupied TN
http://www.fluxeon.com      <-- THE source for induction heaters
http://www.neon-john.com    <-- email from here
http://www.johndearmond.com <-- Best damned Blog on the net
PGP key: wwwkeys.pgp.net: BCB68D77
Stefanie Dargel | 29 Jul 13:54 2014
Picon

MS Exchange and KDE synchronization: Colleague's calendar?

Hi,

 

I tried the MS Exchange and KDE synchronization as described in the wiki. It works with my calendar, but I would like to see my colleague's in KDE kmail as well. Is there any way to do that? I tried to use my colleague's email address as user-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org in the wiki and my username and password for "workdomain\username". But that gave me my calendar once again.

 

Thank you for any help or hints!

 

Stefanie

(I'm not subscribed to this list, please keep me in cc)

_______________________________________________
SyncEvolution mailing list
SyncEvolution@...
https://lists.syncevolution.org/mailman/listinfo/syncevolution
Patrick Ohly | 28 Jul 10:43 2014
Picon

Memotoo note syncing using iCalendar 2.0

Hello Thomas!

I am currently testing the following change in SyncEvolution:

commit 662aab0823905d56edf812cf5bf2464379fdfcaf
Author: Patrick Ohly <patrick.ohly@...>
Date:   Wed Jul 23 14:07:13 2014 +0200

    EDS: memo syncing as iCalendar 2.0 (FDO #52714)

    When syncing memos with a peer which also supports iCalendar 2.0 as
    data format, the engine will now pick iCalendar 2.0 instead of
    converting to/from plain text. The advantage is that some additional
    properties like start date and categories can also be synchronized.

    The code is a lot simpler, too, because the EDS specific iCalendar 2.0
    <-> text conversion code can be removed.

With Memotoo that only works partially. Adding a new note on the server
using iCalendar 2.0 as format works. Updating it fails: the server seems
to ignore the new data.

I also noticed that the server sends broken CtCap if (and only if!) the
client mentions iCalendar 2.0. Memotoo then lists
<Rx-Pref><CTType>text/calendar</CTType> and
<Rx><CTType>text/plain</CTType> but then describes some unrelated
<CTCap><CTType>text/x-vnote</CTType>

Here's the sync where a note gets updated:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log.html
First message sent by client:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log_trm001_001_outgoing.xml
Broken CtCap from server:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log_trm001_002_incoming.xml
Update sent by client:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.update.client.A/syncevolution-log_trm002_003_outgoing.xml

This is what a second client then later gets:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log.html
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log_trm003_006_incoming.xml

For reference, this works correctly when the client only claims to
support plain text:
http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-4-99-3/2014-07-22-07-29_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.update.client.A/syncevolution-log.html
http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-4-99-3/2014-07-22-07-29_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.update.client.A/syncevolution-log_trm001_001_outgoing.xml
http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-4-99-3/2014-07-22-07-29_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.update.client.A/syncevolution-log_trm001_002_incoming.xml

http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-4-99-3/2014-07-22-07-29_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log.html

--

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.

Gmane