12:22 p.m.
SyncEvolution 1.1
=================
An incremental update, resolving issues where the fixes would have
been too intrusive for a 1.0.x release. It replaces 1.0.x as the
officially supported stable version.
Compatibility with Nokia phones was improved. Some new features were also
included (command line options for manipulating items [1], backends for MeeGo PIM
storages).
[1]
http://syncevolution.org/blogs/pohly/2010/manipulate-evolution-kcalextend...
For those not familiar with the project, SyncEvolution synchronizes
personal information management (PIM) data like contacts, calenders,
tasks, and memos using the SyncML information synchronization standard.
Support for additional protocols is under way. Up to and including 0.9.2,
a third-party SyncML server was required. Since 1.0, SyncEvolution itself
is able to act as a SyncML server, both via HTTP and Bluetooth (direct
sync with phones).
Details:
* bug fix in sync-ui: wrong direction of one-way data transfers with devices (BMC #7091)
* bug fix in syncevo-dbus-server: incorrect Presence status after config change (BMC
#8453)
Shows up in sync-ui as "'Sync Now' button active after creating a config
while offline".
* sync-ui (GTK version): app is now listed as "SyncEvolution (GTK)" under
"Office"
* Nokia phones: avoid data loss in two-way sync due to X-EVOLUTION-UI-SLOT (BMC #2566)
* Nokia phones: alarm times in UTC, sending PHOTO (BMC #1657, #5860)
* included all phone templates submitted to syncevolution.org Wiki (BMC #5727)
* syncevo-phone-config: set consumerReady in output, more useful for Wiki (BMC #3803)
* workaround for D-Bus timeouts in EDS libecal/libebook (BMC #4026)
* added generic command line options for importing, exporting, updating, listing
and deleting items in the different backends
* added backends for mKCal and QtContacts (MeeGo PIM storage),
meant to be used for manipulating this data on the command line
* enhanced D-Bus interface (BMC #3558, #3559, #3560, #3562, #3563, #7761, #7766)
* the command line tool now warns when running against a different D-Bus daemon (BMC
#3563)
* creating and configuring sources in a context (without peer-specific
properties) is now supported
* improved documentation: README.rst, man page, and --help output
* fixed some compile issues (BMC #6367), improved nightly testing
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2010/syncevolution-11-released
Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources
i386, amd64 and lpia 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":
deb http://downloads.syncevolution.org/apt stable main
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
2:08 a.m.
Two issues which apparently were not solved:
1- I'm recently experiencing a strange behaviour for my E61: every time I sync
two-way I get the duplication of all my addrebook entries.
This behaviour started suddenly two days ago, with the previous version of
syncevolution, and continues with this version.
My configuration is the same I used earlier and is explained in the wiki.
I did not change anything.
This issue does not affect my other phone, Nokia 6220 classic.
2- everytime I change an entry under evolution, either contact or calendar, I
cannot sync my phones (nokia E61 and nokia 6220 classic) because I get an error
412.
When this happens I must refresh-from-server and afterward the nokia 6220
classic works correcly.
Any hints?
Giancarlo
2:30 a.m.
On Do, 2010-10-28 at 10:08 +0100, Giancarlo wrote:
Two issues which apparently were not solved:
Well, we can only fix issues which are reported in time before the
release ;-/
1- I'm recently experiencing a strange behaviour for my E61:
every time I sync
two-way I get the duplication of all my addrebook entries.
This behaviour started suddenly two days ago, with the previous version of
syncevolution, and continues with this version.
So at least it is not a regression. Please run a sync with "loglevel=4"
and send me the syncevolution-log.html file. It'll contain your private
contact data, but without that I cannot debug the problem. I promise to
keep it confidential.
You can restore the local state before the duplication with the command
line (--restore option) or the sync-ui ("recovery dialog").
2- everytime I change an entry under evolution, either contact or
calendar, I
cannot sync my phones (nokia E61 and nokia 6220 classic) because I get an error
412.
When this happens I must refresh-from-server and afterward the nokia 6220
classic works correcly.
Again a log file will be needed.
--
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.
10:40 a.m.
Patrick Ohly <patrick.ohly@...> writes:
Please run a sync with "loglevel=4"
> and send me the syncevolution-log.html file. It'll contain your private
> contact data, but without that I cannot debug the problem. I promise to
> keep it confidential.
I just can't. I have _very_ confidential information in my addressbook
(VISA card number, passwords, and so on) so I would never-ever send
such info through email. I'll try to replicate this issue with a clean
addressbook and if I succeed I'll send you the log at level 4.
> Again a log file will be needed.
This is feasable: my calendar is not that sensitive... I never
meet people
from Mafia, even if I'm from Sicily. So never mind even if someone taps my
email...;-)
Thank you _very_ much for your kind and prompt reply: I'll try to be
responsive as well.
Best wishes and thank you for your great work.
Giancarlo
On Do, 2010-10-28 at 10:08 +0100, Giancarlo wrote:
> Two issues which apparently were not solved:
Well, we can only fix issues which are reported in time before the
release ;-/
oh well... I did notice that this issue was there only yesterday and just
today I realized that the new release was out...
> cannot sync my phones (nokia E61 and nokia 6220 classic) because
I get
an error
> > 412.
> > When this happens I must refresh-from-server and afterward the nokia 6220
> > classic works correcly.
1:26 a.m.
Giancarlo <ianni@...> writes:
Patrick Ohly <patrick.ohly@...> writes:
> > cannot sync my phones (nokia E61 and nokia 6220 classic) because I get
an error
> > 412.
> > When this happens I must refresh-from-server and afterward the nokia 6220
> > classic works correcly.
>
> Again a log file will be needed.
>
This is feasable: my calendar is not that sensitive... I never meet people
from Mafia, even if I'm from Sicily. So never mind even if someone taps my
email...
Hi Patrick,
I'm sending you privately the log of my synchronization with Nokia6620 Classic.
I sync'ed using the GUI and asking only a calendar (regular: two-way) sync.
Before sync'ing, I made a change to two (or three?) entries in the calendar on
the server side (through Evolution), in order to replicate the error. As
expected, the error 412 appeared and no sync was performed on the phone.
Thank you very much for your kind help.
Giancarlo
5:01 a.m.
On Sa, 2010-10-30 at 09:26 +0100, Giancarlo wrote:
Giancarlo <ianni@...> writes:
>
> Patrick Ohly <patrick.ohly@...> writes:
>
> > > cannot sync my phones (nokia E61 and nokia 6220 classic) because I get
> an error
> > > 412.
> > > When this happens I must refresh-from-server and afterward the nokia 6220
> > > classic works correcly.
> >
> > Again a log file will be needed.
> >
> This is feasable: my calendar is not that sensitive... I never meet people
> from Mafia, even if I'm from Sicily. So never mind even if someone taps my
> email...
>
Hi Patrick,
I'm sending you privately the log of my synchronization with Nokia6620 Classic.
I sync'ed using the GUI and asking only a calendar (regular: two-way) sync.
Before sync'ing, I made a change to two (or three?) entries in the calendar on
the server side (through Evolution), in order to replicate the error. As
expected, the error 412 appeared and no sync was performed on the phone.
Can you replicate it with any kind of update or only with some of them?
There wasn't anything particularly exotic about the one which triggered
the 412 error in your log.
The phone is sent two properties which are optional in vCalendar 1.0,
UID and SEQUENCE. Perhaps it doesn't like them. Can you try again after
making the following changes?
1. copy /usr/share/syncevolution/xml/datatypes/11calendar-profile.xml into your home
directory as ~/.config/syncevolution-xml/datatypes/11calendar-profile.xml
2. Find '<property name="SEQUENCE"' in it.
3. Add onlyformode="standard" (similar to "GEO" right underneath
it).
4. Do the same for UID.
5. Repeat your experiment.
If it still fails, then please verify that UID and SEQUENCE number were
not included in the BEGIN:VCALENDAR that was "Generated".
--
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.
3:59 a.m.
Patrick Ohly <patrick.ohly@...> writes:
Can you replicate it with any kind of update or only with some of
them?
I get such error only when normal (two-way) synchronizing, _after making a
change on whatever appointment on the server side, through evolution_.
It happens regularly.
If it still fails, then please verify that UID and SEQUENCE number were
not included in the BEGIN:VCALENDAR that was "Generated".
It still fails. SEQUENCE is still in the Generated BEGIN:VCALENDAR, but UID
is not. I verified: I followed exactly your instructions.
I also made one more test: I backed-up the file
"/usr/share/syncevolution/xml/datatypes/11calendar-profile.xml" and edited
the original, so that the change was made directly on it. I did it just to
make sure that the changes are read and not ignored. But the result is still
the same.
I'm a little confused. I hope you can help me.
best regards
Giancarlo
4:11 a.m.
On So, 2010-10-31 at 13:01 +0100, Patrick Ohly wrote:
On Sa, 2010-10-30 at 09:26 +0100, Giancarlo wrote:
> Giancarlo <ianni@...> writes:
I'm sending you privately the log of my synchronization with Nokia6620 Classic.
>
> I sync'ed using the GUI and asking only a calendar (regular: two-way) sync.
> Before sync'ing, I made a change to two (or three?) entries in the calendar on
> the server side (through Evolution), in order to replicate the error. As
> expected, the error 412 appeared and no sync was performed on the phone.
Can you replicate it with any kind of update or only with some of them?
There wasn't anything particularly exotic about the one which triggered
the 412 error in your log.
I investigated this a bit with a Nokia N97 and was able to replicate the
problem. Don't bother running further experiments, what I suggested with
UID/SEQUENCE doesn't work.
The problem is related to time zone information. I created a new bug for
it here: http://bugs.meego.com/show_bug.cgi?id=9600
Giancarlo, just to confirm that we are seeing the same issue, does
creating an event in the UTC time zone (can be selected in Evolution if
you enable viewing of the time zone in the event edit dialog) and later
updating it work for you? That worked for me. Please reply in the bug
tracker.
But using UTC is a bad workaround, because recurring issues need time
zone information, so some more work is needed.
--
Best Regards
Patrick Ohly
Senior Software Engineer
Intel GmbH
Open Source Technology Center
Pützstr. 5 Phone: +49-228-2493652
53129 Bonn
Germany
4:34 a.m.
Il 02/11/2010 12:11, Patrick Ohly ha scritto:
On So, 2010-10-31 at 13:01 +0100, Patrick Ohly wrote:
> On Sa, 2010-10-30 at 09:26 +0100, Giancarlo wrote:
>
>> Giancarlo <ianni@...> writes:
>>
> I'm sending you privately the log of my synchronization with Nokia6620 Classic.
>
>> I sync'ed using the GUI and asking only a calendar (regular: two-way) sync.
>> Before sync'ing, I made a change to two (or three?) entries in the calendar
on
>> the server side (through Evolution), in order to replicate the error. As
>> expected, the error 412 appeared and no sync was performed on the phone.
>>
> Can you replicate it with any kind of update or only with some of them?
>
> There wasn't anything particularly exotic about the one which triggered
> the 412 error in your log.
>
I investigated this a bit with a Nokia N97 and was able to replicate the
problem. Don't bother running further experiments, what I suggested with
UID/SEQUENCE doesn't work.
The problem is related to time zone information. I created a new bug for
it here: http://bugs.meego.com/show_bug.cgi?id=9600
Giancarlo, just to confirm that we are seeing the same issue, does
creating an event in the UTC time zone (can be selected in Evolution if
you enable viewing of the time zone in the event edit dialog) and later
updating it work for you? That worked for me. Please reply in the bug
tracker.
But using UTC is a bad workaround, because recurring issues need time
zone information, so some more work is needed.
Yes I can confirm that if I create the entry with UTC time, sync, than
change the entry from Evolution (still setting UTC time) and sync again,
I get no error and the sync finishes correctly.
Thank you for your time! I hope the bug will be fixed.
Best regards
Giancarlo
--
--
-------------------------------------------------
Dr. Giancarlo Iannizzotto, PhD
Associate Professor
DiSIA - Dipartimento di Scienze per l'Ingegneria e per l'Architettura,
Faculty of Engineering,
University of Messina - ITALY -
http://visilab.unime.it/~ianni
elm: ianni(a)ingegneria.unime.it
elm: ianni(a)visilab.unime.it
PGP PUBLIC KEY: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF1A96309
phone: +39 0903977327 ---
--------------------------------------------------
"Let us leave this God of Pointland to the ignorant
fruition of his omnipresence and omniscience:
nothing that you or I can do can rescue him from
his self-satisfaction." Flatland, Section 20.
--------------------------------------------------
5 a.m.
Patrick Ohly <patrick.ohly@...> writes:
SyncEvolution 1.1
=================
An incremental update, resolving issues where the fixes would have
been too intrusive for a 1.0.x release. It replaces 1.0.x as the
officially supported stable version.
Compatibility with Nokia phones was improved.
One more question: are you planning to make syncevolution work with
symbian^3 ?
It seems that most nokia phones will run that OS in the future. And I must
admit, I like it.
All the best
Giancarlo
5:50 a.m.
On Di, 2010-11-02 at 12:00 +0000, Giancarlo wrote:
Patrick Ohly <patrick.ohly@...> writes:
>
> SyncEvolution 1.1
> =================
>
> An incremental update, resolving issues where the fixes would have
> been too intrusive for a 1.0.x release. It replaces 1.0.x as the
> officially supported stable version.
>
> Compatibility with Nokia phones was improved.
One more question: are you planning to make syncevolution work with
symbian^3 ?
"Work with" in the sense that SyncEvolution can exchange data with it?
That all depends on what kind of problems users run into. I will
certainly merge patches that fix problems, but whether I have time and
the means (= phones to test with) is a different question.
It seems that most nokia phones will run that OS in the future. And I
must
admit, I like it.
You know that my employer, Intel, and Nokia both work on MeeGo, another
OS which is meant to run on future Nokia phones? I don't have any
insider information and thus don't know, but I certainly hope to see
more Nokia phones use MeeGo than Symbian ;-)
--
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.
6:04 a.m.
Il 02/11/2010 13:50, Patrick Ohly ha scritto:
> One more question: are you planning to make syncevolution work with
> symbian^3 ?
>
"Work with" in the sense that SyncEvolution can exchange data with it?
That all depends on what kind of problems users run into. I will
certainly merge patches that fix problems, but whether I have time and
the means (= phones to test with) is a different question.
It looks like there might be lots of potential users for syncevolution
running symbian^3 in the near future. I suppose that Nokia will provide
you all the necessary hardware ;-)
> It seems that most nokia phones will run that OS in the future.
And I must
> admit, I like it.
>
You know that my employer, Intel, and Nokia both work on MeeGo, another
OS which is meant to run on future Nokia phones? I don't have any
insider information and thus don't know, but I certainly hope to see
more Nokia phones use MeeGo than Symbian ;-)
I do now who is your employee and what is MeeGo: I've been following the
development of Moblin since it was announced and I'm waiting impatiently
for a tablet and for a phone which use it (I'm not changing my netbook
just because I'm waiting for Meego).
I read somewhere that Nokia plans to equip the high-end phones with
MeeGo and low-end phones with Symbian^3.
This means that there will probably be more symbian^3 phones than MeeGo
phones in the near future. :-)
giancarlo
--
--
-------------------------------------------------
Dr. Giancarlo Iannizzotto, PhD
Associate Professor
DiSIA - Dipartimento di Scienze per l'Ingegneria e per l'Architettura,
Faculty of Engineering,
University of Messina - ITALY -
http://visilab.unime.it/~ianni
elm: ianni(a)ingegneria.unime.it
elm: ianni(a)visilab.unime.it
PGP PUBLIC KEY: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xF1A96309
phone: +39 0903977327 ---
--------------------------------------------------
"Let us leave this God of Pointland to the ignorant
fruition of his omnipresence and omniscience:
nothing that you or I can do can rescue him from
his self-satisfaction." Flatland, Section 20.
--------------------------------------------------
4:09 a.m.
Patrick Ohly <patrick.ohly@...> writes:
SyncEvolution 1.1
=================
An incremental update, resolving issues where the fixes would have
been too intrusive for a 1.0.x release. It replaces 1.0.x as the
officially supported stable version.
Compatibility with Nokia phones was improved.
Just to let you know that with this last version, both my phones (Nokia 6220
Classic and E61) are correctly detected and configured by just using sync-UI and
therefore no further configuration is needed. The only problem I got is the bug
regarding local time zone.
4254
days inactive
4263
days old
syncevolution@synevolution.org
12 comments
3 participants
participants (3)
-
Giancarlo -
Giancarlo Iannizzotto
-
Patrick Ohly