Daniel CLEMENT | 20 Oct 11:47 2014
Picon

FYI: Microsoft drop Nokia Sync

Hello,

Just a word to confirm what could be suspected from a recent attempt I
made at using the OVI service (AKA Nokia Sync). Like many Nokia
customers, shortly after that, I have received an e-mail from Microsoft
which reads:

[Quote] We are planning to discontinue the Nokia Sync service on 5
December 2014. After 5 December 2014, you will not be able to access
your data through the Nokia Sync service. We strongly encourage you to
export and/or migrate your data from the service before this date.
[/Quote]

So... it looks like OVI support can safely be dropped from
Syncevolution :-(

Best regards,
--

-- 
Daniel CLEMENT
Patrick Ohly | 19 Oct 21:04 2014
Picon

Re: Configuring Activesync in SyncEvolution 1.4.99.4

On Sat, 2014-10-18 at 15:36 +0100, Graham Cobb wrote:
> On 15/09/14 16:19, Patrick Ohly wrote:
> > 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! :-)
> 
> The (new in this release, I think) checking for mixing shared/unshared
> properties is causing me some logical confusion.  Here is (the outline
> of) how I used to configure my Exchange server config:
> 
> 1) Remove the existing configurations
> 
> 2) syncevolution --configure --template none backend=eas-contacts
> database=Contacts username=my-account-name  <at> Exchange contacts
> 
> 3) syncevolution --configure --template none username=my-account-name
> password= printChanges=1 loglevel=4 target-config <at> Exchange
> 
> 4) syncevolution --configure sync=two-way uri=contacts loglevel=4
> target-config <at> Exchange contacts
> 
> The second step now gives the error:
> 
> [ERROR] per-peer (unshared) properties not allowed: username
> 
> If I remove the username, it gives the error:
> 
(Continue reading)

Patrick Ohly | 19 Oct 20:52 2014
Picon

Re: SyncEvolution 1.4.99.4

On Sat, 2014-10-18 at 14:32 +0100, Graham Cobb wrote:
> On 15/09/14 16:19, Patrick Ohly wrote:
> > 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! :-)
> 
> I am trying to update my various configs and check that everything works.
> 
> The first problem isn't really a bug because I know the Debian packaging
> is not a supported feature.  But when I tried to upgrade using "apt-get
> install syncevolution-activesync", apt-get would have been happy to
> install the new syncevolution-activesync without upgrading
> syncevolution-activesync-saucy and syncevolution-bundle as well.  Adding
> syncevolution-kde caused all four packages to be upgraded.
> 
> I think the dependency of syncevolution-activesync on
> "syncevolution-activesync-wheezy | syncevolution-activesync-saucy |
> syncevolution-activesync-trusty" should be versioned to require the same
> version.

I agree, this should be changed. Will do.

> I am also surprised that activesyncd-saucy hasn't been upgraded.  Is
> that because it has not changed?

Exactly.

--

-- 
Best Regards, Patrick Ohly

(Continue reading)

Gregor Horvath | 9 Oct 07:46 2014

Parse error

Hi,

I use SyncEvolution 1.2.2 on a N900 version in conjunction with a
Radicale server and Icedove clients on the Desktop.
It seems that syncevolution does not like some entries created from a
Debian Icedove Client.
I get the following error, although this snippet is validating fine
with http://severinghaus.org/projects/icv/

From the syncevolution log:

First ERROR encountered: error code from SyncEvolution fatal error
(local, status 10500):  <at> default/calendar5: parsing ical:
BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Synthesis AG//NONSGML SyncML
Engine V3.4.0.27//EN BEGIN:VTIMEZONE
TZID:Europe/Vienna
BEGIN:STANDARD
DTSTART:19671029T020000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19870329T030000
RRULE:FREQ=MONTHLY;INTERVAL=12;BYDAY=-1SU
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
(Continue reading)

Patrick Ohly | 7 Oct 21:08 2014
Picon

Re: GOA credentials not found

On Tue, 2014-10-07 at 09:28 -0700, Todd Wilson wrote:
> On Mon, Oct 6, 2014 at 11:56 PM, Patrick Ohly
<patrick.ohly@...> wrote:
> > > > Nevertheless, can you show the output of:
> > > >
> > > > syncevolution --print-config -q google
> > > > syncevolution --print-config -q target-config <at> google
> > >
> > > [I'm leaving off the blank options to save space and redacting a few
> > > id numbers; let me know if you need more]
> > >
> > > syncURL = local:// <at> google
> > > username = goa:account_...
> >
> > When I asked about "username=goa:..." in your "google" sync config", I
> > meant the "google" config. You said that only
> > google/peers/target-config/config.ini has username=goa:... set, but then
> > why does it show up here?
> >
> > Is it really unset in default/peers/google/config.ini?
> 
> Sorry, I was just looking in google/ and didn't think to look in default/:
> 
> $ cd ~/.config/syncevolution
> $ find . -name config.ini -print | xargs grep goa
> ./default/peers/google/config.ini:username = goa:account_...
> ./google/peers/target-config/config.ini:username = goa:account_...

Do you have an idea how it got there? I don't think previous
SyncEvolution versions worked with such a config.
(Continue reading)

Todd Wilson | 5 Oct 03:41 2014
Picon

GOA credentials not found

I may be overlooking something obvious here, but when using the latest 
version (1.4.99.4-1) on Ubuntu 14.04, my GOA credentials are not being found:

% syncevolution --sync refresh-from-local google
[ERROR] goa:account_nnnn: need username+password as credentials

The account number I'm redacting as "nnnn" does exist (I can see it with 
seahorse) and is authorized.

I've also tried deleting the account in seahorse and Online Accounts, 
starting over with a new account, and replacing the old account number in my 
google target-config with the new number, but I still get the same error.
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

Gmane