Re: [SyncEvolution] superdatastore = combined events+todo (was: Re: SyncEvolution Bug 3182 - support ovi.com (Nokia sync service))
by Suyog
Hi,
I have tested latest version with Ubuntu Karmic Koala 9.10 which I have installed on my laptop.
Everything works well exactly same as it was in 9.04, Contacts, Calendar but No Notes & To-do.
When are you planning to release 1.0? Can you add OVI in list of services rather than entering manually?
How we can have contact pictures also synced to Evolution?
Let me know if you want me to test anything specific.
Best Regards,
Suyog
> ----- Original message -----
> From: "Patrick Ohly" <patrick.ohly(a)intel.com>
> To: "Chen, Congwu" <congwu.chen(a)intel.com>
> Subject: RE: superdatastore = combined events+todo (was: Re: [SyncEvolution] SyncEvolution Bug 3182 - support ovi.com (Nokia sync service))
> Date: Thu, 29 Oct 2009 08:49:11 +0100
>
>
> On Thu, 2009-10-29 at 01:02 +0000, Chen, Congwu wrote:
> > Local Rejections: That would be solved by adding a superdatastore in
> > SyncEvolution as pointed by Patrick, this will goto my todo list.
>
> http://bugzilla.moblin.org/show_bug.cgi?id=4611
> "join/dejoin different sources"
>
> --
> 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.
>
--------------------------------------------------------------
Ovi Mail: Easy setup in minutes
http://mail.ovi.com
11 years, 10 months
[SyncEvolution] configuration testing
by Patrick Ohly
Hello!
Yongsheng has added some tests of the Session.Set/GetConfig() API calls
to test-dbus.py and I merged them into master. These tests cover the
API, but not whether the complete configuration tree looks exactly right
down to every single property.
The CPPUnit Cmdline test in src/syncevo/Cmdline.cpp covers these
details. This implies extra work whenever new properties are added,
because the reference configs must be updated as well. Being written in
pure C++ with no external reference files, this comparison is kind of
cumbersome.
Maintaining the tests is worthwhile. I had not run the test while
working on the new server config properties and promptly introduced some
flaws:
commit 4135afb8bc2b07730a05d679ebf8e6bd7ee2dde5
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Thu Nov 12 21:19:03 2009 +0100
server config: fixed tests and code for new config options
The Cmdline tests hadn't been updated together with adding the
new options and therefore failed. New properties must be added
to the reference config m_scheduleWorldConfig and new internal
properties also to the props list in testOldConfigure.
While checking the test failures, the following problems were found
and fixed:
- "adminData" property name was used for both sync and source property.
The sync property stores Synthesis device information and was
renamed to "deviceData" to avoid confusion. SyncConfig API calls
renamed accordingly. Property instance now follows syncProp* naming
convention.
- The source "adminData" property was not declared as "hidden"
and therefore showed up in the user-visible config.ini files
and --print-config output. The real value set/get in SyncSourceAdmin
was done correctly via the m_hiddenNode.
But maintaining the tests might be easier as part of the Python script.
We have regular expressions and can call external commands more easily.
Now my question is: should the CPPUnit-based tests be replaced by
Python/D-Bus ones? The advantage is that we only have to maintain the
tests once, possibly in some easier form. The disadvantage is that
without D-Bus enabled, that test doesn't work, and that we haven't
integrated the D-Bus tests into our nightly testing.
--
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.
11 years, 10 months
[SyncEvolution] Syncing multiple task lists
by John Dykstra
I'm attempting to use SyncEvolution and ScheduleWorld to sync multiple
to-do lists, but I haven't been able to figure out from the
documentation how to do that.
I understand how to specify the source, i.e.
syncevolution --source-property "evolutionsource=Work" --run scheduleworld todo
But I don't see how to tell the server to keep this data separate from
other to-do lists I sync. I suspect the URI that can be specified with
evolutionsource is the answer, but I need more of a recipe.
I'm using syncevolution-evolution_0.9.1-2_i386 running with Evolution
2.22.3.1 on Ubuntu Hardy.
Thanks for the help!
-- John
11 years, 10 months
[SyncEvolution] classification of configuration properties
by Patrick Ohly
Hello!
As mentioned before, the new configuration layout with shared properties
requires a classification of which properties are shared between peers:
http://syncevolution.org/development/configuration-handling
I've updated the classification slightly today:
* loglevel, printChanges, IconURI are now per-peer properties
(were shared before): IconURI clearly belongs to the peer,
loglevel and printChanges could be shared. I made them per-peer
settings because is conceivable that one might want to have
different settings (high loglevel for one peer while debugging
it, printing of changes off for peers where we act as server in
the background)
* "sync" per peer instead of shared; again, this should have been
per-peer from the start
* "type" per peer, because it contains per-peer parts (the
preferred data format)
The "type" is problematic. It selects both the backend (address
book/calendar/Evolution Address Book/etc.) and the data format
(iCalendar 2.0/vCalendar 1.0/both/...). This hack seemed like a good
idea because a) it avoided introducing another property and b) the
backend can be deduced from the data format ("text/vcard" => backend
which provides contacts, use vCard 3.0).
I'm not entirely sure how to deal with it yet. Perhaps introduce a
shared "type" property and a separate, per-peer "dataFormat" property
which are presented in the view as one "type"? That makes it impossible
to set inconsistent values via the APIs and keeps the rest of the code
as it is 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.
11 years, 10 months
[SyncEvolution] Recursive mainloop in SoupTransportAgent
by Chen Congwu
Hi,
We are using an inner recursive gmainloop for SoupTransport, which starts
blocking during wait() and quit the mainloop until the http request been
finished.
How does it work with the outer mainloop? Does it mean during wait() the outer
mainloop is freezing? I am inclined to this and this is not desiable. Any
comments?
--
Regards,
Chen Congwu
Moblin China Development
11 years, 10 months
Re: [SyncEvolution] code review: automatic D-Bus testing + Session.Sync()
by Patrick Ohly
On Fri, 2009-11-06 at 13:59 +0000, Zhu, Yongsheng wrote:
> Is 'mustauthenciate' used only internally?
At the moment, yes. It is used to implement the sync via a Connection.
> If no, we might change the API. If yes, we currently hardcode it.
> Seem strange.
Session.Sync() is meant to be used for initiating a sync from the GUI.
When we act as client, there's is no need for "mustauthenticate", it
wouldn't have any effect (our clients always send credentials, even if
they are not required to). When we act as server, the caller could
temporarily reset username and password to get the same effect.
Hmm, this would have been another way for a Connection to set "no need
to authenticate". Should I remove the parameter again?
--
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.
11 years, 10 months
[SyncEvolution] memo not supported by backends (0.9.1)
by Jason Grant
Hello,
I just downloaded the 0.9.1 rpm and installed under fedora 11, and am
getting the error shown at [1] below. The synthesis log is at [2]
below.
To get started with syncevolution, I installed the rpm, copied the
default funambol config and added a username/password. I also had to
"yum install pcre-devel" and "ln
-s /usr/lib/libpcrd.so /usr/lib/pcre.so.3".
I've gone through the blog and bugzilla, so hopefully I am not doing
something stupid...
Thanks for any tips,
Jason.
---------------------------------------------
[1] Error on first sync
[jas@talby funambol]$ syncevolution funambol
[ERROR] memo: type 'select backend' not supported by any of the backends (syncaddressbook.so, syncecal.so, syncsqlite.so, syncfile.so, syncebook.so)
Synchronization failed, see /home/jas/sync/SyncEvolution-funambol-2009-11-04-14-15/sysynclib_linux.html for details.
Changes applied during synchronization:
+---------------|-------ON CLIENT-------|-------ON SERVER-------|-CON-+
| | rejected / total | rejected / total | FLI |
| Source | NEW | MOD | DEL | NEW | MOD | DEL | CTS |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| addressbook | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| calendar | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| todo | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| start Wed Nov 4 14:15:07 2009, duration 0:00min |
| synchronization failed (status code 500) |
+---------------+-------+-------+-------+-------+-------+-------+-----+
---------------------------------------------
[2] Synthesis log
[2009-11-03 21:59:47.699] SyncML server account: removedForEmail
[2009-11-03 21:59:47.699] client: SyncEvolution 0.9.1 for desktop
[2009-11-03 21:59:47.699] device ID:
[2009-11-03 21:59:47.699] using libedataserver-1.2.so.11
using libebook-1.2.so.9
using libecal-1.2.so.7
[2009-11-03 21:59:47.699] Scanning backend libraries in /usr/lib/syncevolution/backends/
Loading backend library syncaddressbook.so
Loading backend library syncecal.so
Loading backend library syncsqlite.so
Loading backend library syncfile.so
Loading backend library syncebook.so
[2009-11-03 21:59:47.701] memo: type 'select backend' not supported by any of the backends (syncaddressbook.so, syncecal.so, syncsqlite.so, syncfile.so, syncebook.so)
11 years, 10 months
Re: [SyncEvolution] Calendar Error in V 0.9 ("could not read revision identifier...")
by dev＠welzl.info
Patrick Ohly schrieb:
> > V0.9 now really makes it difficult for me.
>
> Why did it become more difficult with 0.9? Without the GUI (which is off
> by default) the library dependencies should be about the same as in 0.8.
Sorry, I should have made one thing more clear:
I'm an end user. I can do configure/make/make install, and I once adapted
the Debian rules file without knowing what I really did to bring an package to
Maemo. But that's about it.
So I may well run into "problems" that in reality are just lack of knowledge
on my side.
Back on topic:
I don't remember what exactly was wrong, it's more than a month ago; I just know that
simply going the confige/make/make install route as in V0.7/V0.8 didn't work. It took
some googling and trial and error especially during the configure stage to reach
"make install" finally.
I know this isn't helpful.
I'd like to continue playing with it in scratchbox, anyway, where everything was
even worse, so I might be able to recall some of the dirty details once I'm there
again... If your still interested. ;)
> > [ERROR] calendar: could not read revision identifier for item
> > pas-id-419B999600000002-birthday-rid: only refresh-from-client
> synchronization
> > is supported
>
> Hmm, we might have a code path in 0.9 which triggers this exception. I
> don't remember how it worked in 0.8, but this code probably has changed.
> I'll check.
Thanks. Syncevolution has become a part of my life and I'd hate to miss some of its
functionality.
> Best Regards
Oskar
11 years, 10 months
[SyncEvolution] Could not encode item as iCal
by John Dykstra
I'm trying to use SyncEvolution for the first time, and I'm running into
a solid error when I try to do my first (refresh-from-client) sync:
[2009-11-06 15:16:51.381] SyncML server account: xxxxxxx
[2009-11-06 15:16:51.381] client: SyncEvolution 0.9.1 for desktop
[2009-11-06 15:16:51.381] device ID: sc-pim-51b0a4c3-f6a3-498a-a8eb-3b89feb4120d
[2009-11-06 15:16:51.381] using libedataserver-1.2.so.9
using libebook-1.2.so.9
using libecal-1.2.so.7
[2009-11-06 15:16:51.381] Scanning backend libraries in /usr/lib/syncevolution/backends/
Loading backend library syncecal.so
Loading backend library syncfile.so
Loading backend library syncaddressbook.so
Loading backend library syncebook.so
Loading backend library syncsqlite.so
[2009-11-06 15:16:51.418] creating /home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/todo.before
[2009-11-06 15:16:51.560] /home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/todo.before created
[2009-11-06 15:16:51.560] creating /home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/addressbook.before
[2009-11-06 15:16:54.877] /home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/addressbook.before created
[2009-11-06 15:16:54.878] creating /home/jwd/.cache/syncevolution/scheduleworld-2009-11-06-15-16/calendar.before
[2009-11-06 15:16:55.186] calendar: could not encode item as iCal: 040000008200E00074C5B7101A82E00800000000308FEABFA05DC801000000000000000010000000F0D61F794250FC45A6D673BD47934D15-rid
I've tried doing the same thing on a different machine where the
Evolution calendar is empty except for a test entry, and things seem to
work fine. So this might well be a corrupted entry in the first
machine's default calendar, but the hex string in the error message
doesn't help me to find it.
I couldn't find anything relevant on the list archives or searching the
web. It appears that error message used to refer to the failing item in
a more recognizable way.
This is syncevolution-evolution_0.9.1-2_i386 running with Evolution
2.22.3.1 on Ubuntu Hardy. The server is ScheduleWorld.
Thanks for the help!
-- John
11 years, 10 months
[SyncEvolution] How is "peer.config" selected in dbus method Connect
by Chen Congwu
Hello Patrick
If the syncevo-dbus-server is supposed to work as a syncML server, the dus api
Server.connect need peer.config to be set explictly to select the appropriate
configuration.
I noticed the http server now uses the request url path to identify this. How
can this be handled in obexd? The only possible information Obexd can get
without looking into the message is the peer's Mac address, but this property
seems not appropriate for configuration identification (The same device can
have multiple remote configuraitons).
I am asking this because I am using Obexd+SyncEvolution Server <--> Obex
Client+client-test for the obex transport test. It looks not easy for the obexd
to set the peer.config properly without looking into the message; therefore
either it always stick to a default configuration or the server need some other
mechanism to detect the configuraitons itself.
Also, the documentation seems have not updated to include peer.config.
--
Regards,
Chen Congwu
Moblin China Development
11 years, 10 months