[SyncEvolution] Problems with --sync refresh-from-client
by Mikel Astiz
Hi all,
I am trying to synchronize a Nokia phone (6303i Classic) over Bluetooth
with SyncEvolution, and I'm experiencing problems when
"refresh-from-client" is used. The synchronization process starts but
then stalls indefinitely until timeouted or manually cancelled.
The output I get is the following:
obex_parse_connect_header(): requested MTU=32767, used MTU=32767
[INFO] Server sending SAN
obex_data_request(): len = 104 bytes
fdobex_write(): sending 104 bytes
obex_data_indication(): Got 0 bytes msg len=3
obex_data_request(): len = 40 bytes
fdobex_write(): sending 40 bytes
obex_data_indication(): Got 1005 bytes msg len=1008
obex_data_indication(): Got 971 bytes msg len=1979
obex_data_request(): len = 4821 bytes
fdobex_write(): sending 4821 bytes
obex_data_indication(): Got 0 bytes msg len=3
obex_data_request(): len = 40 bytes
fdobex_write(): sending 40 bytes
With the same phone and configuration, it works fine with both "--sync
slow" and "--sync one-way-from-client".
Is there any specific configuration regarding the mode
"refresh-from-client"? Any ideas on how to debug this issue?
I'm using the latest source tree from the git repository.
Regards,
Mikel
9 years, 4 months
[SyncEvolution] SyncEvolution's ActiveSync backend moved
by Patrick Ohly
Hello!
I have moved the source of the ActivSync backend for SyncEvolution to
the SyncEvolution git repo. I used the import-foreign-git.sh script to
copy the entire development history and only pruned some of the
back-and-forth around compiling it.
I deleted the source in the activesyncd repo to avoid to avoid
confusion. I kept a pointer to it in the top-level README, so people
should know where to find now.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9 years, 4 months
Re: [SyncEvolution] sqlite backend calendar
by Patrick Ohly
On Do, 2011-08-25 at 20:21 +1000, Roger KeIrad wrote:
> I make a mistake, i mean the SQLiteContact source in sqlite backend .
Then I don't know what you mean with GetValue() and "ical representation
data". The GetValue() calls in that sqlite backend read the field list
entries, which are independent of the external representation.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9 years, 4 months
[SyncEvolution] trying to understand syncevolution config
by Diane Trout
Hi,
My eventual goal is to try and get an N900 to synchronize with an ubuntu 11.04 desktop. The bluetooth path looks broken so I was trying to understand how to use the syncevo-http-server.
On the N900 running "syncevolution ${server}" I get the error
[DEBUG 00:00:04] SAN source calendar uri http://192.168.34.178:9000/syncevolution/calendar type text/x-vcalendar
[DEBUG 00:00:04] SAN with overall sync mode 206
[INFO 00:00:04] Server sending SAN
[INFO 00:00:04] CurlTransport Failure: No URL set!
[DEBUG 00:00:04] exception thrown at SyncContext.cpp:1854
[ERROR 00:00:04] error code from SyncEvolution fatal error (local, status 10500): Server Alerted Sync init failed
[DEBUG 00:00:04] Module_DeleteContext 'session'
Synchronization failed, see /home/user/.cache/syncevolution/myrada-2011-08-24-00-11/syncevolution-log.html for details.
The part I think I'm not understanding is the relationship between the context and the peer.
Does the context contains the configuration for the database you want to sync? And then the peer describes the various "remote" devices you're tring to connect to. If so, what are the URLs in the peer supposed to be?
Also any guesses what the CurlTransport failure is about?
in default/config.ini syncURL is set, in default/peers/${server}/sources/calendar/config.ini there's a url set. (I disabled the other databases while trying to understand whats going on).
Thanks
Diane
9 years, 4 months
Re: [SyncEvolution] sqlite backend calendar
by Patrick Ohly
Roger,
please remember to do group-replies.
On Mi, 2011-08-24 at 01:39 +1000, Roger KeIrad wrote:
> To solve to the DB schema problem, it will be usefull to implement a
> rapper that can be used by anyone who would like to synchronize using
> sqlite backend. when the DB schema change only the rapper will
> change .
My expectation is that the Synthesis sqlite datastore has a
configuration mechanism. Whether it covers the relevant mapping in this
case would have to be investigated.
> can you explain to me what's the iCalendar import/export mechanism ?
See MAKE/PARSETEXTWITHPROFILE() and how SyncSource uses it.
> what 's the part that ensure the mapping from some higher-level
> representation of calendar data to the schema ?
The mapping between the internal field list (which is kind of
higher-level) and the iCalendar text format is done via profiles. See
http://syncevolution.org/development/pim-data-synchronization-why-it-so-hard
How it is done with direct sqlite access I don't know. I have never used
or investigated that part. See SySync_config_reference.pdf and search it
for SQL.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9 years, 4 months
[SyncEvolution] Memotoo + X-EVOLUTION-FILE-AS
by Patrick Ohly
Hello!
According to its CtCap, Memotoo supports the X-EVOLUTION-FILE-AS
extension:
http://syncev.meego.com/2011-08-17-18-20_synthesis_memotoo_mobical_google...
But it seems to get lost, which breaks the testExtensions test.
This is provided by Evolution:
BEGIN:VCARD
VERSION:3.0
NICKNAME:user15
NOTE:Spouse's Name: foobar
FN:spouse name
N:name;spouse;;;
X-EVOLUTION-FILE-AS:spouse\, name
UID:pas-id-4E4C7EDE00000180
REV:2011-08-18T02:54:22Z
END:VCARD
This is sent to Memotoo as:
BEGIN:VCARD
VERSION:2.1
REV:20110818T025422Z
N:name;spouse;;;
FN:spouse name
X-EVOLUTION-FILE-AS:spouse, name
X-GENDER:
NICKNAME:user15
TITLE:
ORG:;;;
ROLE:
TEL:
EMAIL:
URL:
X-MOZILLA-HTML:
ADR:;;;;;;
BDAY:
NOTE:Spouse's Name: foobar
PHOTO:
END:VCARD
http://syncev.meego.com/2011-08-17-18-20_synthesis_memotoo_mobical_google...
Note that the comma was not considered special by the Synthesis encoder.
My memory is a bit fuzzy: is escaping it optional in vCard 3.0 optional
and/or does this depend on whether the property is meant to be a
comma-separated list? Lukas?
What comes back has an no X-EVOLUTION-FILE-AS:
BEGIN:VCARD
VERSION:3.0
REV:20110818T025434Z
N:name;spouse;;;
FN:name spouse
NICKNAME:user15
NOTE:Spouse's Name: foobar
END:VCARD
http://syncev.meego.com/2011-08-17-18-20_synthesis_memotoo_mobical_google...
Thomas, Memotoo either has to preserve the property or must not declare
support for it in the CtCap.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9 years, 4 months
Re: [SyncEvolution] sqlite backend calendar
by Patrick Ohly
On Fr, 2011-08-19 at 18:50 +1000, Roger KeIrad wrote:
> i want to use the GPE DB schema already proposed by Ove Kåven,i think
> it's a good schema, i want to implement vcalendar backend but i dont
> understand how to retrieve or insert items from libsynthesis cause in
> evolution backend you use libical and libecal. did i need to use these
> libraries (libical/libecal) in sqlite backend case ?
> As Ove Kåven mentionned that it will be usefull so i will try to do
> this task .
So the goal is to make it work with GPE?
In that case you have to ask yourself first whether reading/writing the
sqlite database directly really is the right approach. If GPE has a
library accessing it, then most likely that is the official API.
Bypassing it will lead to maintenance/compatibility problems if that
schema changes. You also have to duplicate existing work (mapping from
some higher-level representation of calendar data to the schema).
If you decide to use such a library and it has some iCalendar
import/export mechanism, then you can use some of the existing backends
as example to copy and adapt, for example the KCalExtended backend.
If it does not have such import/export, then an approach as in the
SQLiteContactSource with copying data from Synthesis directly (see
readItemAsKey/insertItemAsKey) may be easier.
If you want to use the Synthesis sqlite support, then you are entering
new ground. SyncEvolution has never used this before, so you would have
to figure out how to integrate that first. You'll have to understand
what needs to be in the Synthesis XML config (run with loglevel=5 to see
it) for an sqlite-based datastore. In SyncEvolution, that part of the
config is created by SyncSourceBase::getDatastoreXML(). You'll have to
modify the SynthesisInfo structure such that your SyncEvolution backend
can tell the core SyncSourceBase class a) that the backend wants to use
sqlite and b) with which parameters.
Change tracking could be done based on the ID + "modified" field. See
SQLiteContactSource + listAllItems().
> sqlite> .tables
> alarms_fired_through calendar_dbinfo events
> alarms_unacknowledged calendars events_deleted
> calendar default_calendar
> sqlite> .schema calendars
> create table calendars (title TEXT, description TEXT, url TEXT,
> username TEXT, password TEXT, parent INTEGER, hidden INTEGER,
> has_color INTEGER, red INTEGER, green INTEGER, blue INTEGER, mode
> INTEGER, sync_interval INTEGER, last_pull INTEGER, last_push INTEGER,
> last_modified);
> sqlite> .schema calendar
> create table calendar (uid INTEGER not NULL, tag STRING, value
> STRING);
> sqlite> .schema calendar_dbinfo
> create table calendar_dbinfo (version integer NOT NULL);
> sqlite> .schema events
> create table events (uid INTEGER PRIMARY KEY, start DATE, duration
> INTEGER, recur INTEGER, rend DATE, alarm INTEGER, calendar INTEGER,
> eventid STRING, rcount INTEGER, rincrement INTEGER, modified DATE,
> byday STRING, rexceptions STRING);
You'll need to know exactly what the semantic of these fields is and how
they map to the Synthesis fields. For example, what are valid values for
the recur integer? What is the difference between uid and eventid?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9 years, 4 months
[SyncEvolution] building activesyncd: undefined reference to `eas_account_set_server_protocols'
by Patrick Ohly
Hello!
I'm running into a baffling link error when rebuilding activesyncd
f72a6ce from today:
make[1]: Entering directory `/home/pohly/work/activesyncd/eas-daemon/src'
/bin/bash ../../libtool --tag=CC --mode=link gcc -g -Wall -DG_DISABLE_DEPRECATED -DDISABLE_EAS_DAEMON -g -Wall -Wextra -Wno-missing-field-initializers -Wno-sign-compare -Wno-unused-parameter -Werror=pointer-to-int-cast -Wdeclaration-after-statement -Werror-implicit-function-declaration -Wformat-nonliteral -Wformat-security -Winit-self -Wmissing-declarations -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs -Wpointer-arith -Wundef -Wwrite-strings -L/usr/local/evolution-2.32-2011-07-05/lib -lglib-2.0 -pthread -L/usr/local/evolution-2.32-2011-07-05/lib -ledataserver-1.2 -lxml2 -lgconf-2 -lsoup-2.4 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -ldbus-1 -lpthread -lrt -pthread -L/usr/local/evolution-2.32-2011-07-05/lib -ldbus-glib-1 -ldbus-1 -lpthread -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -pthread -L/usr/local/evolution-2.32-2011-07-05/lib -lsoup-2.4 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -o activesyncd activesyncd-activesyncd-server.o activesyncd-eas-sync.o activesyncd-eas-common.o activesyncd-eas-mail.o activesyncd-eas-test.o activesyncd-eas-marshal.o activesyncd-eas-interface-base.o ../../logger/libeaslogger.la ../libeas/libeas.la ../../libeasmail/src/libeasmail.la ../../libeassync/src/libeassync.la ../../libeastest/src/libeastest.la
libtool: link: gcc -g -Wall -DG_DISABLE_DEPRECATED -DDISABLE_EAS_DAEMON -g -Wall -Wextra -Wno-missing-field-initializers -Wno-sign-compare -Wno-unused-parameter -Werror=pointer-to-int-cast -Wdeclaration-after-statement -Werror-implicit-function-declaration -Wformat-nonliteral -Wformat-security -Winit-self -Wmissing-declarations -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs -Wpointer-arith -Wundef -Wwrite-strings -pthread -pthread -pthread -o .libs/activesyncd activesyncd-activesyncd-server.o activesyncd-eas-sync.o activesyncd-eas-common.o activesyncd-eas-mail.o activesyncd-eas-test.o activesyncd-eas-marshal.o activesyncd-eas-interface-base.o -L/usr/local/evolution-2.32-2011-07-05/lib /usr/local/evolution-2.32-2011-07-05/lib/libedataserver-1.2.so /usr/lib/libxml2.so /usr/lib/libgconf-2.so -ldbus-glib-1 -ldbus-1 -lpthread -lsoup-2.4 /usr/local/evolution-2.32-2011-07-05/lib/libgio-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgobject-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgmodule-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgthread-2.0.so -lrt /usr/local/evolution-2.32-2011-07-05/lib/libglib-2.0.so ../../logger/.libs/libeaslogger.so ../libeas/.libs/libeas.so ../../libeasmail/src/.libs/libeasmail.so ../../libeassync/src/.libs/libeassync.so ../../libeastest/src/.libs/libeastest.so -pthread -Wl,-rpath -Wl,/usr/local/evolution-2.32-2011-07-05/lib -Wl,-rpath -Wl,/tmp/activesyncd/lib
../libeas/.libs/libeas.so: undefined reference to `eas_account_set_server_protocols'
collect2: ld returned 1 exit status
make[1]: *** [activesyncd] Error 1
make[1]: Leaving directory `/home/pohly/work/activesyncd/eas-daemon/src'
What confuses me is that eas_account_set_server_protocols is in
libeasaccounts.so and libeas.so was linked against that library:
$ ldd ../libeas/.libs/libeas.so | grep account
libeasaccount.so.0 => /home/pohly/work/activesyncd/libeasaccount/src/.libs/libeasaccount.so.0 (0x00007f2797caf000)
$ objdump -T /home/pohly/work/activesyncd/libeasaccount/src/.libs/libeasaccount.so.0 | grep eas_account_set_server_protocols
000000000000413f g DF .text 00000000000003de Base eas_account_set_server_protocols
$ objdump -T ../libeas/.libs/libeas.so | grep eas_account_set_server_protocols
0000000000000000 DF *UND* 0000000000000000 eas_account_set_server_protocols
There's also no other reference to that symbol:
$ gcc -g -Wall -DG_DISABLE_DEPRECATED -DDISABLE_EAS_DAEMON -g -Wall -Wextra -Wno-missing-field-initializers -Wno-sign-compare -Wno-unused-parameter -Werror=pointer-to-int-cast -Wdeclaration-after-statement -Werror-implicit-function-declaration -Wformat-nonliteral -Wformat-security -Winit-self -Wmissing-declarations -Wmissing-include-dirs -Wmissing-noreturn -Wnested-externs -Wpointer-arith -Wundef -Wwrite-strings -pthread -pthread -pthread -o .libs/activesyncd activesyncd-activesyncd-server.o activesyncd-eas-sync.o activesyncd-eas-common.o activesyncd-eas-mail.o activesyncd-eas-test.o activesyncd-eas-marshal.o activesyncd-eas-interface-base.o -L/usr/local/evolution-2.32-2011-07-05/lib /usr/local/evolution-2.32-2011-07-05/lib/libedataserver-1.2.so /usr/lib/libxml2.so /usr/lib/libgconf-2.so -ldbus-glib-1 -ldbus-1 -lpthread -lsoup-2.4 /usr/local/evolution-2.32-2011-07-05/lib/libgio-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgobject-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgmodule-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgthread-2.0.so -lrt /usr/local/evolution-2.32-2011-07-05/lib/libglib-2.0.so ../../logger/.libs/libeaslogger.so ../libeas/.libs/libeas.so ../../libeasmail/src/.libs/libeasmail.so ../../libeassync/src/.libs/libeassync.so ../../libeastest/src/.libs/libeastest.so -pthread -Wl,-rpath -Wl,/usr/local/evolution-2.32-2011-07-05/lib -Wl,-rpath -Wl,/tmp/activesyncd/lib -Wl,-trace-symbol=eas_account_set_server_protocols
../libeas/.libs/libeas.so: reference to eas_account_set_server_protocols
../libeas/.libs/libeas.so: undefined reference to `eas_account_set_server_protocols'
collect2: ld returned 1 exit status
Why doesn't the linker consider libeasaccount.so.0 when checking for
this symbol? Why does it care in the first place?
[a bit later]
Found it. stracing the final ld invocation shows that it looks at an old
libeasaccount.so.0 in my /tmp/activesyncd install dir. Wiping that out
first avoided the issue.
I still don't know why ld considers those old libs at all. Does setting
the rpath have that effect? That is the only reference
to /tmp/activesyncd/lib.
Here's the final ld:
$ /usr/bin/ld -v --build-id --eh-frame-hdr -m elf_x86_64 --hash-style=both -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o .libs/activesyncd /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/crt1.o /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/crti.o /usr/lib/gcc/x86_64-linux-gnu/4.4.5/crtbegin.o -L/usr/local/evolution-2.32-2011-07-05/lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4.5 -L/usr/lib/gcc/x86_64-linux-gnu/4.4.5 -L/usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../.. -L/usr/lib/x86_64-linux-gnu activesyncd-activesyncd-server.o activesyncd-eas-sync.o activesyncd-eas-common.o activesyncd-eas-mail.o activesyncd-eas-test.o activesyncd-eas-marshal.o activesyncd-eas-interface-base.o /usr/local/evolution-2.32-2011-07-05/lib/libedataserver-1.2.so /usr/lib/libxml2.so /usr/lib/libgconf-2.so -ldbus-glib-1 -ldbus-1 -lpthread -lsoup-2.4 /usr/local/evolution-2.32-2011-07-05/lib/libgio-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgobject-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgmodule-2.0.so /usr/local/evolution-2.32-2011-07-05/lib/libgthread-2.0.so -lrt /usr/local/evolution-2.32-2011-07-05/lib/libglib-2.0.so ../../logger/.libs/libeaslogger.so ../libeas/.libs/libeas.so ../../libeasmail/src/.libs/libeasmail.so ../../libeassync/src/.libs/libeassync.so ../../libeastest/src/.libs/libeastest.so -rpath /usr/local/evolution-2.32-2011-07-05/lib -rpath /tmp/activesyncd/lib -trace-symbol=eas_account_set_server_protocols -lgcc --as-needed -lgcc_s --no-as-needed -lpthread -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/x86_64-linux-gnu/4.4.5/crtend.o /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/crtn.o
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9 years, 4 months
[SyncEvolution] SyncEvolution 1.1.99.6 released
by Patrick Ohly
SyncEvolution 1.1.99.6
======================
Mostly bug fixes, some improvements in testing and packaging. This
release was tested successfully with DAViCal 0.9.9.4.
* CalDAV: fixed incorrect change tracking causing "event not found" (BMC #22329)
* CalDAV: handle delete<->delete conflict during local sync (BMC #22327)
If the same event was deleted both locally and in the CalDAV server, syncing
failed with "event not found".
* Google Contacts: ensure that first/middle/name are set when storing in EDS (BMC #20864)
Evolution and the MeeGo UX assume that first/middle/last name are set.
That is not the case when a contact is created in the Google Contacts
web interface. Such contacts are sent by Google without the N
property.
SyncEvolution now tries to recreate the name components from the FN
string, by splitting at word boundaries and assuming "<first>
<middle> <last>" or "<last>, <first>" format. Obviously this
heuristic fails for some locales.
* CalDAV: continue despite Google Calendar access problems (see BMC #19484)
An attempt to work around "403 You don't have access to change that
event" errors, perhaps caused by
http://code.google.com/p/google-caldav-issues/issues/detail?id=38
The problem is now recorded instead of aborting the sync. The sync
then ends in a 22001 = "partial failure" error and the operation
will be retried in the next sync.
* CalDAV: transform UTC RECURRENCE-ID for Evolution (BMC #22594)
Evolution showed a meeting twice on the day of a modified recurrence,
if the meeting series was originally created and modified in Exchange,
then imported into Google Calendar.
* CalDAV syncevolution.org binaries now works when libneon.so.27
or libneon-gnutls.so.27 (Debian) are installed. Previously
libneon.so.27 was required, which is no longer available in
Debian Testing.
* syncevo-dbus-server/gdbus: fixed segfault when asked for properties
when none are available (BMC #22152)
* Evolution Calendar: fixed error handling for broken TZIDs
* Sony Ericsson: use ISO-8859-1 for all devices (BMC #14414)
Passing invalid UTF-8 strings into libecal caused glib to
abort syncevo-dbus-server.
* item operations: authentication problem for WebDAV when using keyring (BMC #21311)
The password wasn't looked up in the keyring when using --print-items/import/export/...
* WebDAV: fixed item operations without configuration (BMC #22164)
Previously failed with "[ERROR] : virtual read-only configuration node, cannot write
property webDAVCredentialsOkay = 1".
* auto sync: show all failed syncs except for temporary network errors (BMC #21888)
Notifications were meant to be shown for all errors except temporary
ones. This has never been implemented correctly since the feature was
introduced: instead of hiding known temporary errors, all errors except
500 (fatal error) were suppressed.
* vCard: inline local photo data (BMC #19661)
Some platforms (Maemo, MeeGo) store photos in separate files. Now SyncEvolution
efficiently includes that photo data in the generated vCard right before sending
it to a peer; previously it sent a useless local file:// URI. The Maemo port
has a less efficient workaround for that which now should be obsolete.
* syncevo-dbus-server: online status wrong without Network Manager or ConnMan (BMC #21543)
When neither Network Manager nor ConnMan are running, network presence was "not
online". This prevented running automatic syncs.
* fixed compile issues with Debian Testing/gcc 4.6.1
Known issues, might still be resolved for the final 1.2:
--------------------------------------------------------
* syncevolution.org binaries: libnotify1 -> libnotify4 incompatibility (BMC #22668)
Newer distros no longer have the libnotify.so.1 that syncevolution.org
binaries depend on. As a workaround it is possible to install the libnotify1
package from older distro releases.
* CalDAV: add<->add conflicts (BMC #22669)
Suppose the same meeting invitation for event UID=FOO is processed in
both Evolution and Google Calendar. This always happens when the meeting
invitation emails is sent to Google Mail, then later viewed in Evolution.
On the Evolution side, the invitation is accepted. In Google Calendar this is
still open.
When syncing in that state the sync engine does not recognize that
both sides have added the same meeting and the "meeting accepted"
information eventually gets lost.
As a workaround, always synchronize the calendar before processing
meeting invitation emails.
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2011/syncevolution-11996-released
Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources
i386 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":
deb http://downloads.syncevolution.org/apt unstable main
Binaries for lpia will be made available again in the next release.
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
http://downloads.syncevolution.org/syncevolution/evolution. 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
9 years, 5 months
