[SyncEvolution] SyncEvolution 1.5.1 released
by Patrick Ohly
About SyncEvolution
===================
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 Maemo (Nokia N900, N9) and Sailfish OS (Jolla
phone).
About 1.5.1
===========
Maintenance release. Binaries now also get compiled for Debian 8.0
"Jessie".
Details:
* avoid time zone issue with Funambol server
The Funambol iCalendar 2.0 parser fails to handle time zones
with quotation marks around the TZID value, which is something
that SyncEvolution started to add in 1.4.99.3. While it is valid
to quote like that, it is not necessary, so avoid quoting in
this case to restore interoperability.
* syncevo-http-server: stop using deprecated twisted.web.error (FDO #90419)
This has become a real problem for example on Fedora 22 where the
old name is no longer available.
* syncevo-http-server: use TLS instead of SSLv3
This fixes a potential security risk and connection problems with clients
that don't support SSLv3 anymore.
* syncing: avoid segfault for invalid text inside items (FDO #90118)
As reported by Canonical, syncing fails if data items contain
text which is not correct UTF-8 in one of the fields that
SyncEvolution logs in the command line output (like SUMMARY of
a calendar event).
That is because the byte string coming from the item is passed
unchecked to the D-Bus implementation for transmission via D-Bus. But
D-Bus strings must be correct UTF-8, so depending on the D-Bus library
in use, one gets a segfault (GIO D-Bus, due to an unchecked NULL
pointer access) or an "out of memory" error (libdbus, which checks for
NULL).
SyncEvolution now replaces invalid bytes with a question mark in its
output while preserving the rest of the text.
* file backend: log item manipulation
Extracting a meaningful description of each item from the Synthesis
engine when updating and adding items is easy to do for items of
certain known types (contacts and calendar items).
* command line: preserve log prefix of target side of local sync
In some cases, the prefix which was supposed to be embedded
in the log messages from the target side of a local sync got
lost on the way to the command line tool.
Primarily this affected the added/updated/deleted messages, as in:
[INFO remote@client] @client/addressbook: started
[INFO remote@client] updating "Joan Doe"
[INFO remote@client] @client/addressbook: received 1/1
* compile fix: use ${PKG_CONFIG} instead of pkg-config.
This fixes the build on Exherbo that only has prefixed versions of
pkg-config.
* WebDAV: handle 403 during Google OAuth authentication
When sending an access token with insufficient scope (for example,
because the Ubuntu Online Accounts service definition was incomplete,
as documented in FDO #86824), Google responds with a 403 "service
denied" error.
This is now dealt with by retrying, just as for a transient 401 error.
* CalDAV: more efficient "is empty" check (FDO #86335)
Since 1.4.99.4, syncing WebDAV collections always checks first
whether there are items in the collections. This was partly done for
slow sync prevention (which is not necessary for empty collections),
partly for the "is the datastore usable" check.
However, this did not take into account that for CalDAV collections,
the entire content gets downloaded for this check. That is because
filtering by item type (VEVENT vs. VJOURNAL) is not implemented
correctly by all servers. So now all CalDAV syncs, whether incremental
or slow, always transfered all items, which is not the
intention (incremental syncs should be fast and efficient).
This release adds a more efficient isEmpty() check: for simple CardDAV
collections, only luid and etag get transferred, as in
listAllItems(). This is the behavior from 1.5.
For CalDAV, a report with a filter for the content type is used and
the transfer gets aborted after the first item, without actually
double-checking the content of the item. This is different from
listAllItems(), which really transfers the content. This extra content
check would only be needed for some old servers (Radical 0.7) and is
not essential, because reporting "not empty" even when empty is safe.
* WebDAV: send Basic Auth via http in some cases (FDO #57248)
It turned out that finding databases on an Apple Calendar server accessed via
http depends on sending Basic Auth even when the server does not ask for it:
without authentication, there is no information about the current principal,
which is necessary for finding the user's databases.
To make this work again, sending the authentication header is now forced for
plain http if (and only if) the request which should have returned the
principal URL fails to include it. This implies sending the same request
twice, but as this scenario should be rare in practise (was only done for
testing), this is acceptable.
* Ubuntu Online Accounts: support plain text credentials
The backend for UOA was rewritten by Alberto Mardegan and now also
can use plain username/password credentials stored in UOA.
* various compiler error and warning fixes
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2015/syncevolution-151-released
Source code bundles for users are available in
https://download.01.org/syncevolution/syncevolution/sources
and the original source is in the git repositories
http://cgit.freedesktop.org/SyncEvolution/
i386, lpia and amd64 binaries for Debian-based distributions are
available via the "stable" syncevolution.org repository. Add the
following entry to your /etc/apt/source.list:
deb https://download.01.org/syncevolution/apt stable main
The GPG key for the repository needs to be imported as root with:
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys B2EC3981
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 ActiveSync binaries which were
compiled for Debian Wheezy, Ubuntu Saucy, Ubuntu Trusty an Debian
Jessie. The packages mentioned above are meta-packages which pull in
suitable packages matching the distro during installation.
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
https://download.01.org/syncevolution/syncevolution/. 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
http://syncevolution.org/documentation/getting-started steps.
--
Patrick Ohly, on behalf of everyone who has helped
to make SyncEvolution possible:
http://syncevolution.org/about/contributors
2 years, 12 months
[SyncEvolution] Comparison was impossible.
by Marc Bantle
Hi all,
since early May I am using syncevolution from command line to sync my bq
E4.5 against my desktop machine syncevolution syncml-http-server.
Everything was working as expected.
Since mid of June (according to the logs) I permanently get the
'Comparison was impossible.'
warning for all (memo, contacts, calendar, todo).
I additionally set logdir and maxlogdir entries as suggested in [1]
(which where commented out before). This mainly changed the location
where the dumps are written to and prevented log directories from being
auto-deleted during the following update, if they do not contain
changes. This makes analysis easier.
If I look at the previous database dumps, that are given as comparison
sources in the log files [2], all the files (e.g. VCARD-entries for
addressbook) seem to be there and contain reasonable data. A diff of a
previous *.after-dump and its successor *.before-dump will show the
expected changes, if an entry was modified.
So for me its not obvious, why I get the above message.
Any ideas what else can be causing the message?
Marc
[1]
https://lists.syncevolution.org/pipermail/syncevolution-issues/2009-Octob...
[2]
http://gut-informierte-kreise.de/syncevolution-log-Comparison-was-impossi...
6 years, 9 months
[SyncEvolution] Handling event changes from Exchange
by Graham Cobb
I have just noticed that events are being corrupted when syncing from
Exchange.
The problem is that when an event changes, EAS can send a "change"
notification, with only the fields that have changed, not the whole new
event. activesyncd then creates a partial (and invalid!) VEVENT with
only the changed fields.
Syncevolution then replaces the event with just the information from the
partial VEVENT, losing all the rest of the information.
To make it clearer, here is an extract from the EAS protocol message
sent when one attendee's status has to be updated for an existing event:
<Change>
<ServerId>1:2170</ServerId>
<ApplicationData>
<Attendees xmlns="Calendar:">
<Attendee>
<Attendee_Email>aaaa(a)example.com</Attendee_Email>
<Attendee_Name>aaaa(a)example.com</Attendee_Name>
<Attendee_Status>4</Attendee_Status>
<Attendee_Type>1</Attendee_Type>
</Attendee>
</Attendees>
</ApplicationData>
</Change>
activesyncd generates:
1:2170
BEGIN:VCALENDAR
PRODID:-//Meego//ActiveSyncD 1.0//EN
VERSION:2.0
METHOD:PUBLISH
BEGIN:VEVENT
ATTENDEE;CN=aaaa(a)example.com;PARTSTAT=DECLINED;ROLE=REQ-PARTICIPANT:
aaaa(a)example.com
END:VEVENT
END:VCALENDAR
And syncevolution ends up replacing the whole event with:
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.47//EN
BEGIN:VEVENT
LAST-MODIFIED:20150710T132346Z
DTSTAMP:20150710T132346Z
UID:syuid320541.212303337826681
SUMMARY:unnamed
ATTENDEE;CN="aaaa(a)example.com";PARTSTAT=DECLINED;ROLE=REQ-
PARTICIPANT:mailto:aaaa@example.com
END:VEVENT
END:VCALENDAR
The question is, what do I do about this? Is there any way for
syncevolution to process updates and merge them with the existing
object? If not, does activesyncd have to go and refetch the entire
updated object from Exchange?
Graham
6 years, 9 months
[SyncEvolution] bluetooth error
by Téglás János
After upgrading to fedora 22, a SonyEricsson v640 phone cannot sync with evolution via bluetooth. Under Fedora19 it has been working well. No hardware has been changed. Bluez file transfer is working. In the syncevolution 1.5.1-1 GUI window no device can be found, neither a button to add one. I copied the old backup config files to .config/syncevolution/... and I get this error:
(...)
SAN datastore todo uri Task type 6 mode 206
Connecting Bluetooth device with address (the device address ) and channel 10
OBEX progress
OBEX Transport: get header who from connect response with value SYNCML-SYNC
Server sending SAN
ObexTransport send is called
OBEX progress
OBEX Request 2 got a failed response Bad Request
Server Alerted Sync init with SANFormat 12 failed, trying with legacy format
starting SAN 11 auth (a long alfanumeric here)== nonce SyncEvolution session 1 server PC Suite
SAN datastore addressbook uri Contact type text/x-vcard
SAN datastore calendar uri Calendar type text/x-vcalendar
SAN datastore memo uri Memo type
SAN datastore todo uri Task type text/x-vcalendar
SAN with overall sync mode 206
Here the sync terminates.
What can I do?
Thank You for your help,
Johann
6 years, 9 months
[SyncEvolution] Caldav notes, memos, tasks and todo support
by Vincent
Hello, here are my two questions:
1- First, what kind of different storages the Caldav RFC accepts? I was
not able to retrieve this information, because lot of people seem
confused between these four words: notes, memos, tasks and todo.
2- Second, SyncEvolution support two different backends for the things I
understand to be the same concept, and give this description in the
documentation <https://syncevolution.org/documentation/syncevolution-usage>:
* memo: plain text notes
* todo: task list
So what is the difference between memo and todo? ownCloud and
Thunderbird Lightning seem to call "task" the todo concept, and I've
never seen a "memo" implemented.
Enlight me please!
--
*Vincent*
http://influence-pc.fr/
6 years, 10 months
