Skip to content

{ Category Archives } Announcement

SyncEvolution 1.3.99.3 released

So far the development cycle for SyncEvolution 1.4 mostly focused on implementing the “PIM Manager” D-Bus API for IVI use cases [1]. The 1.3.99.3 pre-release starts to include more features and bug fixes again for syncing. For example, several ActiveSync improvements from Graham Cobb were included.

The remaining goal for 1.4, besides more testing of course, is to work out how to support Google CalDAV and CardDAV. I am in discussion with Google to get SyncEvolution whitelisted for use with these APIs – fingers crossed…

Upgrading from release 1.2.x

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):
syncevolution –configure \
syncFormat=text/x-vcard \
mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:
syncevolution –configure \
enableRefreshSync=TRUE \
funambol

Upgrading from releases before 1.2

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Changes 1.3.2 -> 1.3.99.3

  • PIM Manager: add ReplaceSearch, always allow it

    The new ReplaceSearch is more flexible than RefineSearch. It can
    handle both tightening the search and relaxing it. The downside of it
    is the more expensive implementation (must check all contacts again,
    then find minimal set of change signals to update view).

    Previously, a search which had no filter set at all at the begining
    could not be refined. This limitation of the implementation gets
    removed by always using a FilteredView, even if the initial filter is
    empty.

  • PIM Manager: introduce CreateConfig()

    That SetPeer() allows modifying and creating a config leads to race
    conditions when multiple clients want to create a config. The new
    CreateConfig() avoids that by atomically checking that a config does
    not exist yet and creating it.

    SetPeer() is still available for backwards compatibility. It continues
    to be used for modifying an existing config in TestContacts.testSync
    to check the effect of the logging settings.

  • PIM Manager: fix double entries in filtered search with limit

    Stressing the FilteredView by using it in tests originally written
    for the FullView showed that the filling up a view may have
    used data while it was inconsistent internally, leading to
    contacts being present multiple times.

  • PIM Manager and sync: support location = GEO property (FDO #60373)

    Exposed as “location” -> (lat, long) in the D-Bus bindings.
    Reading, writing and updating are supported.

  • PIM Manager: support groups = CATEGORIES (FDO #60380)

    Allow reading and writing of groups (folks terminology), aka
    CATEGORIES in vCard.

  • PIM Manager: intelligent phone search in EDS (part of FDO #59571)

    If phone number search is enabled in EDS, then the direct search in
    EDS now uses the more accurate
    E_BOOK_QUERY_EQUALS_NATIONAL_PHONE_NUMBER comparison, with the E164
    formatted caller ID as value to compare against. This gives
    semantically correct results. The previous solution (now the
    fallback) had to use substring searches, which did not match if the
    contact’s phone number was not formatted according to E164 and
    which may have matched the wrong contacts if the trailing numbers
    are the same.

  • PIM Manager : use pre-computed normalized phone numbers from EDS (part of FDO #59571)

    When available, the pre-computed E164 number from EDS will be used
    instead of doing one libphonebook parser run for each telephone
    number while reading. Benchmarking showed that this parsing was the
    number one hotspot, so this is a considerable improvement.

  • PIM Manager: fix error messages

    Ensure and check that no unnecessary ERROR messages are printed.
    libfolks was used slightly incorrectly, leading to several
    harmless error messages (glib asserts). libphonenumber printed
    its error messages to stdout.

  • PIM Manager: fix memory leaks during writing of contacts

    Constructing the GValues created additional references instead
    of taking over ownership as intended.

  • D-Bus server: fix read-after-free bug when using syslog

    openlog() expects the string to remain valid. Must ensure that in
    LoggerSyslog by making a copy. Found with valgrind.

  • PIM Manager: make implementation of some of the D-Bus methods thread-safe

    The goal is to make it easier to extend syncevo-dbus-server
    with other IPC mechanisms, which then can call the native C++
    code directly.

    That code was not prepared to handle calls in threads other than the
    main one. Now this is checked when entering the methods and work is
    shifted to the main thread if necessary. In the meantime the calling
    thread waits for completion.

  • PIM Manager: check responsiveness (part of FDO #60851)

    Enhanced the testActive test so that it can detect when the D-Bus
    server stops responding for too long. One major reason for that was
    event processing in folks, which got improved as part of
    https://bugzilla.gnome.org/show_bug.cgi?id=694385

  • PIM Manager: adapt to gee 0.8

    Changed the code to compile with gee 0.8, as used by folks 0.9.x.
    Older versions of folks are no longer supported.

  • PBAP: support Bluez 5

    The new Bluez 5 API is the third supported API for doing PBAP
    transfers. It gets checked first, then the PBAB backend falls back to
    new-style obexd (file based, similar to Bluez 5, but not quite the
    same) and finally old-style obexd (data transfer via D-Bus).

    In contrast to previous APIs, Bluez 5 does not report the reason for a
    failed PBAP transfer. SyncEvolution then throws a generic “transfer
    failed” error with “reason unknown” as message.

  • command line: recover from slow sync with new sync modes

    The error message for an unexpected slow sync still mentioned
    the old and obsolete “refresh-from-client/server” sync modes.
    Better mention “refresh-from-local/remote”.

  • CalDAV: more workarounds for Google CalDAV + unique IDs

    Google became even more strict about checking REV. Tests which
    reused a UID after deleting the original item started to fail sometime
    since middle of December 2012.

  • CalDAV: work around Google server regression (undeclared namespace prefix in XML)

    Google CalDAV for a while (December 2012 till January 2013) sent
    invalid XML back when asked to include CardDAV properties in a
    PROPFIND. This got rejected in the XML parser, which prevents
    syncing calendar data:

    Neon error code 1: XML parse error at line 55: undeclared namespace prefix

    In the meantime Google fixed the issue in response to a bug report
    via email. But the workaround, only asking for the properties which
    are really needed, still makes sense and thus is kept.

  • WebDAV: don’t send Basic Auth via http proactively (FDO #57248)

    Sending basic authentication headers via http is insecure. Only do
    it proactively when the connection is encrypted and thus protects
    the information or when the server explicitly asks for it.

  • Nokia: always add TYPE=INTERNET to EMAIL (FDO #61784)

    Without the explicit TYPE=INTERNET, email addresses sent to a Nokia
    e51 were not shown by the phone and even got lost eventually (when
    syncing back).

    This commit ensures that the type is set for all emails sent to any
    Nokia phone, because there may be other phones which need it and
    phones which don’t, shouldn’t mind. This was spot-checked with a N97
    mini, which works fine with and without the INTERNET type.

    This behavior can be disabled again for specific Nokia phones by
    adding a remote rule which sets the addInternetEmail session variable
    to FALSE again.

    Non-Nokia phones can enable the feature in a similar way, by setting
    the variable to TRUE.

  • SyncML: config option for broken peers

    Some peers have problems with meta data (CtCap, old Nokia phones)
    and the sync mode extensions required for advertising the restart
    capability (Oracle Beehive). The default in SyncEvolution is to
    advertise the capability, so manual configuration is necessary when
    working with a peer that fails in that mode.

    Because the problem occurs when SyncEvolution contacts the peers
    before it gets the device information from the peer, dynamic rules
    based on the peer identifiers cannot be used. Instead the local config
    must already disable these extra features in advance.

    The “SyncMLVersion” property gets extended for this. Instead of just
    “SyncMLVersion = 1.0″ (as before) it now becomes possible to say
    “SyncMLVersion = 1.0, noctcap, norestart”.

    “noctcap” disables sending CtCap. “norestart” disables the sync mode
    extensions and thus doing multiple sync cycles in the same session
    (used between SyncEvolution instances in some cases to get client and
    server into sync in one session).

    Both keywords are case-insensitive. There’s no error checking for
    typos, so beware!

    The “SyncMLVersion” property was chosen because it was already in use
    for configuring SyncML compatibility aspects and adding a new property
    would have been harder.

  • ActiveSync: added support for specifying folder names

    Previously, the database field was interpreted as a Collection ID. This adds
    logic to allow the database to be interpreted as a folder path. The logic is:

    1) If the database is an empty string, pass it through (this is the most
    common case as it is interpreted as “use the default folder for the
    source type”).
    2) If the database matches a Collection ID, use the ID (this is the same as
    the previous behaviour).
    3) If the database matches a folder path name, with an optional leading “/”,
    use the Collection ID for the matching folder.
    4) Otherwise, force a FolderSync to get the latest folder changes from the
    server and repeat steps 2 and 3
    5) If still no match, throw an error.

  • ActiveSync: support for listing databases

    Now –print-databases scans folders on the ActiveSync server and
    shows suitable folders for the ActiveSync backends instead of the
    previous, hard-coded help text.

    Invoking –print-databases can be used as a workaround for
    “SyncFolder error: Invalid synchronization key” errors. A better
    solution would be to do that automatically, but there was no time
    to implement that. See FDO #61869 and “[SyncEvolution] Activesync server losing state”
    http://thread.gmane.org/gmane.comp.mobile.syncevolution/4295

  • command line: show backend error when listing databases fails

    The command line swallowed errors thrown by the backend while listing
    databases. Instead it just showed “: backend failed”. The goal
    was to not distract users who accidentally access a non-functional backend.
    But the result is that operations like –configure or –print-databases could
    fail without giving the user any hint about the root cause of the issue.

    Now the error explanation in all its gory details is included.

    For example, not having activesyncd running leads to:
    INFO] eas_contact: backend failed: fetching folder list:
    GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
    org.meego.activesyncd was not provided by any .service files

    And running activesyncd without the necessary gconf keys shows up as:
    [INFO] eas_contact: backend failed: fetching folder list:
    GDBus.Error:org.meego.activesyncd.Error.AccountNotFound: Failed to find
    account [syncevolution@lists.intel.com]

  • Minor memory leak fix when using GDBus GIO: GDBusMethodInfo

    Also depends on a glib fix, see https://bugzilla.gnome.org/show_bug.cgi?id=695376

  • build fixes

    Avoid -lrt in make dependencies. Add missing pcre libs to
    syncevo-dbus-server. sqlite backend needs “#include ”
    (patch from Mario Kicherer).

1.3.99.1 => 1.3.99.2, 13.12.2012

  • PIM Manager searches for a caller ID (’phone’ search) in EDS
    directly while folks still starts up. No unification is done of
    these results. Intermediate results are replaced by the final ones
    from folks once those are ready.

  • PIM Manager: allow configuration of session directories (part of FDO #55921)

    Useful for moving the session directories to a temporary file system.
    They are essentially just useful for debugging when used as part of
    PIM Manager.

    • “logdir” – a directory in which directories are created with
      debug information about sync session
    • “maxsessions” – number of sessions that are allowed to exist
      after a sync (>= 0): 0 is special and means unlimited,
      1 for just the latest, etc.;
      old sessions are pruned heuristically (for example,
      keep sessions where something changed instead of
      some where nothing changed), so there is no hard
      guarantee that the last n sessions are present.
  • PIM Manager: write less data to disk (part of FDO #55921)

    Avoid writing config file changes to disk by enabling a new
    “ephemeral” mode for syncing via the PIM Manager. In this mode,
    config file changes are not flushed resp. discarded directly.
    This prevents writing to .ini files in ~/.config.

    The “synthesis” binfile client files are still written, but they get
    redirected into the session directory, which can (and should) be set
    to a temp file system and get deleted again quickly.

    Data dumps are turned off now in the configs created by the PIM
    Manager.

  • syncevo-dbus-server: use syslog instead of standard output by default

  • syncevo-dbus-server: command line options for controlling
    output and startup

    -d, –duration=seconds/’unlimited’ Shut down automatically
    when idle for this duration (default 300 seconds)
    -v, –verbosity=level Choose amount of output, 0 = no output,
    1 = errors, 2 = info, 3 = debug; default is 1.
    -o, –stdout Enable printing to stdout (result of operations)
    and stderr (errors/info/debug).
    -s, –no-syslog Disable printing to syslog.
    -p, –start-pim Activate the PIM Manager (= unified address book)
    immediately.

  • PIM Manager: store set of active address books persistently (FDO #56334)

    Together with storing the sort order persistently, this allows
    restarting the daemon and have it create the same unified address book
    again.

  • PIM Manager: remove colon from valid peer UID character set (FDO #56436)

    Using the UID as part of file names gets more problematic when
    allowing colons. Remove that character from the API and enforce
    the format in the source code.

  • PIM Manager API: introduce contact ID and use it for reading

    This makes it easier for a client to fully polulate its view with
    contact data. Previously it could happen that due to concurrent
    changes in the server, a client was returned data for the same
    contact multiple times. A client had to detect that and re-issue
    read requests.

  • PIM Manager API: optional ViewAgent.Quiescent() (FDO #56428)

    The callback is guaranteed to be invoked once when a search has
    finished sending its initial results, and not sooner. This makes it
    possible to check whether the current data contains some contact or
    not.

  • PIM Manager: limit number of search results (FDO #56142)

    A ‘limit’ search term with a number as parameter (formatted as string)
    can be added to a ‘phone’ or ‘any-contains’ search term to truncate the
    search results after a certain number of contacts. Example:
    Search([['any-contains', 'Joe'], ['limit', '10']])
    => return the first 10 Joes.

    As with any other search, the resulting view will be updated if
    contact data changes.

    The limit must not be changed in a RefineSearch(). A ‘limit’ term may
    (but doesn’t have to) be given. If it is given, its value must match
    the value set when creating the search. This limitation simplifies the
    implementation and its testing. The limitation could be removed if
    there is sufficient demand.

  • PIM Manager: fix refining a search

    Due to not mapping the local index in the view to the parent’s index,
    refining only worked in views where parent and child had the same
    index for the contacts in the search view.

  • PIM Manager: fix starting when done via search

    When the unified address book (= FullView) was not running yet at the
    time when a client wanted to search it, the unified address book was
    not started and thus the search never returned results.

  • PIM Manager: fix writing contact, support photo and notes

    folks and EDS do not support writing properties in parallel
    (https://bugzilla.gnome.org/show_bug.cgi?id=652659). Must serialize
    setting of modified properties.

  • PIM Manager: fix incorrect contact removal signals in filtered view

    The filtered view did not check whether a parent’s removed contact was
    really part of the view before sending a removal signal for it.

  • D-Bus: missing out parameters in D-Bus introspection XML (FDO #57292)

    The problem was in the C++ D-Bus binding. If the method that gets bound
    to D-Bus returns a value, that value was ignored in the signature:
    int foo() => no out parameter

    It works when the method was declared as having a retval:
    void foo (int &result) => integer out parameter

    This problem existed for both the libdbus and the GIO D-Bus
    bindings. In SyncEvolution it affected methods like GetVersions().

  • PIM Manager performance: pre-compute normalized telephone numbers

    Looking up by phone number spends most of its cycles in normalizing of
    the phone numbers in the unified address book. Instead of doing that
    work over and over again during the search, do it once while loading.

    Looking up a phone number only once does not gain from this change, it
    even gets slower (more memory intensive, less cache locality). Only
    searching multiple times becomes faster.

    Ultimately it would be best to store the normalized strings together
    with the telephone number inside EDS when the contact gets
    created. Work on that is in progress.

  • PIM Manager: improve performance of FullView sorting

    This fixes the hotspot during populating the FullView content: moving
    contacts around required copying IndividualData and thus copying
    complex C++ structs and strings. Storing pointers and moving those
    avoids that, with no lack of convenience thanks to boost::ptr_vector.

    Reordering also becomes faster, because the intermediate copy only
    needs to be of the pointers instead of the full content.

  • PIM Manager example: add benchmarking

    The new “checkpoints” split up the whole script run into pieces which
    are timed separately, with duration printed to stdout. In addition,
    tools like “perf” can be started for the duration of one phase.

  • EDS: fix creating databases

    –create-database was broken in combination with the final code in EDS
    3.6 because it passed NULL for the UID to e_source_new_with_uid(),
    which is considered an error by the implementation of that
    method. Must use e_source_new() if we don’t have a UID.

  • fixed some memory leaks, extended tests to cover new features and bugs

SyncEvolution 1.3.99.1, 25.10.2012

  • workarounds for warnings from g++ 4.5

  • engine: : local cache sync mode

    This patch introduces support for true one-way syncing (”caching”):
    the local datastore is meant to be an exact copy of the data on the
    remote side. The assumption is that no modifications are ever made
    locally outside of syncing. This is different from one-way sync modes,
    which allows local changes and only temporarily disables sending them
    to the remote side.

    Another goal of the new mode is to avoid data writes as much as
    possible.

    This new mode only works on the server side of a sync, where the
    engine has enough control over the data flow. Setting “sync” to:

    • “local-cache-incremental” will do an incremental sync (if possible)
      or a slow sync (otherwise). This is usually the right mode to use,
      and thus has “local-cache” as alias.
    • “local-cache-slow” will always do a slow sync. Useful for
      debugging or after (accidentally) making changes on the local side.
      An incremental sync will ignore such changes because they are not
      meant to happen, aren’t checked for to improve performance and
      thus will leave client and server out-of-sync!

    Both modes are recorded in the sync report of the local side. The
    target side is the client and records the normal “two-way” or “slow”
    sync modes.

    With the current SyncEvolution contact field list, first, middle and
    last name are used to find matches for contacts. For events, tasks
    and memos, time, summary and description are used.

  • HTTP proxy: useProxy=0 overrides http_* env variables

    Previously, if http_proxy was set, a proxy was used even if
    explicitly disabled. This prevented disabling the use of a proxy
    which only made sense in some cases, like accessing something
    that runs locally. Explicitly telling SyncEvolution to ignore
    http_proxy is necessary because it doesn’t support no_proxy.

  • WebDAV: auto-discovery fix

    With Google Contact + CardDAV the auto-discovery failed after
    finding the default address book, without reporting that result.

  • command line: implement –create/remove-database

    Creating a database is only possible with a chosen name. The UID is
    chosen automatically by the storage. Only implemented in the EDS
    backend.

  • file backend: sub-second mod time stamps

    Change tracking in the file backend used to be based on the
    modification time in seconds. When running many syncs quickly (as in
    testing), that can lead to changes not being detected when they happen
    within a second. Now the file backend also includes the sub-second part of the
    modification time stamp, if available.

    This change is relevant when upgrading SyncEvolution: most of the
    items will be considered “updated” once during the first sync after
    the upgrade (or a downgrade) because the revision strings get
    calculated differently.

  • D-Bus server: avoid progress outside of 0-100% range

    For example in the new TestLocalCache.testItemDelete100, the
    percentage value in the ProgressChanged signal become larger
    than 100 and then revert to 100 at the end of the sync.

    Seems the underlying calculation is faulty or simply inaccurate.
    This is not fixed. Instead the result is just clipped to the valid
    range.

  • code cleanup + improvements in testing

Source, Installation, Further information

http://syncevolution.org/blogs/pohly/2013/syncevolution-13993-released

Source code bundles for users are available in
http://downloads.syncevolution.org/syncevolution/sources
and the original source is the git repositories.

i386, lpia and amd64 binaries for Debian-based distributions are
available via the “unstable” syncevolution.org repository. Add the
following entry to your /apt/source.list:

Then install “syncevolution-evolution”, “syncevolution-kde” and/or
“syncevolution-activesync”.

These binaries include the “sync-ui” GTK GUI and were compiled for
Ubuntu 10.04 LTS (Lucid), except for “syncevolution-activesync” which
depends on libraries in Debian Squeeze, for example EDS 3.4.

Older distributions like Debian 4.0 (Etch) can no longer be supported
with precompiled binaries because of missing libraries, but the source
still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in
the download directories. In contrast
to 0.8.x archives, the 1.x .tar.gz archives have to be unpacked and the
content must be moved to /usr, because several files would not be found
otherwise.

After installation, follow the getting started steps. More specific HOWTOs can be found in the Wiki.

SyncEvolution 1.3.2 released

Minor (or major, if you depend on auto syncing) bug fix
release. Automatic syncing only ran once and notifications were not translated.

* auto sync: only synced once (FDO #56667)

A successful sync was incorrectly treated like a sync with a permanent
failure, which prevents further automatic syncing.

  • auto sync: notifications were not translated

    The code which enabled localization of messages created by the
    D-Bus server was incomplete. Localization was only enabled
    accidentally through KDE if the KDE platform modules was enabled
    during compilation and installed.

  • HTTP Proxy: useProxy=0 overrides http_* env variables

    Previously, if http_proxy was set, a proxy was used even if
    explicitly disabled. This prevented disabling the use of a proxy
    which only made sense in some cases, like accessing something
    that runs locally. Explicitly telling SyncEvolution to ignore
    http_proxy is necessary because it doesn’t support no_proxy.

  • minor changes in testing and autotools files (missing Boost search path
    in gdbus* libs might have caused compile problems)

Upgrading from release 1.2.x

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):
syncevolution –configure \
syncFormat=text/x-vcard \
mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:
syncevolution –configure \
enableRefreshSync=TRUE \
funambol

Upgrading from releases before 1.2

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information

Source code bundles for users are available in
http://downloads.syncevolution.org/syncevolution/sources
and the original source is in
the git repositories.

i386, lpia and amd64 binaries for Debian-based distributions are
available via the “stable” syncevolution.org repository. Add the
following entry to your /apt/source.list:

Then install “syncevolution-evolution”, “syncevolution-kde” and/or
“syncevolution-activesync”.

These binaries include the “sync-ui” GTK GUI and were compiled for
Ubuntu 8.04 LTS (Hardy), except for “syncevolution-activesync” which
depends on libraries in Debian Squeeze, for example EDS 3.4.

Older distributions like Debian 4.0 (Etch) can no longer be supported
with precompiled binaries because of missing libraries, but the source
still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in
the download directories. In contrast
to 0.8.x archives, the 1.x .tar.gz archives have to be unpacked and the
content must be moved to /usr, because several files would not be found
otherwise.

After installation, follow the getting started steps.

SyncEvolution 1.3.1 released

SyncEvolution 1.3.1 fixes some minor issues found after 1.3 was released.

* command line: fix output of –import for directories

The running count at the start of the line (#0, #1, …) was
not incremented when reading individual files from a directory.

  • Funambol: work around PHOTO TYPE=image/jpeg, part II

    The final version of the fix hadn’t made it into the source code.

  • vCalendar 1.0 + tasks: DUE date could be shifted by a day (FDO #55238)

    Because of incomplete support for time conversion, the due date
    could get mixed up when phone and PC were set to something other
    than UTC. Reported and fixed by Peter Jan.

  • syncevolution.org: syncevolution-evolution had incorrect dependencies

    Installation on older Linux distros was not possible because the ebook/ecal
    package dependencies were named incorrectly, for example libebook-1.2-10
    instead of libebook1.2-10. Only more recent packages have the extra
    dash, for example libebook-1.2-12. Reported by Mariusz Sokolowski.

  • GTK-3 UI: fixed compile problem

    The GTK-3 UI depends on a class from gio-unix-2.0 and failed to
    compile on Fedora Core 16 because the configure checks for that lib
    (and thus the compiler flags) were missing. Reported by Peter
    Robinson.

  • Curl: allow using it in the D-Bus server

    In the past, using curl as HTTP transport in the syncevo-dbus-server
    was prevented, leading to “unsupported transport type is specified in
    the configuration”. The reason was that using curl would block the
    server and make it unresponsive on D-Bus.

    This reason has gone away, because now the HTTP traffic happens in a
    separate process. Thus now it is allowed to use curl in the
    syncevo-dbus-server.

  • fix for false negative in syncevo-dbus-server testing

Upgrading from release 1.2.x

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):
syncevolution –configure \
syncFormat=text/x-vcard \
mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:
syncevolution –configure \
enableRefreshSync=TRUE \
funambol

Upgrading from releases before 1.2

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information

Source code bundles for users are available in
http://downloads.syncevolution.org/syncevolution/sources
and the original source is in
the git repositories.

i386, lpia and amd64 binaries for Debian-based distributions are
available via the “stable” syncevolution.org repository. Add the
following entry to your /apt/source.list:

Then install “syncevolution-evolution”, “syncevolution-kde” and/or
“syncevolution-activesync”.

These binaries include the “sync-ui” GTK GUI and were compiled for
Ubuntu 8.04 LTS (Hardy), except for “syncevolution-activesync” which
depends on libraries in Debian Squeeze, for example EDS 3.4.

Older distributions like Debian 4.0 (Etch) can no longer be supported
with precompiled binaries because of missing libraries, but the source
still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in
the download directories. In contrast
to 0.8.x archives, the 1.x .tar.gz archives have to be unpacked and the
content must be moved to /usr, because several files would not be found
otherwise.

After installation, follow the getting started steps.

SyncEvolution 1.3 released

After almost three months of public beta testing the next major
version of SyncEvolution is ready for release. The pre-releases did
have the desired effect of flushing out bugs not found by nightly
testing alone. Thanks everyone for packaging, downloading and testing
them!

Project status

SyncEvolution synchronizes personal information management (PIM) data via various protocols (SyncML, CalDAV/CardDAV, ActiveSync). It syncs contacts, appointments, tasks and memos. It syncs to web services or to SyncML-capable phones via Bluetooth.

Binaries are available for Linux desktops (using GNOME Evolution, or KDE’s Akonadi), for MeeGo and for Maemo (Nokia N900, N9).

The project moved its bug tracking from bugs.meego.com to
bugs.freedesktop.org. All the old issues were migrated.
Please file new issues here:
http://bugs.freedesktop.org/enter_bug.cgi?product=SyncEvolution

The git repositories were also moved to freedesktop.org:
http://cgit.freedesktop.org/SyncEvolution/

SyncEvolution 1.3

New features are KDE/Akonadi and ActiveSync support, not only in the
source code but also in syncevolution.org binaries. ActiveSync is the
recommended way of synchronizing contacts with Google:
https://syncevolution.org/wiki/google-contacts-activesync

The D-Bus server and local sync were rewritten considerably, to make
the code cleaner and more robust. The CalDAV backend now also supports
tasks and memos. CalDAV and CardDAV can be used in combination with a
SyncML peer (”bridging SyncML and WebDAV”), thus allowing a device
which only supports SyncML to talk to a WebDAV service without any
intermediate storage.

1.3 contains bug fixes that were not backported to 1.2.x, so upgrading
is recommended. For example, SyncEvolution 1.3 is required for
Evolution 3.4, otherwise photos are not exported properly. Support for
Evolution >= 3.6 is in the source code, but not in syncevolution.org
binaries. Further workarounds for recent changes in Google CalDAV and
Funambol One Media were added.

Upgrading from release 1.2.x

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):
syncevolution –configure \
syncFormat=text/x-vcard \
mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:
syncevolution –configure \
enableRefreshSync=TRUE \
funambol

Upgrading from releases before 1.2

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Changes 1.2.2 -> 1.3

  • ActiveSync: updated to work with latest activesyncd and Google, package binaries

    Syncing Google contacts was added to the nightly testing. Syncing
    contacts and events with Exchange 2012 was already working. Setup
    instructions and known issues are described here:
    https://syncevolution.org/wiki/google-contacts-activesync

  • phone sync: delete<->delete conflict + phone calendar+todo sync (BMC #23744)

    When deleting an item on phone and locally, the next sync failed with
    ERROR messages about “object not found”. This has several reasons:

    • libsynthesis super data store attempts to read items
      which may or may not exist (triggers ERROR message)
    • it checks for 404 but Evolution backends only return a generic
      database error (causes sync to fail)
  • phone sync: get phone vendor and model from Device ID profile (BMC #736)

    In the past we have relied on the user-modifiable device name to be
    the fingerprint for matching a phone to a template which is unreliable.

    This release changes this in the cases where the phone supports the
    Device ID profile (DIP). If support for DIP is detected, then we
    extract the vendor and product ids and attempt to associate them
    with a product and vendor name by using a newly added lookup table.

    This lookup table has to be maintained manually and depends on
    contributions by users to cover more devices. See
    http://blixtra.org/blog/2011/09/22/syncevolution-needs-you-or-at-least-y…

  • vCalendar 1.0: fixed recurring all-day event support

    vCalendar 1.0 cannot represent all-day events. The workarounds for
    mapping iCalendar 2.0 all-day events into vCalendar 1.0 was
    incomplete, leading to effects like shifting EXDATEs and end
    times.

  • Funambol: ignore UID

    Funambol’s OneMedia sends UID, but not RECURRENCE-ID. That becomes a
    problem when multiple events of the same event series are added to a
    backend which follows the iCalendar 2.0 standard (CalDAV, EDS, KDE),
    because these events all look like the master event, and there can be
    only one of those.

    SyncEvolution now strips the UID from all events coming from any
    Funambol server (regardless of the version). If a future Funambol
    server release adds support for both UID and RECURRENCE-ID, then
    SyncEvolution will have to be updated to take advantage of the
    improved server. Because the RECURRENCE-ID is also getting
    stripped (despite not being set at the moment), SyncEvolution should
    continue to work as it does now even if the server changes.

    It would have been nice to limit this workaround to affected Funambol
    server versions, but an inquiry on the Funambol mailing list didn’t
    get a reply, therefore SyncEvolution is playing it safe and assumes
    that all future Funambol releases will have the same problem.

  • Funambol: work around PHOTO TYPE=image/jpeg

    A combination of Funambol Android and Funambol server recently led to
    the Funambol server sending PHOTO data with TYPE=image/jpeg. This is
    invalid and caused EDS to reject the photo (Vladimir Elisseev,
    “[SyncEvolution] issues with syncing photos”).

    Work around the problem by only keeping the part of the type after the
    last slash, if there is any. For image/jpeg and similar types that
    leads to the desired value and does not affect valid values, because
    those do not contain a slash
    (http://www.iana.org/assignments/media-types/image/index.html).

  • Funambol: avoid slow syncs in refresh from server

    libsynthesis has traditionally implemented “refresh-from-server” as
    “delete local data” plus “slow” sync. This is more compatible, because
    some servers (like Google) do not support “refresh-from-server”.

    But it has the downside that the server cannot know that the client
    won’t send any data, and Funambol’s OneMedia now only allows one slow
    sync before blocking the next one for a certain period of time. This is
    done to prevent excessive resource usage by badly behaving clients.

    To accomodate both kinds of servers, the new “enableRefreshSync”
    sync property can be set set to explicitly allow the usage of
    the “refresh-from-server” sync mode. It’s off by default. The Funambol
    template has it turned on, existing configs must be updated manually
    (see upgrading comments below).

  • Mobical (aka Everdroid): stopped testing memo syncing

    Memos used to work, but now only trigger an unspecific 400 error
    on the server side.

  • GTK-UI: accept service config with a username again (BMC#23106)

    Suppressing configs with empty username had undesired side effects:
    modifying configs for direct syncing with a device incorrectly
    triggered the same error message, without any means of entering
    a username. The faulty check was removed without replacement.

  • GTK-UI: added GTK 3 version of UI

    When GTK 3 is found during compilation, a GTK 3 version of the
    UI is built. The source code of both is different to avoid
    excessive use of ifdefs. At the moment, both versions offer
    the same features. In the long run, the GTK 3 version will
    replace the GTK 2 version.

  • command line: added refresh/one-way-from-local/remote (BMC #23537)

    The -from-client/server sync modes are confusing because the direction
    of the data exchange depends on which side acts as SyncML server or
    client.

    This release introduces new modes which use -from-local/remote
    instead. The statistics and messages also use these variants
    now. The old modes are still understood, but are declared as “not
    recommended” in the documentation.

  • command line: config and source names are optional (BMC #23783)

    The need to add “foo” and “bar” pseudo config and source names to the
    command line even when all parameters for the operation where
    explicitly specified on the command line was confusing.

    Now it is possible to invoke item operations without the config and
    source name. Names which refer to non-existent configs are still
    accepted, as in previous releases. Typos are handled better by
    producing a detailed error report which includes (as applicable):

    • config doesn’t exist
    • source doesn’t exist or not selected
    • backend property not set

    Because luids used to be positional arguments after and
    , a new –luids keyword is necessary to indicate that the
    ensuing parameters are luids and not and .

  • command line: introduced –print-databases, supported for CalDAV/CardDAV

    Listing databases is now a dedicated operation, instead of being done
    whenever syncevolution was invoked without parameters.

    Advantages:

    • can be combined with property assignments for backends
      which do not work without that additional information, for example
      CalDAV/CardDAV:
      syncevolution –print-databases \
      backend=[caldav|carddav] \
      syncURL=… \
      username=… \
      password=…
    • can be done for configured sources
  • command line: use both stdout and stderr

    Traditionally, the “syncevolution” command line tool mixed its
    INFO/ERROR/DEBUG messages into the normal stdout. This has the major
    drawback that error messages get lost during operations like
    syncevolution –export – @default addressbook | grep “John Doe”

    Now anything which is not the expected result of the operation is
    always sent to stderr. Obviously this includes ERROR messages. INFO
    and DEBUG are harder to decide. Because they usually convey meta
    information about the running operation, they are also sent to
    stderr. The output of running a sync goes to both stdout (summary)
    and stderr (progress).

  • command line: allow setting empty properties

    Due to the way how properties were handled internally, it wasn’t
    possible to explicitly set a property to its default value. Instead
    the property was unset. For example, explicitly setting database= was
    not possible.

    This is necessary for client-test and ActiveSync, because client-test
    needs to know that the testing is expected to run with the default
    databases (something which normally is avoided by overwriting empty
    database properties).

    Now the “is set” state is tracked explicitly in the config storage and
    command line property APIs. Unsetting a property via the command line
    could be implemented with an explicit command line option, but is not
    supported at the moment.

  • command line: fixed –export

    When exporting items into a file, the delimiter between items
    was missing.

  • command line + local sync: fixed erroneous “Comparison impossible” output.

    “Comparison impossible” was incorrectly printed after a successful
    comparison on the target side of local sync.

  • local sync: fix timeout with local sync with libdbus

    When using libdbus instead of GIO D-Bus (as done by syncevolution.org
    binaries and SyncEvolution on Maemo), local sync may have aborted
    after 25 seconds when syncing many items with a D-Bus timeout error:

    [ERROR] sending message to child failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible ca

    Reported by Toke Høiland-Jørgensen for Harmattan. Somehow not encountered
    elsewhere.

  • synccompare: shorter data dump of PHOTO

    A full comparison of the base64 PHOTO data can be very long.
    Now some key characteristics of the PHOTO data (number of
    characters in base64 encoding, number of bytes in decoded
    data, md5sum of decoded data) are printed instead.

    That way, unintended changes of the data (different encoding,
    different content) should still be found while testing and
    added/removed photos are nicely visible in synccompare diffs.

  • synccompare: fixed output for byte-identical duplicates

    If database dumps contained byte-identical duplicates, they
    were treated as a single item on the left side of a comparison.
    This caused erroneous “added” entries on the right side.

  • secure password storage: usage of GNOME Keyring vs. KDE KWallet configurable

    Automatically detecting KDE users is not possible at the
    moment. Instead KDE users have to manually set the new “keyring”
    global config property to “KDE” (case insensitive) if the
    SyncEvolution installation supports both, because GNOME Keyring is the
    default to avoid surprises for traditional users. If only KWallet
    support is enabled, then this is not necessary.

    “GNOME” and “true/false/1/0/yes/no” can also be set. This has the
    advantage that keyring usage can be enabled permanently for the
    command line in –daemon=no mode; normally keyrings are not used in
    that mode because accessing them can bring up UI dialogs.

    It also becomes possible to disable keyring usage in syncevo-dbus-server,
    something which couldn’t be done before.

    The –keyring command line option is still supported, as an alias for
    “[--sync-property] keyring=”. The default value for –keyring
    is true, to match the traditional behavior. In contrast to other sync
    properties, setting “keyring” does not require an explicit –run
    parameter. Again this is done to mirror traditional usage.

  • config: improved ‘maxlogdirs’ documentation

    The old explanation made it sound like nothing would get deleted by
    default (”If set, …”). That’s not correct, by default only 10
    sessions are kept.
    Also explain the behavior of deleting intermediate sessions first.

  • Evolution: always create databases (PTCOM-113)

    Always try to create address book or calendar database, because even
    if there is a source there’s no guarantee that the actual database
    was created already; the original logic for only setting this when
    explicitly requesting a new database therefore failed in some cases.

    This problem affected users who had never created anything locally
    and wanted to use SyncEvolution to migrate their data. Now that
    works without having to create dummy entries first.

  • Evolution contacts: changed default sync format to vCard 3.0

    vCard 3.0 is the better default because it has saner encoding
    rules and defines more properties, thus avoiding the need for
    non-standard extensions. However, Mobical has problems with
    the new default. See upgrade instructions below.

  • Evolution: added support for EDS 3.5.x

    When compiled against EDS 3.5.x or later, SyncEvolution now uses
    the backend code originally written for the EClient API introduced
    in EDS 3.2. That code was changed so that it works with the new
    include file rules and ESourceRegistry in EDS 3.5.x. Support
    for using the EClient API with EDS 3.4 was removed because maintaining
    three different flavors of the EDS backend code would be too much
    work and not gain much (just the possibility to test the EDSClient
    code with 3.4).

    At the moment, this is a compile time choice made automatically
    by configure. syncevolution.org binaries are compiled against
    an older EDS and thus do not work with EDS 3.5.x or later.

    EDS 3.5.x handles authentication itself, using a standard system
    prompt if necessary. SyncEvolution can no longer provide the password,
    and thus the “databaseUser/Password” options have no effect when using
    EDS 3.5.x.

  • D-Bus server: fixed HTTP presence for recent libdbus

    Testing with libdbus 1.6.0 on Debian Testing failed because the lib
    changed some behavior: instead of looking up the owner of a certain
    bus name immediately, it now does that when invoking a
    method. Therefore the check for “have connection” in SyncEvolution
    was too simplistic and missed the fact that both were not usable,
    causing the server to assume that HTTP was down while in reality it
    should have assumed it to be up. This prevented auto-syncing and
    manually clicking “Sync” in the GTK UI.

  • D-Bus server: made notification verbosity configurable with “notifyLevel”

    The new “notifyLevel” per-peer configuration option allows users to
    control how many desktop notifications the D-Bus server produces while
    executing an automatic sync:

    0 – suppress all notifications
    1 – show only errors
    2 – show information about changes and errors (in practice currently the same as level 3)
    3 – show all notifications, including starting a sync (default)

  • WebDAV: fixed data corruption issue when uploading item with long UID

    In some cases data with a very long UID wasn’t handled correctly,
    causing the out-going data to be malformed and probably causing a
    rejection by the server. The root cause is incorrect string handling.
    In releases before 1.2.99.1, only the –import operation of contacts
    into CardDAV were affected. In 1.2.99.1, the same code also got used
    for calendar items and then could also affect syncing.

  • CalDAV: updated Google workarounds

    Google started sending empty items (VCALENDAR with no VEVENT inside)
    which cannot be removed. SyncEvolution 1.3 ignores such items.

    The workaround for a 404 from Google Calendar for a GET (sending a
    REPORT request matching the item’s UID) was broken: first, processing
    the result ended up calling the unset responseEnd boost function
    pointer, which caused the request to fail. Second, getting multiple
    items wasn’t handled (data from all items concatenated together was
    used).

    That can happen in the somewhat unlike case that some items have a UID
    which is a complete superset of the requested UID – not realistic in
    real life, but happens during testing.

  • Google Calendar: updated URL redirect handling

    Google Calendar sometimes returns redirect requests to human-readable
    web sites (an “unavailable” page, a login form). This is of course
    bogus when the client is an automated CalDAV client.

    The “unavailable.html” case was already handled. Made it a bit more
    flexible to also catch possible variations of it (additional
    parameters, https instead of http).

    Added the https://accounts.google.com/ServiceLogin case. Not sure
    whether retrying will help in that case, but there’s not much else
    that SyncEvolution can do.

  • WebDAV: bridge with SyncML

    Now a peer accessed via SyncML can read/write data stored in a
    CalDAV/CardDAV server directly. This can be used to connect a device
    which only supports SyncML to a CalDAV/CardDAV server, or sync data
    between a SyncML server and a CalDAV/CardDAV server. See “CalDAV and
    CardDAV” in the README for details.

  • WebDAV: improved –configure

    Added INFO output about checking sources. This helps with WebDAV when
    the server cannot be contacted (dead, misconfigured) because otherwise
    there would be no indication at all why the –configure operation
    seems to hang.

    Here is some example output, including aborting:

    $ syncevolution --configure --template webdav \
                    syncURL=http://192.168.1.100:9000/ \
                    username=foo password=bar retryDuration=2s \
                    target-config@webdav-temp
    [INFO] creating configuration target-config@webdav-temp
    [INFO] addressbook: looking for databases...
    [INFO] addressbook: no database to synchronize
    [INFO] calendar: looking for databases...
    [INFO] calendar: no database to synchronize
    [INFO] memo: looking for databases...
    [INFO] memo: no database to synchronize
    [INFO] todo: looking for databases...
    [INFO] todo: no database to synchronize

    It timed out fairly quickly here because of the retryDuration=2s. That
    also gets placed in the resulting config, which is probably not desired.

    Aborting the operation is now supported:

    $ syncevolution --configure \
                    --template webdav \
                    syncURL=http://192.168.1.100:9000/ \
                    username=foo password=bar \
                    target-config@webdav-temp
    [INFO] creating configuration target-config@webdav-temp
    [INFO] addressbook: looking for databases...
    ^C[INFO] Asking to suspend...
    [INFO] Press CTRL-C again quickly (within 2s) to stop immediately (can cause problems in the future!)
    ^C[INFO] Aborting immediately ...
    [ERROR] error code from SyncEvolution aborted on behalf of user (local, status 20017): aborting as requested by user

    It would be good to make the CTRL-C handling code aware that it can
    abort immediately instead of doing the intermediate “asking to suspend”
    step, which only makes sense for sync sessions.

  • WebDAV: support tasks and memos (BMC #24893)

    The new backend property values “CalDAVTodo” and “CalDAVJournal”
    select tasks resp. memos stored in a CalDAV collection. “CalDAV”
    continues to select events.

    Events, tasks and journals can be mixed in the same resource (=
    URL). However, this is less efficient than storing them separately.

    A good CalDAV server allows filtering items by type, and SyncEvolution
    uses that. However, it was found that Radicale 0.7 ignores this
    filtering, which could have led to data loss (SyncEvolution asks for
    all VTODOs in preparation for a “delete all items” operation in a
    “CalDAVTodo” source, gets also VJOURNALs, then deletes them).

    Therefore SyncEvolution plays it safe and downloads the VTODO and
    VJOURNAL data to double-check that it is working on the right items.
    This causes additional traffic for well-behaving servers; currently
    it cannot be turned off.

    Tasks are exchanged as vCalendar 1.0 or iCalendar 2.0 VJOURNAL.
    Memos are exchanged as VTODO or plain text. The logic for storing
    incoming plain text is slightly different compared to the way how
    the EDS memo backend did it: instead of copying the first line
    from the text into the summary, it is now moved. In other words,
    the first line gets stripped. The change is primarily technically
    motivated; both approaches have pros and cons.

  • WebDAV: improved Radicale support

    Radicale > 0.7 will return status 200 for delete requests;
    is now treated like 204 by SyncEvolution. 412 ‘Preconditiona Failed’
    when asking to delete an already removed item is treated like
    the more common 404 ‘not found’. Same with 410 ‘gone’ instead
    of 404 when trying to read a non-existent item.

  • CalDAV/CardDAV sync: improved target side output

    Added a “target side of local sync ready” INFO message to introduce
    the output which has the target context in the [INFO] tag. The sync report
    from the target side now has the target context embedded in brackets
    after the “Changes applied during synchronization” header, to avoid
    ambiguities.

    Sometimes the backend has to resend requests because of temporary
    issues. If the problem turned out to be permanent, there was a long
    period of time, retryDuration=5 minutes to be precice, in which no
    visible progress happened.

    Now SyncEvolution’s WebDAV backend will print a message like this
    before going to sleep until it is time to retry:

    [INFO @googlecalendar] operation temporarily (?) failed, going to retry in 5.0s before giving up in 18.4s: PROPFIND: Neon error code 1: 401 Unauthorized

    The uncertainty comes from several factors. In this example, the 401
    might indicate a permanent problem (wrong credentials), or it could be
    Google reporting a temporary authorization problem which is (probably)
    meant to slow down the client while it asks the user to re-enter the
    password. SyncEvolution only asks for passwords once, so it tries
    again with the same password if it was successful with it in the
    past. Otherwise it gives up immediately.

    Another dubious example are name server lookup errors. They can be
    permanent (wrong host name) or temporary (name server
    down). SyncEvolution errs on the side of retrying, to avoid
    interrupting an operation which still has a chance to continue.

    Output from the target side of a local sync was passed through stderr
    redirection as chunks of text to the frontends. This had several
    drawbacks:

    • forwarding only happened when the local sync parent was processing
      the output redirection, which (due to limitations of the implementation)
      only happens when it needs to print something itself
    • debug messages were not forwarded
    • message boundaries might have been lost

    In particular the new INFO messages are relevant while the sync runs
    and need to be shown immediately.

  • WebDAV: –status for WebDAV source aborted

    The command line –status operation did not complete when applied to a
    CalDAV/CardDAV source. Instead it aborted because the operation took a
    code path where the backend was not fully initialized.

  • file backend: more flexible sync support for memos

    The databaseFormat=text/calendar for memos did not support
    synchronizing as plain text. When using the new
    databaseFormat=text/calendar+plain, vCalendar/iCalendar/plain text
    are all valid sync formats; the storage is iCalendar 2.0
    VJOURNAL in all cases.

  • WebDAV: avoid potential crash during database detection

    When a server responds to a PROPFIND for a path with results for some
    other path, then SyncEvolution crashed during the search for the
    default calendar or address book because of a bug in the code which
    was meant to handle that kind of response. Apparently Yahoo Calendar
    did that. Now seen again in combination with Radicale 0.6.4.

    In general, the code was made more robust to cope with bugs in
    Radicale 0.6.4. Later Radicale versions fixed these issues and also
    worked with SyncEvolution 1.2.2 without client-side workarounds.

  • WebDAV: better path normalization

    “syncURL” and “database” properties had to end in a trailing slash,
    otherwise items were not found (404 errors). Now the necessary slash
    is added automatically.

  • Curl transport: support SSLServerCertificates=

    When the setting refers to a directory, then CURLOPT_CAINFO doesn’t
    work (must be a file). Check this and use CURLOPT_CAPATH instead.

    Caveat: there are some comments in the API documentation about “NSS
    enabled libcurl” which supports a directory in
    CURLOPT_CAINFO. Hopefully providing an explicit path in CURLOPT_CAPATH
    also works in that configuration.

  • code cleanup + rewrite: syncing done in separate process

    syncevo-dbus-server now runs syncing in a separate process. Local
    sync also uses a second helper process. This makes the D-Bus server
    more responsive via D-Bus (no more blocking operations) and
    minimizes the effect of bugs in code involved with syncing
    (backends, system libraries, etc.).

    In the long term this restructuring will also allow more advanced
    features, like monitoring local or remote storage for changes.

  • SyncEvolution <-> SyncEvolution sync: multiple cycles per session

    SyncML only allows one send/receive cycle per session. There are cases
    (for example, client side merges data that a dumber server failed to
    match correctly) where client and server are still out of sync at
    the end of a cycle. When SyncEvolution syncs with another SyncEvolution
    instance (locally or remotely), both sides detect that the peer
    can continue syncing in the same session and start over automatically
    when needed. Previously the user had to start another sync session manually.

    To the user this is shown as “number of cycles” in a sync session
    in the sync report. “Restart” is the process of entering a new cycle.

    The cycles are also visible in the command line output as multiple
    INFO lines:

    [INFO] eds_contact: starting first time sync from client (peer is server)
    [INFO] creating complete data backup of source eds_contact before sync (enabled with dumpData and needed for prin
    Local data changes to be applied during synchronization:
    *** eds_contact ***
    no changes

    [INFO] eds_contact: sent 1/1
    [INFO] eds_contact: started
    [INFO] eds_contact: first time sync done successfully
    [INFO] eds_contact: starting normal sync from client (peer is server)         <===
    [INFO] eds_contact: started                                                   <===
    [INFO] eds_contact: 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 |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
    |   eds_contact |  0  |  0  |  0  |  0  |  1  |  0  |  0  |  0  |  0  |
    |   refresh-from-local, 2 cycles, 0 KB sent by client, 0 KB received  |
                            ^^^^^^^^
    |   item(s) in database backup: 1 before sync, 1 after it             |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
    |          start Tue Feb  7 17:07:49 2012, duration 0:03min           |
    |               synchronization completed successfully                |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+

  • SyncEvolution <-> SyncEvolution sync: negotiate UID support via SyncCap (BMC #22783)

    The semantic of UID/RECURRENCE-ID in calendar data is now tracked
    per data store involved in a sync. If full iCalendar 2.0 semantic
    (= IDs are globally unique) is guaranteed, then pairs are found
    based on these IDs. Otherwise pairs must be found by looking at
    item attributes.

    Previously a hack was used to detect this kind of support (any kind
    of SyncEvolution instance was assumed to support it, although some
    backends do not).

  • engine: add DTSTAMP+LAST-MODIFIED before writing calendar items

    When writing calendar items into a backend storage as iCalendar 2.0 or
    vCalendar 1.0, they should have DTSTAMP and LAST-MODIFIED values. DTSTAMP
    is expected by some CalDAV servers (like Apple). LAST-MODIFIED is usually
    added by the storage, but not always.

    In the text/plain -> syncevolution -> text/calendar -> Radicale -> EDS
    -> syncevolution chain the LAST-MODIFIED was not added by Radicale, which caused
    problems for change tracking in an EDS-based SyncEvolution.

    Also necessary when importing from a phone using vCalendar without
    DTSTAMP directly into CalDAV.

  • autotools: ensure that link lines are complete

    As mentioned by Tino Keitel on the mailing list, some libs and
    executables were only implicitly linked against libraries that they
    called directly. This happened to work by chance because these libraries
    ended up in the running executable anyway, due to indirect loading.
    Now there is a “make installcheck” test for this kind of defect
    and the makefiles were updated to avoid it.

    One exception is libsmltk, which depends on the caller providing
    SySync logging support.

  • syncevolution.org packages: fixed D-Bus server autostart in .deb and .rpm packages

    syncevo-dbus-server wasn’t started automatically as part of a user
    session because /etc/xdg/autostart/syncevo-dbus-server.desktop wasn’t
    included in the packages. This broke auto syncing after a session
    restart (required manually starting SyncEvolution).

  • syncevolution.org packages: support KDE

    The traditional “syncevolution-evolution” package was
    replaced with “syncevolution-bundle”. A meta “syncevolution-evolution”
    package depends on it, to support seamless updates for users who have
    “syncevolution-evolution” installed.

    Binary dependencies of the main .deb are ignored for backends
    because loading them is optional. The new “syncevolution-kde”
    package has the right dependencies for KDE/Akonadi, while
    “syncevolution-evolution” mostly just lists standard libs
    if the “EDS compatibility” mode is used, where libebook/libecal
    are loaded dynamically.

    Platform specific code (GNOME keyring, KDE wallet) was moved into
    loadable, optional modules, to allow installation of the SyncEvolution
    bundle without forcing the installation of unused system components.

  • D-Bus: use GIO D-Bus instead of libdbus if available

    When compiling from source, the more modern GIO D-Bus is used instead
    of libdbus if available and recent enough (>= 2.30). syncevolution.org
    binaries still use libdbus, to stay compatible with older Linux
    distros.

  • several minor bug fixes

    syncevo-dbus-server now runs under valgrind in the nightly testing,
    plus several more test scenarios were added. This helped to find
    and fix various minor memory handling issues.

  • developers: backend API changes

    beginSync/endSync() (aka m_startDataRead/m_endDataWrite) may now be
    called multiple times per SyncSource instance life cycle. SyncSources
    derived from TrackingSyncSource should work without changes. Use the
    Client::Source::*::testChangesMultiCycles test to check whether your
    backend supports this correctly.

    Reading and deleting must throw a 404 status exception when an item
    is not found. The Client::Source::::404 tests cover this.

    The special semantic of the former RegisterSyncSource::InactiveSource
    (invalid pointer of value 1) caused bugs, like using it in
    –print-databases (=> segfault) or not being able to store the result
    of a createSource() directly in a smart pointer (=> potential leak in
    SyncSource::createSource()).

    Obviously a bad idea to start with. Replaced with a
    RegisterSyncSource::InactiveSource() method which creates a real,
    inactive SyncSource instance which can and must be deleted by the
    caller.

    This is a SyncSource API change for backend developers. Instead of
    RegisterSyncSource::InactiveSource, return
    RegisterSyncSource::InactiveSource(). Comparisons against
    RegisterSyncSource::InactiveSource needs to be replaced with a call
    to the new SyncSource::isInactive().

    Long-running backend calls are encouraged to check for events on the
    main glib context (either in a loop or with
    g_main_context_iteration(NULL)) and abort when
    SuspendFlags::getSuspendFlags().getState() returns
    SuspendFlags::ABORT.

    Implementing the improved local sync output required extending the
    D-Bus API. The Server.LogOutput signal now has an additional
    “process name” parameter. Normally it is empty. For messages
    originating from the target side, it carries that extra target
    context string.

    This D-Bus API change is backward compatible. Older clients can still
    subscribe to and decode the LogOutput messages, they’ll simply ignore
    the extra parameter. Newer clients expecting that extra parameter
    won’t work with an older D-Bus daemon: they’ll fail to decode the
    D-Bus message.

  • packagers:

    libgdbussyncevo is now installed as a normal library in /usr/lib,
    even though SyncEvolution is the only user.

    pcrecpp is now a new hard dependency.

Changes 1.2.99.4 -> 1.3

  • D-Bus server + GIO D-Bus: shutdown fix

    When compiled against GIO D-Bus (not the case in syncevolution.org
    binaries), the syncevo-dbus-server occasionally shut down before
    sending out all pending D-Bus messages. Showed up only in nightly
    testing.

  • D-Bus server + GIO D-Bus: fix auto-activation (Debian bug #599247)

    When syncevo-dbus-server was started on demand by the D-Bus daemon,
    then it registered itself with the daemon before it was ready to
    serve requests. Only happened in combination with GIO D-Bus and
    thus was not a problem before 1.2.99.x.

    One user-visible effect was that the GTK UI did not select the default
    service when it was started for the first time, because it could not
    retrieve that information from syncevo-dbus-server.

  • local sync: fix timeout with local sync with libdbus

    When using libdbus instead of GIO D-Bus (as done by syncevolution.org
    binaries and SyncEvolution on Maemo), local sync may have aborted
    after 25 seconds when syncing many items with a D-Bus timeout error:

    [ERROR] sending message to child failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible ca

    Reported by Toke Høiland-Jørgensen for Harmattan. Somehow not encountered
    elsewhere.

  • KDE: check for D-Bus to avoid crash in KApplication (BMC #25596)

    Some unnamed version of KDE crashes in KApplication when invoked
    without a D-Bus session. The reporter ran into this when compiling
    from source, because the SyncEvolution binary is invoked as part of
    the build process, which ran outside of a D-Bus session.

    Avoid the crash by checking for a D-Bus session bus before instantiating
    KApplication. Instantiating KApplication was added for KWallet support.
    Without D-Bus, KWallet does not work either, therefore throw an explicit
    error when the lack of D-Bus is detected.

  • Funambol: work around PHOTO TYPE=image/jpeg

    A combination of Funambol Android and Funambol server recently led to
    the Funambol server sending PHOTO data with TYPE=image/jpeg. This is
    invalid and caused EDS to reject the photo (Vladimir Elisseev,
    “[SyncEvolution] issues with syncing photos”).

    Work around the problem by only keeping the part of the type after the
    last slash, if there is any. For image/jpeg and similar types that
    leads to the desired value and does not affect valid values, because
    those do not contain a slash
    (http://www.iana.org/assignments/media-types/image/index.html).

  • syncevo-http-server: fixed printing of server debug output

    Python failed to call logSyncEvoOutput() after adding the additional
    ‘process’ parameter to LogOutput because it extracts all four
    parameters and then cannot pass them to logSyncEvoOutput().

    Now logSyncEvoOutput() uses the new process information to instantiate
    a logger with the right prefix, using ’sync’ as fallback for messages
    without that information (as before).

  • Some minor code and test cleanup.

Source, Installation, Further information

Source code bundles for users are available in
http://downloads.syncevolution.org/syncevolution/sources
and the original source is in
the git repositories.

i386, lpia and amd64 binaries for Debian-based distributions are
available via the “stable” syncevolution.org repository. Add the
following entry to your /apt/source.list:

Then install “syncevolution-evolution”, “syncevolution-kde” and/or
“syncevolution-activesync”.

These binaries include the “sync-ui” GTK GUI and were compiled for
Ubuntu 8.04 LTS (Hardy), except for “syncevolution-activesync” which
depends on libraries in Debian Squeeze, for example EDS 3.4.

Older distributions like Debian 4.0 (Etch) can no longer be supported
with precompiled binaries because of missing libraries, but the source
still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in
the download directories. In contrast
to 0.8.x archives, the 1.x .tar.gz archives have to be unpacked and the
content must be moved to /usr, because several files would not be found
otherwise.

After installation, follow the getting started steps.

SyncEvolution 1.2.99.3 and 1.2.99.4 released, bug tracking at freedesktop.org

Work towards the 1.3 release of SyncEvolution continued with two more snapshots since the last announcement.

The project also moved its bug tracking from bugs.meego.com to bugs.freedesktop.org. Most of the old issues were already migrated, the rest will follow later. Please file new issues there.

The git repos are still at meego.com; they will move to freedesktop.org eventually.

SyncEvolution 1.2.99.3 -> 1.2.99.4, 07.08.2012

Another release candidate for SyncEvolution 1.3. Lesson learned:
declaring a snapshot as “final” is a good way of luring the hidden bugs
into the light. Of course, then another snapshot is needed…

Details:

  • D-Bus server: fix support for autoSyncDelay > 0

    Auto syncing was not getting triggered when using an autoSyncDelay > 0;
    by default it is 5 minutes. Thanks to Vladimir Elisseev for reporting
    this problem.

  • command line: fixed –export

    When exporting items into a file, the delimiter between items
    was missing.

  • config: improved ‘maxlogdirs’ documentation

    The old explanation made it sound like nothing would get deleted by
    default (”If set, …”). That’s not correct, by default only 10
    sessions are kept.
    Also explain the behavior of deleting intermediate sessions first.

  • developers: fixed D-Bus interface XML

    Reverted to Qt 4.x compatible annotations and changed “templateName”
    to “getTemplate” to make it more obvious what the parameter does.
    Only relevant for the out-of-tree Qt UI.

    Fixed accidental removal of the “template” parameter in
    Session.GetNamedConfig(). Was not used in practice, but has to be
    correct in case that someone wants to use it.

SyncEvolution 1.2.99.2 -> 1.2.99.3, 24.07.2012

Final release candidate for SyncEvolution 1.3 – fingers crossed,
knock on wood, etc.

ActiveSync is now available in binaries from syncevolution.org and
becomes the recommended way of synchronizing contacts with Google. EDS
3.5.x and later are supported when compiling from source;
syncevolution.org binaries continue to support only EDS up to 3.4.

Details:

  • EDS: added support for EDS 3.5.x

    When compiled against EDS 3.5.x or later, SyncEvolution now uses
    the backend code originally written for the EClient API introduced
    in EDS 3.2. That code was changed so that it works with the new
    include file rules and ESourceRegistry in EDS 3.5.x. Support
    for using the EClient API with EDS 3.4 was removed because maintaining
    three different flavors of the EDS backend code would be too much
    work and not gain much (just the possibility to test the EDSClient
    code with 3.4).

    At the moment, this is a compile time choice made automatically
    by configure. syncevolution.org binaries are compiled against
    an older EDS and thus do not work with EDS 3.5.x or later.

    EDS 3.5.x handles authentication itself, using a standard system
    prompt if necessary. SyncEvolution can no longer provide the password,
    and thus the “databaseUser/Password” options have no effect when using
    EDS 3.5.x.

  • ActiveSync: updated to work with latest activesyncd and Google, package binaries

    Syncing Google contacts was added to the nightly testing. Syncing
    contacts and events with Exchange 2012 was already working. Setup
    instructions and known issues are described here:
    https://syncevolution.org/wiki/google-contacts-activesync

  • local sync: don’t drop data comparison output on target side

    synccompare on the target side of a local sync was invoked with its
    output being redirected via an unreliable socket to the local sync
    parent. When the output was large, some of it might have been lost.

  • local sync: fixed crash

    When processing stdout from syncevo-local-child in
    syncevo-dbus-helper, the LogRedirect class was invoked recursively and
    tried to print the same stdout data repeatedly until the
    syncevo-dbus-helper crashed due to the infinite recurssion.

  • local sync: fixed helper process shutdown in case of parent failure

    The helper process only detected that the parent failed when
    it tried to log something while the parent had already shut down
    the D-Bus connection. Even that did not work reliably and differed
    between D-Bus libdbus and GIO.

    Added several test cases and fixes for “process died prematurely”
    error scenarios.

  • Mobical (aka Everdroid): stopped testing memo syncing

    Memos used to work, but now only trigger an unspecific 400 error
    on the server side.

  • autotools: ensure that link lines are complete

    As mentioned by Tino Keitel on the mailing list, some libs and
    executables were only implicitly linked against libraries that they
    called directly. This happened to work by chance because these libraries
    ended up in the running executable anyway, due to indirect loading.
    Now there is a “make installcheck” test for this kind of defect
    and the makefiles were updated to avoid it.

    One exception is libsmltk, which depends on the caller providing
    SySync logging support.

  • D-Bus server: fixed HTTP presence for recent libdbus

    Testing with libdbus 1.6.0 on Debian Testing failed because the lib
    changed some behavior: instead of looking up the owner of a certain
    bus name immediately, it now does that when invoking a
    method. Therefore the check for “have connection” in SyncEvolution
    was too simplistic and missed the fact that both were not usable,
    causing the server to assume that HTTP was down while in reality it
    should have assumed it to be up. This prevented auto-syncing and
    manually clicking “Sync” in the GTK UI.

  • syncevolution.org: declare dependencies on libical and EDS

    Let the bundle .deb depend on libical if the lib was enabled during
    compilation (for example, for CalDAV). This ensures that it gets
    installed on systems which otherwise don’t have it.

    “syncevolution-evolution” is compatible (and depends on) EDS up to
    and including 3.4. The package now declares that dependency and
    conflicts with more recent EDS, because even if the older EDS libs
    are still installed they won’t work when the rest of EDS was
    updated.

  • CalDAV + syncevolution.org: fixed segfault without libical+libecal

    When libical and libecal were not installed, trying to use the CalDAV
    backend for VEVENTs segfaulted because it depends on libical and did
    not check properly for it. Only affected syncevolution.org binaries.

Upgrading from release 1.2.x:

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):
syncevolution –configure \
syncFormat=text/x-vcard \
mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:
syncevolution –configure \
enableRefreshSync=TRUE \
funambol

Upgrading from releases before 1.2:

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information

Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources

i386, lpia and amd64 binaries for Debian-based distributions are available via the “unstable” syncevolution.org repository. Add the following entry to your /apt/source.list, then install “syncevolution-evolution”:

These binaries include the “sync-ui” GTK GUI and were compiled for Ubuntu 8.04 LTS (Hardy). Older distributions like Debian 4.0 (Etch) can no longer be supported with precompiled binaries because of missing libraries, but the source still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in the download directories. In contrast to 0.8.x archives, the new .tar.gz archives have to be unpacked and the content must be moved to /usr, because several files would not be found otherwise.

After installation, follow the getting started steps.

SyncEvolution 1.2.99.2 released

Next step towards SyncEvolution 1.3. It adds a workaround for
Funambol’s OneMedia and fixes an old bug which became more severe in
1.2.99.1. Also has some usability improvements for
CalDAV/CardDAV. Hopefully it will not take long to stabilize the code,
so test it now while it is still hot :-)

Details:

  • Funambol: ignore UID

    Funambol’s OneMedia sends UID, but not RECURRENCE-ID. That becomes a
    problem when multiple events of the same event series are added to a
    backend which follows the iCalendar 2.0 standard (CalDAV, EDS, KDE),
    because these events all look like the master event, and there can be
    only one of those.

    SyncEvolution now strips the UID from all events coming from any
    Funambol server (regardless of the version). If a future Funambol
    server release adds support for both UID and RECURRENCE-ID, then
    SyncEvolution will have to be updated to take advantage of the
    improved server. Because the RECURRENCE-ID is also getting
    stripped (despite not being set at the moment), SyncEvolution should
    continue to work as it does now even if the server changes.

    It would have been nice to limit this workaround to affected Funambol
    server versions, but an inquiry on the Funambol mailing list didn’t
    get a reply, therefore SyncEvolution is playing it safe and assumes
    that all future Funambol releases will have the same problem.

  • WebDAV: fixed data corruption issue when uploading item with long UID

    In some cases data with a very long UID wasn’t handled correctly,
    causing the out-going data to be malformed and probably causing a
    rejection by the server. The root cause is incorrect string handling.
    In releases before 1.2.99.1, only the –import operation of contacts
    into CardDAV were affected. In 1.2.99.1, the same code also got used
    for calendar items and then could also affect syncing.

  • engine: add DTSTAMP+LAST-MODIFIED before writing calendar items

    When writing calendar items into a backend storage as iCalendar 2.0 or
    vCalendar 1.0, they should have DTSTAMP and LAST-MODIFIED values. DTSTAMP
    is expected by some CalDAV servers (like Apple). LAST-MODIFIED is usually
    added by the storage, but not always.

    In the text/plain -> syncevolution -> text/calendar -> Radicale -> EDS
    -> syncevolution chain the LAST-MODIFIED was not added by Radicale, which caused
    problems for change tracking in an EDS-based SyncEvolution.

    Also necessary when importing from a phone using vCalendar without
    DTSTAMP directly into CalDAV.

  • Google Calendar: updated URL redirect handling

    Google Calendar sometimes returns redirect requests to human-readable
    web sites (an “unavailable” page, a login form). This is of course
    bogus when the client is an automated CalDAV client.

    The “unavailable.html” case was already handled. Made it a bit more
    flexible to also catch possible variations of it (additional
    parameters, https instead of http).

    Added the https://accounts.google.com/ServiceLogin case. Not sure
    whether retrying will help in that case, but there’s not much else
    that SyncEvolution can do.

  • CalDAV + VJOURNAL: handle UID conflicts

    When asked to insert a VJOURNAL which already existed (= same UID),
    CalDAV servers respond with a 412 “Precondition failed” error. This
    needs to be detected and translated into an “item needs to be merged”
    result so that the engine can load the existing item, merge the data,
    and then write back.

  • WebDAV: –status for WebDAV source aborted

    The command line –status operation did not complete when applied to a
    CalDAV/CardDAV source. Instead it aborted because the operation took a
    code path where the backend was not fully initialized.

  • CalDAV/CardDAV sync: improved target side output

    Added a “target side of local sync ready” INFO message to introduce
    the output which has the target context in the [INFO] tag. The sync report
    from the target side now has the target context embedded in brackets
    after the “Changes applied during synchronization” header, to avoid
    ambiguities.

    Sometimes the backend has to resend requests because of temporary
    issues. If the problem turned out to be permanent, there was a long
    period of time, retryDuration=5 minutes to be precice, in which no
    visible progress happened.

    Now SyncEvolution’s WebDAV backend will print a message like this
    before going to sleep until it is time to retry:

    [INFO @googlecalendar] operation temporarily (?) failed, going to retry in 5.0s before giving up in 18.4s: PROPFIND: Neon error code 1: 401 Unauthorized

    The uncertainty comes from several factors. In this example, the 401
    might indicate a permanent problem (wrong credentials), or it could be
    Google reporting a temporary authorization problem which is (probably)
    meant to slow down the client while it asks the user to re-enter the
    password. SyncEvolution only asks for passwords once, so it tries
    again with the same password if it was successful with it in the
    past. Otherwise it gives up immediately.

    Another dubious example are name server lookup errors. They can be
    permanent (wrong host name) or temporary (name server
    down). SyncEvolution errs on the side of retrying, to avoid
    interrupting an operation which still has a chance to continue.

    Output from the target side of a local sync was passed through stderr
    redirection as chunks of text to the frontends. This had several
    drawbacks:

    • forwarding only happened when the local sync parent was processing
      the output redirection, which (due to limitations of the implementation)
      only happens when it needs to print something itself
    • debug messages were not forwarded
    • message boundaries might have been lost

    In particular the new INFO messages are relevant while the sync runs
    and need to be shown immediately.

  • command line: fixed password + property lookup during –print-databases

    –print-databases for an existing configuration did not look up
    passwords stored in a keyring, causing the operation to fail for
    backends like CalDAV/CardDAV where credentials are required.

    Overriding source properties in that case also only worked when using
    the unqualified property name (”databasePassword=foo”) but not when
    using the source name as prefix (”calendar/databasePassword=foo”).

  • Developers:

    Implementing the improved local sync output required extending the
    D-Bus API. The Server.LogOutput signal now has an additional
    “process name” parameter. Normally it is empty. For messages
    originating from the target side, it carries that extra target
    context string.

    This D-Bus API change is backward compatible. Older clients can still
    subscribe to and decode the LogOutput messages, they’ll simply ignore
    the extra parameter. Newer clients expecting that extra parameter
    won’t work with an older D-Bus daemon: they’ll fail to decode the
    D-Bus message.

Upgrading from release 1.2.x:

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):

   syncevolution --configure \
                 syncFormat=text/x-vcard \
                 mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:

   syncevolution --configure \
                 enableRefreshSync=TRUE \
                 funambol

Upgrading from releases before 1.2:

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information

Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources

i386, lpia and amd64 binaries for Debian-based distributions are available via the “unstable” syncevolution.org repository. Add the following entry to your /apt/source.list, then install “syncevolution-evolution”:

These binaries include the “sync-ui” GTK GUI and were compiled for Ubuntu 8.04 LTS (Hardy). Older distributions like Debian 4.0 (Etch) can no longer be supported with precompiled binaries because of missing libraries, but the source still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in the download directories. In contrast to 0.8.x archives, the new .tar.gz archives have to be unpacked and the content must be moved to /usr, because several files would not be found otherwise.

After installation, follow the getting started steps.

SyncEvolution 1.2.99.1 released

First pre-release of SyncEvolution 1.3. Contains bug fixes that were
not backported to 1.2.x, so upgrading is recommended. For example,
SyncEvolution 1.3 is required for Evolution 3.4, otherwise photos are
not exported properly. Further workarounds for recent changes in
Google CalDAV were added.

Major new features are KDE/Akonadi support in the syncevolution.org
binaries and ActiveSync support (only in the source code). The D-Bus
server and local sync were rewritten considerably, to make the code
cleaner and more robust. The CalDAV backend now also supports tasks
and memos.

Details:

  • phone sync: delete<->delete conflict + phone calendar+todo sync (BMC #23744)

    When deleting an item on phone and locally, the next sync failed with
    ERROR messages about “object not found”. This has several reasons:

    • libsynthesis super data store attempts to read items
      which may or may not exist (triggers ERROR message)
    • it checks for 404 but Evolution backends only return a generic
      database error (causes sync to fail)
  • phone sync: get phone vendor and model from Device ID profile (BMC #736)

    In the past we have relied on the user-modifiable device name to be
    the fingerprint for matching a phone to a template which is unreliable.

    This release changes this in the cases where the phone supports the
    Device ID profile (DIP). If support for DIP is detected, then we
    extract the vendor and product ids and attempt to associate them
    with a product and vendor name by using a newly added lookup table.

    This lookup table has to be maintained manually and depends on
    contributions by users to cover more devices. See
    http://blixtra.org/blog/2011/09/22/syncevolution-needs-you-or-at-least-y…

  • vCalendar 1.0: fixed recurring all-day event support

    vCalendar 1.0 cannot represent all-day events. The workarounds for
    mapping iCalendar 2.0 all-day events into vCalendar 1.0 was
    incomplete, leading to effects like shifting EXDATEs and end
    times.

  • GTK-UI: accept service config with a username again (BMC#23106)

    Suppressing configs with empty username had undesired side effects:
    modifying configs for direct syncing with a device incorrectly
    triggered the same error message, without any means of entering
    a username. The faulty check was removed without replacement.

  • GTK-UI: added GTK 3 version of UI

    When GTK 3 is found during compilation, a GTK 3 version of the
    UI is built. The source code of both is different to avoid
    excessive use of ifdefs. At the moment, both versions offer
    the same features. In the long run, the GTK 3 version will
    replace the GTK 2 version.

  • command line: added refresh/one-way-from-local/remote (BMC #23537)

    The -from-client/server sync modes are confusing because the direction
    of the data exchange depends on which side acts as SyncML server or
    client.

    This release introduces new modes which use -from-local/remote
    instead. The statistics and messages also use these variants
    now. The old modes are still understood, but are declared as “not
    recommended” in the documentation.

  • command line: config and source names are optional (BMC #23783)

    The need to add “foo” and “bar” pseudo config and source names to the
    command line even when all parameters for the operation where
    explicitly specified on the command line was confusing.

    Now it is possible to invoke item operations without the config and
    source name. Names which refer to non-existent configs are still
    accepted, as in previous releases. Typos are handled better by
    producing a detailed error report which includes (as applicable):

    • config doesn’t exist
    • source doesn’t exist or not selected
    • backend property not set

    Because luids used to be positional arguments after and
    , a new –luids keyword is necessary to indicate that the
    ensuing parameters are luids and not and .

  • command line: introduced –print-databases, supported for CalDAV/CardDAV

    Listing databases is now a dedicated operation, instead of being done
    whenever syncevolution was invoked without parameters.

    Advantages:

    • can be combined with property assignments for backends
      which do not work without that additional information, for example
      CalDAV/CardDAV:

          syncevolution --print-databases \
                        backend=[caldav|carddav] \
                        syncURL=... \
                        username=... \
                        password=...
    • can be done for configured sources
  • command line: use both stdout and stderr

    Traditionally, the “syncevolution” command line tool mixed its
    INFO/ERROR/DEBUG messages into the normal stdout. This has the major
    drawback that error messages get lost during operations like
    syncevolution –export – @default addressbook | grep “John Doe”

    Now anything which not the expected result of the operation is
    always sent to stderr. Obviously this includes ERROR messages. INFO
    and DEBUG are harder to decide. Because they usually convey meta
    information about the running operation, they are also sent to
    stderr. The output of running a sync goes to both stdout (summary)
    and stderr (progress).

  • command line: allow setting empty properties

    Due to the way how properties were handled internally, it wasn’t
    possible to explicitly set a property to its default value. Instead
    the property was unset. For example, explicitly setting database= was
    not possible.

    This is necessary for client-test and ActiveSync, because client-test
    needs to know that the testing is expected to run with the default
    databases (something which normally is avoided by overwriting empty
    database properties).

    Now the “is set” state is tracked explicitly in the config storage and
    command line property APIs. Unsetting a property via the command line
    could be implemented with an explicit command line option, but is not
    supported at the moment.

  • command line + local sync: fixed erroneous “Comparison impossible” output.

    “Comparison impossible” was incorrectly printed after a successful
    comparison on the target side of local sync.

  • synccompare: shorter data dump of PHOTO

    A full comparison of the base64 PHOTO data can be very long.
    Now some key characteristics of the PHOTO data (number of
    characters in base64 encoding, number of bytes in decoded
    data, md5sum of decoded data) are printed instead.

    That way, unintended changes of the data (different encoding,
    different content) should still be found while testing and
    added/removed photos are nicely visible in synccompare diffs.

  • synccompare: fixed output for byte-identical duplicates

    If database dumps contained byte-identical duplicates, they
    were treated as a single item on the left side of a comparison.
    This caused erroneous “added” entries on the right side.

  • secure password storage: usage of GNOME Keyring vs. KDE KWallet configurable

    Automatically detecting KDE users is not possible at the
    moment. Instead KDE users have to manually set the new “keyring”
    global config property to “KDE” (case insensitive) if the
    SyncEvolution installation supports both, because GNOME Keyring is the
    default to avoid surprises for traditional users. If only KWallet
    support is enabled, then this is not necessary.

    “GNOME” and “true/false/1/0/yes/no” can also be set. This has the
    advantage that keyring usage can be enabled permanently for the
    command line in –daemon=no mode; normally keyrings are not used in
    that mode because accessing them can bring up UI dialogs.

    It also becomes possible to disable keyring usage in syncevo-dbus-server,
    something which couldn’t be done before.

    The –keyring command line option is still supported, as an alias for
    “[--sync-property] keyring=”. The default value for –keyring
    is true, to match the traditional behavior. In contrast to other sync
    properties, setting “keyring” does not require an explicit –run
    parameter. Again this is done to mirror traditional usage.

  • Evolution: always create databases (PTCOM-113)

    Always try to create address book or calendar database, because even
    if there is a source there’s no guarantee that the actual database
    was created already; the original logic for only setting this when
    explicitly requesting a new database therefore failed in some cases.

    This problem affected users who had never created anything locally
    and wanted to use SyncEvolution to migrate their data. Now that
    works without having to create dummy entries first.

  • Evolution contacts: changed default sync format to vCard 3.0

    vCard 3.0 is the better default because it has saner encoding
    rules and defines more properties, thus avoiding the need for
    non-standard extensions. However, Mobical has problems with
    the new default. See upgrade instructions below.

  • D-Bus server: made notification verbosity configurable with “notifyLevel”

    The new “notifyLevel” per-peer configuration option allows users to
    control how many desktop notifications the D-Bus server produces while
    executing an automatic sync:

    0 – suppress all notifications
    1 – show only errors
    2 – show information about changes and errors (in practice currently the same as level 3)
    3 – show all notifications, including starting a sync (default)

  • CalDAV: updated Google workarounds

    Google started sending empty items (VCALENDAR with no VEVENT inside)
    which cannot be removed. SyncEvolution 1.3 ignores such items.

    The workaround for a 404 from Google Calendar for a GET (sending a
    REPORT request matching the item’s UID) was broken: first, processing
    the result ended up calling the unset responseEnd boost function
    pointer, which caused the request to fail. Second, getting multiple
    items wasn’t handled (data from all items concatenated together was
    used).

    That can happen in the somewhat unlike case that some items have a UID
    which is a complete superset of the requested UID – not realistic in
    real life, but happens during testing.

  • WebDAV: bridge with SyncML

    Now a peer accessed via SyncML can read/write data stored in a
    CalDAV/CardDAV server directly. This can be used to connect a device
    which only supports SyncML to a CalDAV/CardDAV server, or sync data
    between a SyncML server and a CalDAV/CardDAV server. See “CalDAV and
    CardDAV” in the README for details.

  • WebDAV: improved –configure

    Added INFO output about checking sources. This helps with WebDAV when
    the server cannot be contacted (dead, misconfigured) because otherwise
    there would be no indication at all why the –configure operation
    seems to hang.

    Here is some example output, including aborting:

      $ syncevolution --configure --template webdav \
                      syncURL=http://192.168.1.100:9000/ \
                      username=foo password=bar retryDuration=2s \
                      target-config@webdav-temp
      [INFO] creating configuration target-config@webdav-temp
      [INFO] addressbook: looking for databases...
      [INFO] addressbook: no database to synchronize
      [INFO] calendar: looking for databases...
      [INFO] calendar: no database to synchronize
      [INFO] memo: looking for databases...
      [INFO] memo: no database to synchronize
      [INFO] todo: looking for databases...
      [INFO] todo: no database to synchronize

    It timed out fairly quickly here because of the retryDuration=2s. That
    also gets placed in the resulting config, which is probably not desired.

    Aborting the operation is now supported:

  $ syncevolution --configure \
                  --template webdav \
                  syncURL=http://192.168.1.100:9000/ \
                  username=foo password=bar \
                  target-config@webdav-temp
  [INFO] creating configuration target-config@webdav-temp
  [INFO] addressbook: looking for databases...
  ^C[INFO] Asking to suspend...
  [INFO] Press CTRL-C again quickly (within 2s) to stop immediately (can cause problems in the future!)
  ^C[INFO] Aborting immediately ...
  [ERROR] error code from SyncEvolution aborted on behalf of user (local, status 20017): aborting as requested by user

It would be good to make the CTRL-C handling code aware that it can
abort immediately instead of doing the intermediate “asking to suspend”
step, which only makes sense for sync sessions.

  • WebDAV: support tasks and memos (BMC #24893)

    The new backend property values “CalDAVTodo” and “CalDAVJournal”
    select tasks resp. memos stored in a CalDAV collection. “CalDAV”
    continues to select events.

    Events, tasks and journals can be mixed in the same resource (=
    URL). However, this is less efficient than storing them separately.

    A good CalDAV server allows filtering items by type, and SyncEvolution
    uses that. However, it was found that Radicale 0.7 ignores this
    filtering, which could have led to data loss (SyncEvolution asks for
    all VTODOs in preparation for a “delete all items” operation in a
    “CalDAVTodo” source, gets also VJOURNALs, then deletes them).

    Therefore SyncEvolution plays it safe and downloads the VTODO and
    VJOURNAL data to double-check that it is working on the right items.
    This causes additional traffic for well-behaving servers; currently
    it cannot be turned off.

    Tasks are exchanged as vCalendar 1.0 or iCalendar 2.0 VJOURNAL.
    Memos are exchanged as VTODO or plain text. The logic for storing
    incoming plain text is slightly different compared to the way how
    the EDS memo backend did it: instead of copying the first line
    from the text into the summary, it is now moved. In other words,
    the first line gets stripped. The change is primarily technically
    motivated; both approaches have pros and cons.

  • WebDAV: improved Radicale support

    Radicale > 0.7 will return status 200 for delete requests;
    is now treated like 204 by SyncEvolution. 412 ‘Preconditiona Failed’
    when asking to delete an already removed item is treated like
    the more common 404 ‘not found’. Same with 410 ‘gone’ instead
    of 404 when trying to read a non-existent item.

  • file backend: more flexible sync support for memos

    The databaseFormat=text/calendar for memos did not support
    synchronizing as plain text. When using the new
    databaseFormat=text/calendar+plain, vCalendar/iCalendar/plain text
    are all valid sync formats; the storage is iCalendar 2.0
    VJOURNAL in all cases.

  • WebDAV: avoid potential crash during database detection

    When a server responds to a PROPFIND for a path with results for some
    other path, then SyncEvolution crashed during the search for the
    default calendar or address book because of a bug in the code which
    was meant to handle that kind of response. Apparently Yahoo Calendar
    did that. Now seen again in combination with Radicale 0.6.4.

    In general, the code was made more robust to cope with bugs in
    Radicale 0.6.4. Later Radicale versions fixed these issues and also
    worked with SyncEvolution 1.2.2 without client-side workarounds.

  • WebDAV: better path normalization

    “syncURL” and “database” properties had to end in a trailing slash,
    otherwise items were not found (404 errors). Now the necessary slash
    is added automatically.

  • Funambol: avoid slow syncs in refresh from server

    libsynthesis has traditionally implemented “refresh-from-server” as
    “delete local data” plus “slow” sync. This is more compatible, because
    some servers (like Google) do not support “refresh-from-server”.

    But it has the downside that the server cannot know that the client
    won’t send any data, and Funambol’s OneMedia now only allows one slow
    sync before blocking the next one for a certain period of time. This is
    done to prevent excessive resource usage by badly behaving clients.

    To accomodate both kinds of servers, the new “enableRefreshSync”
    sync property can be set set to explicitly allow the usage of
    the “refresh-from-server” sync mode. It’s off by default. The Funambol
    template has it turned on, existing configs must be updated manually
    (see upgrading comments below).

  • Curl transport: support SSLServerCertificates=

    When the setting refers to a directory, then CURLOPT_CAINFO doesn’t
    work (must be a file). Check this and use CURLOPT_CAPATH instead.

    Caveat: there are some comments in the API documentation about “NSS
    enabled libcurl” which supports a directory in
    CURLOPT_CAINFO. Hopefully providing an explicit path in CURLOPT_CAPATH
    also works in that configuration.

  • code cleanup + rewrite: syncing done in separate process

    syncevo-dbus-server now runs syncing in a separate process. Local
    sync also uses a second helper process. This makes the D-Bus server
    more responsive via D-Bus (no more blocking operations) and
    minimizes the effect of bugs in code involved with syncing
    (backends, system libraries, etc.).

    In the long term this restructuring will also allow more advanced
    features, like monitoring local or remote storage for changes.

  • SyncEvolution <-> SyncEvolution sync: multiple cycles per session

    SyncML only allows one send/receive cycle per session. There are cases
    (for example, client side merges data that a dumber server failed to
    match correctly) where client and server are still out of sync at
    the end of a cycle. When SyncEvolution syncs with another SyncEvolution
    instance (locally or remotely), both sides detect that the peer
    can continue syncing in the same session and start over automatically
    when needed. Previously the user had to start another sync session manually.

    To the user this is shown as “number of cycles” in a sync session
    in the sync report. “Restart” is the process of entering a new cycle.

    The cycles are also visible in the command line output as multiple
    INFO lines:

    [INFO] eds_contact: starting first time sync from client (peer is server)
    [INFO] creating complete data backup of source eds_contact before sync (enabled with dumpData and needed for prin
    Local data changes to be applied during synchronization:
    *** eds_contact ***
    no changes

    [INFO] eds_contact: sent 1/1
    [INFO] eds_contact: started
    [INFO] eds_contact: first time sync done successfully
    [INFO] eds_contact: starting normal sync from client (peer is server)         <===
    [INFO] eds_contact: started                                                   <===
    [INFO] eds_contact: 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 |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
    |   eds_contact |  0  |  0  |  0  |  0  |  1  |  0  |  0  |  0  |  0  |
    |   refresh-from-local, 2 cycles, 0 KB sent by client, 0 KB received  |
                            ^^^^^^^^
    |   item(s) in database backup: 1 before sync, 1 after it             |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
    |          start Tue Feb  7 17:07:49 2012, duration 0:03min           |
    |               synchronization completed successfully                |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+

  • SyncEvolution <-> SyncEvolution sync: negotiate UID support via SyncCap (BMC #22783)

    The semantic of UID/RECURRENCE-ID in calendar data is now tracked
    per data store involved in a sync. If full iCalendar 2.0 semantic
    (= IDs are globally unique) is guaranteed, then pairs are found
    based on these IDs. Otherwise pairs must be found by looking at
    item attributes.

    Previously a hack was used to detect this kind of support (any kind
    of SyncEvolution instance was assumed to support it, although some
    backends do not).

  • syncevolution.org packages: fixed D-Bus server autostart in .deb and .rpm packages

    syncevo-dbus-server wasn’t started automatically as part of a user
    session because /etc/xdg/autostart/syncevo-dbus-server.desktop wasn’t
    included in the packages. This broke auto syncing after a session
    restart (required manually starting SyncEvolution).

  • syncevolution.org packages: support KDE

    The traditional “syncevolution-evolution” package was
    replaced with “syncevolution-bundle”. A meta “syncevolution-evolution”
    package depends on it, to support seamless updates for users who have
    “syncevolution-evolution” installed.

    Binary dependencies of the main .deb are ignored for backends
    because loading them is optional. The new “syncevolution-kde”
    package has the right dependencies for KDE/Akonadi, while
    “syncevolution-evolution” mostly just lists standard libs
    if the “EDS compatibility” mode is used, where libebook/libecal
    are loaded dynamically.

    Platform specific code (GNOME keyring, KDE wallet) was moved into
    loadable, optional modules, to allow installation of the SyncEvolution
    bundle without forcing the installation of unused system components.

  • D-Bus: use GIO D-Bus instead of libdbus if available

    When compiling from source, the more modern GIO D-Bus is used instead
    of libdbus if available and recent enough (>= 2.30). syncevolution.org
    binaries still use libdbus, to stay compatible with older Linux
    distros.

  • several minor bug fixes

    syncevo-dbus-server now runs under valgrind in the nightly testing,
    plus several more test scenarios were added. This helped to find
    and fix various minor memory handling issues.

  • developers: backend API changes

    beginSync/endSync() (aka m_startDataRead/m_endDataWrite) may now be
    called multiple times per SyncSource instance life cycle. SyncSources
    derived from TrackingSyncSource should work without changes. Use the
    Client::Source::*::testChangesMultiCycles test to check whether your
    backend supports this correctly.

    Reading and deleting must throw a 404 status exception when an item
    is not found. The Client::Source::::404 tests cover this.

    The special semantic of the former RegisterSyncSource::InactiveSource
    (invalid pointer of value 1) caused bugs, like using it in
    –print-databases (=> segfault) or not being able to store the result
    of a createSource() directly in a smart pointer (=> potential leak in
    SyncSource::createSource()).

    Obviously a bad idea to start with. Replaced with a
    RegisterSyncSource::InactiveSource() method which creates a real,
    inactive SyncSource instance which can and must be deleted by the
    caller.

    This is a SyncSource API change for backend developers. Instead of
    RegisterSyncSource::InactiveSource, return
    RegisterSyncSource::InactiveSource(). Comparisons against
    RegisterSyncSource::InactiveSource needs to be replaced with a call
    to the new SyncSource::isInactive().

    Long-running backend calls are encouraged to check for events on the
    main glib context (either in a loop or with
    g_main_context_iteration(NULL)) and abort when
    SuspendFlags::getSuspendFlags().getState() returns
    SuspendFlags::ABORT.

  • packagers:

    libgdbussyncevo is now installed as a normal library in /usr/lib,
    even though SyncEvolution is the only user.

    pcrecpp is now a new hard dependency.

Upgrading from release 1.2.x:

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):

   syncevolution --configure \
                 syncFormat=text/x-vcard \
                 mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:

   syncevolution --configure \
                 enableRefreshSync=TRUE \
                 funambol

Upgrading from releases before 1.2:

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information

Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources

i386, lpia and amd64 binaries for Debian-based distributions are available via the “unstable” syncevolution.org repository. Add the following entry to your /apt/source.list, then install “syncevolution-evolution”:

These binaries include the “sync-ui” GTK GUI and were compiled for Ubuntu 8.04 LTS (Hardy). Older distributions like Debian 4.0 (Etch) can no longer be supported with precompiled binaries because of missing libraries, but the source still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in the download directories. In contrast to 0.8.x archives, the new .tar.gz archives have to be unpacked and the content must be moved to /usr, because several files would not be found otherwise.

After installation, follow the getting started steps.

SyncEvolution 1.2.99.1 released

First pre-release of SyncEvolution 1.3. Contains bug fixes that were
not backported to 1.2.x, so upgrading is recommended. For example,
SyncEvolution 1.3 is required for Evolution 3.4, otherwise photos are
not exported properly. Further workarounds for recent changes in
Google CalDAV were added.

Major new features are KDE/Akonadi support in the syncevolution.org
binaries and ActiveSync support (only in the source code). The D-Bus
server and local sync were rewritten considerably, to make the code
cleaner and more robust. The CalDAV backend now also supports tasks
and memos.

Details:

  • phone sync: delete<->delete conflict + phone calendar+todo sync (BMC #23744)

    When deleting an item on phone and locally, the next sync failed with
    ERROR messages about “object not found”. This has several reasons:

    • libsynthesis super data store attempts to read items
      which may or may not exist (triggers ERROR message)
    • it checks for 404 but Evolution backends only return a generic
      database error (causes sync to fail)
  • phone sync: get phone vendor and model from Device ID profile (BMC #736)

    In the past we have relied on the user-modifiable device name to be
    the fingerprint for matching a phone to a template which is unreliable.

    This release changes this in the cases where the phone supports the
    Device ID profile (DIP). If support for DIP is detected, then we
    extract the vendor and product ids and attempt to associate them
    with a product and vendor name by using a newly added lookup table.

    This lookup table has to be maintained manually and depends on
    contributions by users to cover more devices. See
    http://blixtra.org/blog/2011/09/22/syncevolution-needs-you-or-at-least-y…

  • vCalendar 1.0: fixed recurring all-day event support

    vCalendar 1.0 cannot represent all-day events. The workarounds for
    mapping iCalendar 2.0 all-day events into vCalendar 1.0 was
    incomplete, leading to effects like shifting EXDATEs and end
    times.

  • GTK-UI: accept service config with a username again (BMC#23106)

    Suppressing configs with empty username had undesired side effects:
    modifying configs for direct syncing with a device incorrectly
    triggered the same error message, without any means of entering
    a username. The faulty check was removed without replacement.

  • GTK-UI: added GTK 3 version of UI

    When GTK 3 is found during compilation, a GTK 3 version of the
    UI is built. The source code of both is different to avoid
    excessive use of ifdefs. At the moment, both versions offer
    the same features. In the long run, the GTK 3 version will
    replace the GTK 2 version.

  • command line: added refresh/one-way-from-local/remote (BMC #23537)

    The -from-client/server sync modes are confusing because the direction
    of the data exchange depends on which side acts as SyncML server or
    client.

    This release introduces new modes which use -from-local/remote
    instead. The statistics and messages also use these variants
    now. The old modes are still understood, but are declared as “not
    recommended” in the documentation.

  • command line: config and source names are optional (BMC #23783)

    The need to add “foo” and “bar” pseudo config and source names to the
    command line even when all parameters for the operation where
    explicitly specified on the command line was confusing.

    Now it is possible to invoke item operations without the config and
    source name. Names which refer to non-existent configs are still
    accepted, as in previous releases. Typos are handled better by
    producing a detailed error report which includes (as applicable):

    • config doesn’t exist
    • source doesn’t exist or not selected
    • backend property not set

    Because luids used to be positional arguments after and
    , a new –luids keyword is necessary to indicate that the
    ensuing parameters are luids and not and .

  • command line: introduced –print-databases, supported for CalDAV/CardDAV

    Listing databases is now a dedicated operation, instead of being done
    whenever syncevolution was invoked without parameters.

    Advantages:

    • can be combined with property assignments for backends
      which do not work without that additional information, for example
      CalDAV/CardDAV:

          syncevolution --print-databases \
                        backend=[caldav|carddav] \
                        syncURL=... \
                        username=... \
                        password=...
    • can be done for configured sources
  • command line: use both stdout and stderr

    Traditionally, the “syncevolution” command line tool mixed its
    INFO/ERROR/DEBUG messages into the normal stdout. This has the major
    drawback that error messages get lost during operations like
    syncevolution –export – @default addressbook | grep “John Doe”

    Now anything which not the expected result of the operation is
    always sent to stderr. Obviously this includes ERROR messages. INFO
    and DEBUG are harder to decide. Because they usually convey meta
    information about the running operation, they are also sent to
    stderr. The output of running a sync goes to both stdout (summary)
    and stderr (progress).

  • command line: allow setting empty properties

    Due to the way how properties were handled internally, it wasn’t
    possible to explicitly set a property to its default value. Instead
    the property was unset. For example, explicitly setting database= was
    not possible.

    This is necessary for client-test and ActiveSync, because client-test
    needs to know that the testing is expected to run with the default
    databases (something which normally is avoided by overwriting empty
    database properties).

    Now the “is set” state is tracked explicitly in the config storage and
    command line property APIs. Unsetting a property via the command line
    could be implemented with an explicit command line option, but is not
    supported at the moment.

  • command line + local sync: fixed erroneous “Comparison impossible” output.

    “Comparison impossible” was incorrectly printed after a successful
    comparison on the target side of local sync.

  • synccompare: shorter data dump of PHOTO

    A full comparison of the base64 PHOTO data can be very long.
    Now some key characteristics of the PHOTO data (number of
    characters in base64 encoding, number of bytes in decoded
    data, md5sum of decoded data) are printed instead.

    That way, unintended changes of the data (different encoding,
    different content) should still be found while testing and
    added/removed photos are nicely visible in synccompare diffs.

  • synccompare: fixed output for byte-identical duplicates

    If database dumps contained byte-identical duplicates, they
    were treated as a single item on the left side of a comparison.
    This caused erroneous “added” entries on the right side.

  • secure password storage: usage of GNOME Keyring vs. KDE KWallet configurable

    Automatically detecting KDE users is not possible at the
    moment. Instead KDE users have to manually set the new “keyring”
    global config property to “KDE” (case insensitive) if the
    SyncEvolution installation supports both, because GNOME Keyring is the
    default to avoid surprises for traditional users. If only KWallet
    support is enabled, then this is not necessary.

    “GNOME” and “true/false/1/0/yes/no” can also be set. This has the
    advantage that keyring usage can be enabled permanently for the
    command line in –daemon=no mode; normally keyrings are not used in
    that mode because accessing them can bring up UI dialogs.

    It also becomes possible to disable keyring usage in syncevo-dbus-server,
    something which couldn’t be done before.

    The –keyring command line option is still supported, as an alias for
    “[--sync-property] keyring=”. The default value for –keyring
    is true, to match the traditional behavior. In contrast to other sync
    properties, setting “keyring” does not require an explicit –run
    parameter. Again this is done to mirror traditional usage.

  • Evolution: always create databases (PTCOM-113)

    Always try to create address book or calendar database, because even
    if there is a source there’s no guarantee that the actual database
    was created already; the original logic for only setting this when
    explicitly requesting a new database therefore failed in some cases.

    This problem affected users who had never created anything locally
    and wanted to use SyncEvolution to migrate their data. Now that
    works without having to create dummy entries first.

  • Evolution contacts: changed default sync format to vCard 3.0

    vCard 3.0 is the better default because it has saner encoding
    rules and defines more properties, thus avoiding the need for
    non-standard extensions. However, Mobical has problems with
    the new default. See upgrade instructions below.

  • D-Bus server: made notification verbosity configurable with “notifyLevel”

    The new “notifyLevel” per-peer configuration option allows users to
    control how many desktop notifications the D-Bus server produces while
    executing an automatic sync:

    0 – suppress all notifications
    1 – show only errors
    2 – show information about changes and errors (in practice currently the same as level 3)
    3 – show all notifications, including starting a sync (default)

  • CalDAV: updated Google workarounds

    Google started sending empty items (VCALENDAR with no VEVENT inside)
    which cannot be removed. SyncEvolution 1.3 ignores such items.

    The workaround for a 404 from Google Calendar for a GET (sending a
    REPORT request matching the item’s UID) was broken: first, processing
    the result ended up calling the unset responseEnd boost function
    pointer, which caused the request to fail. Second, getting multiple
    items wasn’t handled (data from all items concatenated together was
    used).

    That can happen in the somewhat unlike case that some items have a UID
    which is a complete superset of the requested UID – not realistic in
    real life, but happens during testing.

  • WebDAV: bridge with SyncML

    Now a peer accessed via SyncML can read/write data stored in a
    CalDAV/CardDAV server directly. This can be used to connect a device
    which only supports SyncML to a CalDAV/CardDAV server, or sync data
    between a SyncML server and a CalDAV/CardDAV server. See “CalDAV and
    CardDAV” in the README for details.

  • WebDAV: improved –configure

    Added INFO output about checking sources. This helps with WebDAV when
    the server cannot be contacted (dead, misconfigured) because otherwise
    there would be no indication at all why the –configure operation
    seems to hang.

    Here is some example output, including aborting:

      $ syncevolution --configure --template webdav \
                      syncURL=http://192.168.1.100:9000/ \
                      username=foo password=bar retryDuration=2s \
                      target-config@webdav-temp
      [INFO] creating configuration target-config@webdav-temp
      [INFO] addressbook: looking for databases...
      [INFO] addressbook: no database to synchronize
      [INFO] calendar: looking for databases...
      [INFO] calendar: no database to synchronize
      [INFO] memo: looking for databases...
      [INFO] memo: no database to synchronize
      [INFO] todo: looking for databases...
      [INFO] todo: no database to synchronize

    It timed out fairly quickly here because of the retryDuration=2s. That
    also gets placed in the resulting config, which is probably not desired.

    Aborting the operation is now supported:

  $ syncevolution --configure \
                  --template webdav \
                  syncURL=http://192.168.1.100:9000/ \
                  username=foo password=bar \
                  target-config@webdav-temp
  [INFO] creating configuration target-config@webdav-temp
  [INFO] addressbook: looking for databases...
  ^C[INFO] Asking to suspend...
  [INFO] Press CTRL-C again quickly (within 2s) to stop immediately (can cause problems in the future!)
  ^C[INFO] Aborting immediately ...
  [ERROR] error code from SyncEvolution aborted on behalf of user (local, status 20017): aborting as requested by user

It would be good to make the CTRL-C handling code aware that it can
abort immediately instead of doing the intermediate “asking to suspend”
step, which only makes sense for sync sessions.

  • WebDAV: support tasks and memos (BMC #24893)

    The new backend property values “CalDAVTodo” and “CalDAVJournal”
    select tasks resp. memos stored in a CalDAV collection. “CalDAV”
    continues to select events.

    Events, tasks and journals can be mixed in the same resource (=
    URL). However, this is less efficient than storing them separately.

    A good CalDAV server allows filtering items by type, and SyncEvolution
    uses that. However, it was found that Radicale 0.7 ignores this
    filtering, which could have led to data loss (SyncEvolution asks for
    all VTODOs in preparation for a “delete all items” operation in a
    “CalDAVTodo” source, gets also VJOURNALs, then deletes them).

    Therefore SyncEvolution plays it safe and downloads the VTODO and
    VJOURNAL data to double-check that it is working on the right items.
    This causes additional traffic for well-behaving servers; currently
    it cannot be turned off.

    Tasks are exchanged as vCalendar 1.0 or iCalendar 2.0 VJOURNAL.
    Memos are exchanged as VTODO or plain text. The logic for storing
    incoming plain text is slightly different compared to the way how
    the EDS memo backend did it: instead of copying the first line
    from the text into the summary, it is now moved. In other words,
    the first line gets stripped. The change is primarily technically
    motivated; both approaches have pros and cons.

  • WebDAV: improved Radicale support

    Radicale > 0.7 will return status 200 for delete requests;
    is now treated like 204 by SyncEvolution. 412 ‘Preconditiona Failed’
    when asking to delete an already removed item is treated like
    the more common 404 ‘not found’. Same with 410 ‘gone’ instead
    of 404 when trying to read a non-existent item.

  • file backend: more flexible sync support for memos

    The databaseFormat=text/calendar for memos did not support
    synchronizing as plain text. When using the new
    databaseFormat=text/calendar+plain, vCalendar/iCalendar/plain text
    are all valid sync formats; the storage is iCalendar 2.0
    VJOURNAL in all cases.

  • WebDAV: avoid potential crash during database detection

    When a server responds to a PROPFIND for a path with results for some
    other path, then SyncEvolution crashed during the search for the
    default calendar or address book because of a bug in the code which
    was meant to handle that kind of response. Apparently Yahoo Calendar
    did that. Now seen again in combination with Radicale 0.6.4.

    In general, the code was made more robust to cope with bugs in
    Radicale 0.6.4. Later Radicale versions fixed these issues and also
    worked with SyncEvolution 1.2.2 without client-side workarounds.

  • WebDAV: better path normalization

    “syncURL” and “database” properties had to end in a trailing slash,
    otherwise items were not found (404 errors). Now the necessary slash
    is added automatically.

  • Funambol: avoid slow syncs in refresh from server

    libsynthesis has traditionally implemented “refresh-from-server” as
    “delete local data” plus “slow” sync. This is more compatible, because
    some servers (like Google) do not support “refresh-from-server”.

    But it has the downside that the server cannot know that the client
    won’t send any data, and Funambol’s OneMedia now only allows one slow
    sync before blocking the next one for a certain period of time. This is
    done to prevent excessive resource usage by badly behaving clients.

    To accomodate both kinds of servers, the new “enableRefreshSync”
    sync property can be set set to explicitly allow the usage of
    the “refresh-from-server” sync mode. It’s off by default. The Funambol
    template has it turned on, existing configs must be updated manually
    (see upgrading comments below).

  • Curl transport: support SSLServerCertificates=

    When the setting refers to a directory, then CURLOPT_CAINFO doesn’t
    work (must be a file). Check this and use CURLOPT_CAPATH instead.

    Caveat: there are some comments in the API documentation about “NSS
    enabled libcurl” which supports a directory in
    CURLOPT_CAINFO. Hopefully providing an explicit path in CURLOPT_CAPATH
    also works in that configuration.

  • code cleanup + rewrite: syncing done in separate process

    syncevo-dbus-server now runs syncing in a separate process. Local
    sync also uses a second helper process. This makes the D-Bus server
    more responsive via D-Bus (no more blocking operations) and
    minimizes the effect of bugs in code involved with syncing
    (backends, system libraries, etc.).

    In the long term this restructuring will also allow more advanced
    features, like monitoring local or remote storage for changes.

  • SyncEvolution <-> SyncEvolution sync: multiple cycles per session

    SyncML only allows one send/receive cycle per session. There are cases
    (for example, client side merges data that a dumber server failed to
    match correctly) where client and server are still out of sync at
    the end of a cycle. When SyncEvolution syncs with another SyncEvolution
    instance (locally or remotely), both sides detect that the peer
    can continue syncing in the same session and start over automatically
    when needed. Previously the user had to start another sync session manually.

    To the user this is shown as “number of cycles” in a sync session
    in the sync report. “Restart” is the process of entering a new cycle.

    The cycles are also visible in the command line output as multiple
    INFO lines:

    [INFO] eds_contact: starting first time sync from client (peer is server)
    [INFO] creating complete data backup of source eds_contact before sync (enabled with dumpData and needed for prin
    Local data changes to be applied during synchronization:
    *** eds_contact ***
    no changes

    [INFO] eds_contact: sent 1/1
    [INFO] eds_contact: started
    [INFO] eds_contact: first time sync done successfully
    [INFO] eds_contact: starting normal sync from client (peer is server)         <===
    [INFO] eds_contact: started                                                   <===
    [INFO] eds_contact: 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 |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
    |   eds_contact |  0  |  0  |  0  |  0  |  1  |  0  |  0  |  0  |  0  |
    |   refresh-from-local, 2 cycles, 0 KB sent by client, 0 KB received  |
                            ^^^^^^^^
    |   item(s) in database backup: 1 before sync, 1 after it             |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
    |          start Tue Feb  7 17:07:49 2012, duration 0:03min           |
    |               synchronization completed successfully                |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+

  • SyncEvolution <-> SyncEvolution sync: negotiate UID support via SyncCap (BMC #22783)

    The semantic of UID/RECURRENCE-ID in calendar data is now tracked
    per data store involved in a sync. If full iCalendar 2.0 semantic
    (= IDs are globally unique) is guaranteed, then pairs are found
    based on these IDs. Otherwise pairs must be found by looking at
    item attributes.

    Previously a hack was used to detect this kind of support (any kind
    of SyncEvolution instance was assumed to support it, although some
    backends do not).

  • syncevolution.org packages: fixed D-Bus server autostart in .deb and .rpm packages

    syncevo-dbus-server wasn’t started automatically as part of a user
    session because /etc/xdg/autostart/syncevo-dbus-server.desktop wasn’t
    included in the packages. This broke auto syncing after a session
    restart (required manually starting SyncEvolution).

  • syncevolution.org packages: support KDE

    The traditional “syncevolution-evolution” package was
    replaced with “syncevolution-bundle”. A meta “syncevolution-evolution”
    package depends on it, to support seamless updates for users who have
    “syncevolution-evolution” installed.

    Binary dependencies of the main .deb are ignored for backends
    because loading them is optional. The new “syncevolution-kde”
    package has the right dependencies for KDE/Akonadi, while
    “syncevolution-evolution” mostly just lists standard libs
    if the “EDS compatibility” mode is used, where libebook/libecal
    are loaded dynamically.

    Platform specific code (GNOME keyring, KDE wallet) was moved into
    loadable, optional modules, to allow installation of the SyncEvolution
    bundle without forcing the installation of unused system components.

  • D-Bus: use GIO D-Bus instead of libdbus if available

    When compiling from source, the more modern GIO D-Bus is used instead
    of libdbus if available and recent enough (>= 2.30). syncevolution.org
    binaries still use libdbus, to stay compatible with older Linux
    distros.

  • several minor bug fixes

    syncevo-dbus-server now runs under valgrind in the nightly testing,
    plus several more test scenarios were added. This helped to find
    and fix various minor memory handling issues.

  • developers: backend API changes

    beginSync/endSync() (aka m_startDataRead/m_endDataWrite) may now be
    called multiple times per SyncSource instance life cycle. SyncSources
    derived from TrackingSyncSource should work without changes. Use the
    Client::Source::*::testChangesMultiCycles test to check whether your
    backend supports this correctly.

    Reading and deleting must throw a 404 status exception when an item
    is not found. The Client::Source::::404 tests cover this.

    The special semantic of the former RegisterSyncSource::InactiveSource
    (invalid pointer of value 1) caused bugs, like using it in
    –print-databases (=> segfault) or not being able to store the result
    of a createSource() directly in a smart pointer (=> potential leak in
    SyncSource::createSource()).

    Obviously a bad idea to start with. Replaced with a
    RegisterSyncSource::InactiveSource() method which creates a real,
    inactive SyncSource instance which can and must be deleted by the
    caller.

    This is a SyncSource API change for backend developers. Instead of
    RegisterSyncSource::InactiveSource, return
    RegisterSyncSource::InactiveSource(). Comparisons against
    RegisterSyncSource::InactiveSource needs to be replaced with a call
    to the new SyncSource::isInactive().

    Long-running backend calls are encouraged to check for events on the
    main glib context (either in a loop or with
    g_main_context_iteration(NULL)) and abort when
    SuspendFlags::getSuspendFlags().getState() returns
    SuspendFlags::ABORT.

  • packagers:

    libgdbussyncevo is now installed as a normal library in /usr/lib,
    even though SyncEvolution is the only user.

    pcrecpp is now a new hard dependency.

Upgrading from release 1.2.x:

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):

   syncevolution --configure \
                 syncFormat=text/x-vcard \
                 mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:

   syncevolution --configure \
                 enableRefreshSync=TRUE \
                 funambol

Upgrading from releases before 1.2:

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information

Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources

i386, lpia and amd64 binaries for Debian-based distributions are available via the “unstable” syncevolution.org repository. Add the following entry to your /apt/source.list, then install “syncevolution-evolution”:

These binaries include the “sync-ui” GTK GUI and were compiled for Ubuntu 8.04 LTS (Hardy). Older distributions like Debian 4.0 (Etch) can no longer be supported with precompiled binaries because of missing libraries, but the source still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in the download directories. In contrast to 0.8.x archives, the new .tar.gz archives have to be unpacked and the content must be moved to /usr, because several files would not be found otherwise.

After installation, follow the getting started steps.

SyncEvolution 1.2.99.1 released

First pre-release of SyncEvolution 1.3. Contains bug fixes that were
not backported to 1.2.x, so upgrading is recommended. For example,
SyncEvolution 1.3 is required for Evolution 3.4, otherwise photos are
not exported properly. Further workarounds for recent changes in
Google CalDAV were added.

Major new features are KDE/Akonadi support in the syncevolution.org
binaries and ActiveSync support (only in the source code). The D-Bus
server and local sync were rewritten considerably, to make the code
cleaner and more robust. The CalDAV backend now also supports tasks
and memos.

Details:

  • phone sync: delete<->delete conflict + phone calendar+todo sync (BMC #23744)

    When deleting an item on phone and locally, the next sync failed with
    ERROR messages about “object not found”. This has several reasons:

    • libsynthesis super data store attempts to read items
      which may or may not exist (triggers ERROR message)
    • it checks for 404 but Evolution backends only return a generic
      database error (causes sync to fail)
  • phone sync: get phone vendor and model from Device ID profile (BMC #736)

    In the past we have relied on the user-modifiable device name to be
    the fingerprint for matching a phone to a template which is unreliable.

    This release changes this in the cases where the phone supports the
    Device ID profile (DIP). If support for DIP is detected, then we
    extract the vendor and product ids and attempt to associate them
    with a product and vendor name by using a newly added lookup table.

    This lookup table has to be maintained manually and depends on
    contributions by users to cover more devices. See
    http://blixtra.org/blog/2011/09/22/syncevolution-needs-you-or-at-least-y…

  • vCalendar 1.0: fixed recurring all-day event support

    vCalendar 1.0 cannot represent all-day events. The workarounds for
    mapping iCalendar 2.0 all-day events into vCalendar 1.0 was
    incomplete, leading to effects like shifting EXDATEs and end
    times.

  • GTK-UI: accept service config with a username again (BMC#23106)

    Suppressing configs with empty username had undesired side effects:
    modifying configs for direct syncing with a device incorrectly
    triggered the same error message, without any means of entering
    a username. The faulty check was removed without replacement.

  • GTK-UI: added GTK 3 version of UI

    When GTK 3 is found during compilation, a GTK 3 version of the
    UI is built. The source code of both is different to avoid
    excessive use of ifdefs. At the moment, both versions offer
    the same features. In the long run, the GTK 3 version will
    replace the GTK 2 version.

  • command line: added refresh/one-way-from-local/remote (BMC #23537)

    The -from-client/server sync modes are confusing because the direction
    of the data exchange depends on which side acts as SyncML server or
    client.

    This release introduces new modes which use -from-local/remote
    instead. The statistics and messages also use these variants
    now. The old modes are still understood, but are declared as “not
    recommended” in the documentation.

  • command line: config and source names are optional (BMC #23783)

    The need to add “foo” and “bar” pseudo config and source names to the
    command line even when all parameters for the operation where
    explicitly specified on the command line was confusing.

    Now it is possible to invoke item operations without the config and
    source name. Names which refer to non-existent configs are still
    accepted, as in previous releases. Typos are handled better by
    producing a detailed error report which includes (as applicable):

    • config doesn’t exist
    • source doesn’t exist or not selected
    • backend property not set

    Because luids used to be positional arguments after and
    , a new –luids keyword is necessary to indicate that the
    ensuing parameters are luids and not and .

  • command line: introduced –print-databases, supported for CalDAV/CardDAV

    Listing databases is now a dedicated operation, instead of being done
    whenever syncevolution was invoked without parameters.

    Advantages:

    • can be combined with property assignments for backends
      which do not work without that additional information, for example
      CalDAV/CardDAV:

          syncevolution --print-databases \
                        backend=[caldav|carddav] \
                        syncURL=... \
                        username=... \
                        password=...
    • can be done for configured sources
  • command line: use both stdout and stderr

    Traditionally, the “syncevolution” command line tool mixed its
    INFO/ERROR/DEBUG messages into the normal stdout. This has the major
    drawback that error messages get lost during operations like
    syncevolution –export – @default addressbook | grep “John Doe”

    Now anything which not the expected result of the operation is
    always sent to stderr. Obviously this includes ERROR messages. INFO
    and DEBUG are harder to decide. Because they usually convey meta
    information about the running operation, they are also sent to
    stderr. The output of running a sync goes to both stdout (summary)
    and stderr (progress).

  • command line: allow setting empty properties

    Due to the way how properties were handled internally, it wasn’t
    possible to explicitly set a property to its default value. Instead
    the property was unset. For example, explicitly setting database= was
    not possible.

    This is necessary for client-test and ActiveSync, because client-test
    needs to know that the testing is expected to run with the default
    databases (something which normally is avoided by overwriting empty
    database properties).

    Now the “is set” state is tracked explicitly in the config storage and
    command line property APIs. Unsetting a property via the command line
    could be implemented with an explicit command line option, but is not
    supported at the moment.

  • command line + local sync: fixed erroneous “Comparison impossible” output.

    “Comparison impossible” was incorrectly printed after a successful
    comparison on the target side of local sync.

  • synccompare: shorter data dump of PHOTO

    A full comparison of the base64 PHOTO data can be very long.
    Now some key characteristics of the PHOTO data (number of
    characters in base64 encoding, number of bytes in decoded
    data, md5sum of decoded data) are printed instead.

    That way, unintended changes of the data (different encoding,
    different content) should still be found while testing and
    added/removed photos are nicely visible in synccompare diffs.

  • synccompare: fixed output for byte-identical duplicates

    If database dumps contained byte-identical duplicates, they
    were treated as a single item on the left side of a comparison.
    This caused erroneous “added” entries on the right side.

  • secure password storage: usage of GNOME Keyring vs. KDE KWallet configurable

    Automatically detecting KDE users is not possible at the
    moment. Instead KDE users have to manually set the new “keyring”
    global config property to “KDE” (case insensitive) if the
    SyncEvolution installation supports both, because GNOME Keyring is the
    default to avoid surprises for traditional users. If only KWallet
    support is enabled, then this is not necessary.

    “GNOME” and “true/false/1/0/yes/no” can also be set. This has the
    advantage that keyring usage can be enabled permanently for the
    command line in –daemon=no mode; normally keyrings are not used in
    that mode because accessing them can bring up UI dialogs.

    It also becomes possible to disable keyring usage in syncevo-dbus-server,
    something which couldn’t be done before.

    The –keyring command line option is still supported, as an alias for
    “[--sync-property] keyring=”. The default value for –keyring
    is true, to match the traditional behavior. In contrast to other sync
    properties, setting “keyring” does not require an explicit –run
    parameter. Again this is done to mirror traditional usage.

  • Evolution: always create databases (PTCOM-113)

    Always try to create address book or calendar database, because even
    if there is a source there’s no guarantee that the actual database
    was created already; the original logic for only setting this when
    explicitly requesting a new database therefore failed in some cases.

    This problem affected users who had never created anything locally
    and wanted to use SyncEvolution to migrate their data. Now that
    works without having to create dummy entries first.

  • Evolution contacts: changed default sync format to vCard 3.0

    vCard 3.0 is the better default because it has saner encoding
    rules and defines more properties, thus avoiding the need for
    non-standard extensions. However, Mobical has problems with
    the new default. See upgrade instructions below.

  • D-Bus server: made notification verbosity configurable with “notifyLevel”

    The new “notifyLevel” per-peer configuration option allows users to
    control how many desktop notifications the D-Bus server produces while
    executing an automatic sync:

    0 – suppress all notifications
    1 – show only errors
    2 – show information about changes and errors (in practice currently the same as level 3)
    3 – show all notifications, including starting a sync (default)

  • CalDAV: updated Google workarounds

    Google started sending empty items (VCALENDAR with no VEVENT inside)
    which cannot be removed. SyncEvolution 1.3 ignores such items.

    The workaround for a 404 from Google Calendar for a GET (sending a
    REPORT request matching the item’s UID) was broken: first, processing
    the result ended up calling the unset responseEnd boost function
    pointer, which caused the request to fail. Second, getting multiple
    items wasn’t handled (data from all items concatenated together was
    used).

    That can happen in the somewhat unlike case that some items have a UID
    which is a complete superset of the requested UID – not realistic in
    real life, but happens during testing.

  • WebDAV: bridge with SyncML

    Now a peer accessed via SyncML can read/write data stored in a
    CalDAV/CardDAV server directly. This can be used to connect a device
    which only supports SyncML to a CalDAV/CardDAV server, or sync data
    between a SyncML server and a CalDAV/CardDAV server. See “CalDAV and
    CardDAV” in the README for details.

  • WebDAV: improved –configure

    Added INFO output about checking sources. This helps with WebDAV when
    the server cannot be contacted (dead, misconfigured) because otherwise
    there would be no indication at all why the –configure operation
    seems to hang.

    Here is some example output, including aborting:

      $ syncevolution --configure --template webdav \
                      syncURL=http://192.168.1.100:9000/ \
                      username=foo password=bar retryDuration=2s \
                      target-config@webdav-temp
      [INFO] creating configuration target-config@webdav-temp
      [INFO] addressbook: looking for databases...
      [INFO] addressbook: no database to synchronize
      [INFO] calendar: looking for databases...
      [INFO] calendar: no database to synchronize
      [INFO] memo: looking for databases...
      [INFO] memo: no database to synchronize
      [INFO] todo: looking for databases...
      [INFO] todo: no database to synchronize

    It timed out fairly quickly here because of the retryDuration=2s. That
    also gets placed in the resulting config, which is probably not desired.

    Aborting the operation is now supported:

  $ syncevolution --configure \
                  --template webdav \
                  syncURL=http://192.168.1.100:9000/ \
                  username=foo password=bar \
                  target-config@webdav-temp
  [INFO] creating configuration target-config@webdav-temp
  [INFO] addressbook: looking for databases...
  ^C[INFO] Asking to suspend...
  [INFO] Press CTRL-C again quickly (within 2s) to stop immediately (can cause problems in the future!)
  ^C[INFO] Aborting immediately ...
  [ERROR] error code from SyncEvolution aborted on behalf of user (local, status 20017): aborting as requested by user

It would be good to make the CTRL-C handling code aware that it can
abort immediately instead of doing the intermediate “asking to suspend”
step, which only makes sense for sync sessions.

  • WebDAV: support tasks and memos (BMC #24893)

    The new backend property values “CalDAVTodo” and “CalDAVJournal”
    select tasks resp. memos stored in a CalDAV collection. “CalDAV”
    continues to select events.

    Events, tasks and journals can be mixed in the same resource (=
    URL). However, this is less efficient than storing them separately.

    A good CalDAV server allows filtering items by type, and SyncEvolution
    uses that. However, it was found that Radicale 0.7 ignores this
    filtering, which could have led to data loss (SyncEvolution asks for
    all VTODOs in preparation for a “delete all items” operation in a
    “CalDAVTodo” source, gets also VJOURNALs, then deletes them).

    Therefore SyncEvolution plays it safe and downloads the VTODO and
    VJOURNAL data to double-check that it is working on the right items.
    This causes additional traffic for well-behaving servers; currently
    it cannot be turned off.

    Tasks are exchanged as vCalendar 1.0 or iCalendar 2.0 VJOURNAL.
    Memos are exchanged as VTODO or plain text. The logic for storing
    incoming plain text is slightly different compared to the way how
    the EDS memo backend did it: instead of copying the first line
    from the text into the summary, it is now moved. In other words,
    the first line gets stripped. The change is primarily technically
    motivated; both approaches have pros and cons.

  • WebDAV: improved Radicale support

    Radicale > 0.7 will return status 200 for delete requests;
    is now treated like 204 by SyncEvolution. 412 ‘Preconditiona Failed’
    when asking to delete an already removed item is treated like
    the more common 404 ‘not found’. Same with 410 ‘gone’ instead
    of 404 when trying to read a non-existent item.

  • file backend: more flexible sync support for memos

    The databaseFormat=text/calendar for memos did not support
    synchronizing as plain text. When using the new
    databaseFormat=text/calendar+plain, vCalendar/iCalendar/plain text
    are all valid sync formats; the storage is iCalendar 2.0
    VJOURNAL in all cases.

  • WebDAV: avoid potential crash during database detection

    When a server responds to a PROPFIND for a path with results for some
    other path, then SyncEvolution crashed during the search for the
    default calendar or address book because of a bug in the code which
    was meant to handle that kind of response. Apparently Yahoo Calendar
    did that. Now seen again in combination with Radicale 0.6.4.

    In general, the code was made more robust to cope with bugs in
    Radicale 0.6.4. Later Radicale versions fixed these issues and also
    worked with SyncEvolution 1.2.2 without client-side workarounds.

  • WebDAV: better path normalization

    “syncURL” and “database” properties had to end in a trailing slash,
    otherwise items were not found (404 errors). Now the necessary slash
    is added automatically.

  • Funambol: avoid slow syncs in refresh from server

    libsynthesis has traditionally implemented “refresh-from-server” as
    “delete local data” plus “slow” sync. This is more compatible, because
    some servers (like Google) do not support “refresh-from-server”.

    But it has the downside that the server cannot know that the client
    won’t send any data, and Funambol’s OneMedia now only allows one slow
    sync before blocking the next one for a certain period of time. This is
    done to prevent excessive resource usage by badly behaving clients.

    To accomodate both kinds of servers, the new “enableRefreshSync”
    sync property can be set set to explicitly allow the usage of
    the “refresh-from-server” sync mode. It’s off by default. The Funambol
    template has it turned on, existing configs must be updated manually
    (see upgrading comments below).

  • Curl transport: support SSLServerCertificates=

    When the setting refers to a directory, then CURLOPT_CAINFO doesn’t
    work (must be a file). Check this and use CURLOPT_CAPATH instead.

    Caveat: there are some comments in the API documentation about “NSS
    enabled libcurl” which supports a directory in
    CURLOPT_CAINFO. Hopefully providing an explicit path in CURLOPT_CAPATH
    also works in that configuration.

  • code cleanup + rewrite: syncing done in separate process

    syncevo-dbus-server now runs syncing in a separate process. Local
    sync also uses a second helper process. This makes the D-Bus server
    more responsive via D-Bus (no more blocking operations) and
    minimizes the effect of bugs in code involved with syncing
    (backends, system libraries, etc.).

    In the long term this restructuring will also allow more advanced
    features, like monitoring local or remote storage for changes.

  • SyncEvolution <-> SyncEvolution sync: multiple cycles per session

    SyncML only allows one send/receive cycle per session. There are cases
    (for example, client side merges data that a dumber server failed to
    match correctly) where client and server are still out of sync at
    the end of a cycle. When SyncEvolution syncs with another SyncEvolution
    instance (locally or remotely), both sides detect that the peer
    can continue syncing in the same session and start over automatically
    when needed. Previously the user had to start another sync session manually.

    To the user this is shown as “number of cycles” in a sync session
    in the sync report. “Restart” is the process of entering a new cycle.

    The cycles are also visible in the command line output as multiple
    INFO lines:

    [INFO] eds_contact: starting first time sync from client (peer is server)
    [INFO] creating complete data backup of source eds_contact before sync (enabled with dumpData and needed for prin
    Local data changes to be applied during synchronization:
    *** eds_contact ***
    no changes

    [INFO] eds_contact: sent 1/1
    [INFO] eds_contact: started
    [INFO] eds_contact: first time sync done successfully
    [INFO] eds_contact: starting normal sync from client (peer is server)         <===
    [INFO] eds_contact: started                                                   <===
    [INFO] eds_contact: 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 |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
    |   eds_contact |  0  |  0  |  0  |  0  |  1  |  0  |  0  |  0  |  0  |
    |   refresh-from-local, 2 cycles, 0 KB sent by client, 0 KB received  |
                            ^^^^^^^^
    |   item(s) in database backup: 1 before sync, 1 after it             |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
    |          start Tue Feb  7 17:07:49 2012, duration 0:03min           |
    |               synchronization completed successfully                |
    +---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+

  • SyncEvolution <-> SyncEvolution sync: negotiate UID support via SyncCap (BMC #22783)

    The semantic of UID/RECURRENCE-ID in calendar data is now tracked
    per data store involved in a sync. If full iCalendar 2.0 semantic
    (= IDs are globally unique) is guaranteed, then pairs are found
    based on these IDs. Otherwise pairs must be found by looking at
    item attributes.

    Previously a hack was used to detect this kind of support (any kind
    of SyncEvolution instance was assumed to support it, although some
    backends do not).

  • syncevolution.org packages: fixed D-Bus server autostart in .deb and .rpm packages

    syncevo-dbus-server wasn’t started automatically as part of a user
    session because /etc/xdg/autostart/syncevo-dbus-server.desktop wasn’t
    included in the packages. This broke auto syncing after a session
    restart (required manually starting SyncEvolution).

  • syncevolution.org packages: support KDE

    The traditional “syncevolution-evolution” package was
    replaced with “syncevolution-bundle”. A meta “syncevolution-evolution”
    package depends on it, to support seamless updates for users who have
    “syncevolution-evolution” installed.

    Binary dependencies of the main .deb are ignored for backends
    because loading them is optional. The new “syncevolution-kde”
    package has the right dependencies for KDE/Akonadi, while
    “syncevolution-evolution” mostly just lists standard libs
    if the “EDS compatibility” mode is used, where libebook/libecal
    are loaded dynamically.

    Platform specific code (GNOME keyring, KDE wallet) was moved into
    loadable, optional modules, to allow installation of the SyncEvolution
    bundle without forcing the installation of unused system components.

  • D-Bus: use GIO D-Bus instead of libdbus if available

    When compiling from source, the more modern GIO D-Bus is used instead
    of libdbus if available and recent enough (>= 2.30). syncevolution.org
    binaries still use libdbus, to stay compatible with older Linux
    distros.

  • several minor bug fixes

    syncevo-dbus-server now runs under valgrind in the nightly testing,
    plus several more test scenarios were added. This helped to find
    and fix various minor memory handling issues.

  • developers: backend API changes

    beginSync/endSync() (aka m_startDataRead/m_endDataWrite) may now be
    called multiple times per SyncSource instance life cycle. SyncSources
    derived from TrackingSyncSource should work without changes. Use the
    Client::Source::*::testChangesMultiCycles test to check whether your
    backend supports this correctly.

    Reading and deleting must throw a 404 status exception when an item
    is not found. The Client::Source::::404 tests cover this.

    The special semantic of the former RegisterSyncSource::InactiveSource
    (invalid pointer of value 1) caused bugs, like using it in
    –print-databases (=> segfault) or not being able to store the result
    of a createSource() directly in a smart pointer (=> potential leak in
    SyncSource::createSource()).

    Obviously a bad idea to start with. Replaced with a
    RegisterSyncSource::InactiveSource() method which creates a real,
    inactive SyncSource instance which can and must be deleted by the
    caller.

    This is a SyncSource API change for backend developers. Instead of
    RegisterSyncSource::InactiveSource, return
    RegisterSyncSource::InactiveSource(). Comparisons against
    RegisterSyncSource::InactiveSource needs to be replaced with a call
    to the new SyncSource::isInactive().

    Long-running backend calls are encouraged to check for events on the
    main glib context (either in a loop or with
    g_main_context_iteration(NULL)) and abort when
    SuspendFlags::getSuspendFlags().getState() returns
    SuspendFlags::ABORT.

  • packagers:

    libgdbussyncevo is now installed as a normal library in /usr/lib,
    even though SyncEvolution is the only user.

    pcrecpp is now a new hard dependency.

Upgrading from release 1.2.x:

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):

   syncevolution --configure \
                 syncFormat=text/x-vcard \
                 mobical addressbook

The Funambol template explicitly enables usage of the
“refresh-from-server” sync mode to avoid getting throttled with 417
‘retry later’ errors. The same must be added to existing configs
manually:

   syncevolution --configure \
                 enableRefreshSync=TRUE \
                 funambol

Upgrading from releases before 1.2:

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information

Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources

i386, lpia and amd64 binaries for Debian-based distributions are available via the “unstable” syncevolution.org repository. Add the following entry to your /apt/source.list, then install “syncevolution-evolution”:

These binaries include the “sync-ui” GTK GUI and were compiled for Ubuntu 8.04 LTS (Hardy). Older distributions like Debian 4.0 (Etch) can no longer be supported with precompiled binaries because of missing libraries, but the source still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in the download directories. In contrast to 0.8.x archives, the new .tar.gz archives have to be unpacked and the content must be moved to /usr, because several files would not be found otherwise.

After installation, follow the getting started steps.

SyncEvolution 1.2.2 released

Maintenance release with various bug fixes.

* syncevo-dbus-server + ConnMan: fixed “online” detection (BMC #21541, BMC #24587)

SyncEvolution did not recognize any cellular connectivity as
suitable for syncing. The strict check for certain “connected
technology” is unnecessary, anything which makes the computer
“online” should be good enough. So now it just uses the ConnMan
“State” property.

Additional benefit: will continue to work with ConnMan 1.0, which
won’t have the “ConnectedTechnologies” property anymore.

The Bluetooth available check was also (incorrectly) using the
ConnMan API. Now asssume that OBEX/Bluetooth is always available.

  • automatic backups: added INFO messages and fixed dumpData/printChanges (BMC #24619)

    Point out that backups are created (user might be unaware otherwise
    and wonder about the delay), explain why (so that users know how to
    turn it off).

    Turning these backups off with dumpData=0 printChanges=0 had to be
    fixed, backups were always written previously.

  • EDS compatibility: bumped version check for EDS 3.2

    SyncEvolution is known to work with EDS 3.2. Therefore use the
    libebook/ecal/edataserver libs from 3.2 if available, without
    warnings in the –version output. Also happens with inconsistent
    distro setups where the old libs are available and would have been
    prefered by SyncEvolution 1.2.1 even though the old libs no longer
    work with EDS 3.2.

  • GTK-UI: do not accept service config without a username (BMC #23106)

    Instead of creating such a config, an error dialog is shown.

  • GTK-UI: updated translations

  • fixed various compile issues, primarily on Fedora Core 17
    (unistd.h/ssize_t, invoking syncevolution during compilation,
    missing src/dbus/qt/configure-sub.in)

    SyncEvolution is known to not compile with Bluez 4.97. A patch
    for Bluez header files is needed to make them work in C++ again,
    see http://thread.gmane.org/gmane.linux.bluez.kernel/20364

Upgrading from releases before 1.2

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Release 1.2
automatically migrates configurations. The old configurations
will still be available (see “syncevolution –print-configs”) but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information

Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources

i386, lpia and amd64 binaries for Debian-based distributions are available via the “stable” syncevolution.org repository. Add the following entry to your /apt/source.list, then install “syncevolution-evolution”:

These binaries include the “sync-ui” GTK GUI and were compiled for Ubuntu 8.04 LTS (Hardy). Older distributions like Debian 4.0 (Etch) can no longer be supported with precompiled binaries because of missing libraries, but the source still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in the download directories. In contrast to 0.8.x archives, the 1.0 .tar.gz archives have to be unpacked and the content must be moved to /usr, because several files would not be found otherwise.

After installation, follow the getting started steps.