[SyncEvolution] Detecting presence of network adapters
by Chen Congwu
Hello,
I am considering how to detect the status of network adapter (this will
solve MB#8879 as well as some simple presence detection).
I prefer to call Bluez/Connman dbus service for this but the problem is
there is connman on Moblin and network manager on other distros, there
would be some unncessary code duplication to handle both.
Or is there any portable underlying APIs that I can refer to directly?
--
Regards,
Chen Congwu
Moblin China Development
12 years, 5 months
[SyncEvolution] Sync Problem with Ubuntu One Contact list
by Ian Reid
Evolution 2.28.1
Syncevolution 0.9
I am unable to sync to the Scheduleworld server using syncevolution when
I have a Ubuntu One "CouchDB" contact list in Evolution.
The error messages:
#######
reidi@malta:~$ syncevolution scheduleworld
[ERROR] addressbook: contact entry without REV:
02368e17c4a745f5e2ed13495fc84605
Synchronization failed,
see /home/reidi/.cache/syncevolution/scheduleworld-2010-01-12-19-11/sysynclib_linux.html for details.
########
If I delete the Ubuntu One CouchDB contact list, then I can sync
properly.
12 years, 5 months
Re: [SyncEvolution] SyncEvolution in Fremantle
by M R
Hi there,
It's very exiting to have an early N900 version available.
I have tried the deb and works well over HTTP. Thanks Ove!
Just wondering if anyone has managed to establish a sync over HTTPS from
the N900. When I switch to HTTPS on the N900 I get the following INFO
message followed by timeouts.
[INFO] SoupTransport Failure: https://www.xxxxx.co.uk/horde3/rpc.php via
libsoup: SSL handshake failed
Looking at the traffic coming into the server, it would appear no
connection is being established from the N900 and that this is a network
transport problem?
Matt
On Sun, 2010-01-03 at 20:05 +0100, Uwe Kaminski wrote:
[Show Quoted Text - 32 lines][Hide Quoted Text]
Hi Ove,
Am Donnerstag, den 24.12.2009, 09:03 +0100 schrieb Ove Kaaven:
Update:
I've built a far better .deb based on SyncEvolution 0.9.1, and put it up
at http://people.debian.org/~ovek/maemo/
[...]
Still, it seems to work fine from the command line, if you really need
to sync your stuff. That's all I need, at least...
thank you so much for making a working version of syncevolution for
maemo5 including calendars and all the other sync sources!
There is already a brainstorming about the possibilities to add full
SyncML support to the N900 and syncevolution is the best solution (yet).
What are the next steps to make a solution for "everybody" out of your
development package? Is there anything to do for non-programming people
(like me) to make this project available for the community?
There is also a wiki page in maemo.org wiki where it's possible to add
some words about the status of the project:
http://wiki.maemo.org/Sync#SyncML
What do you think? Is this the right place for this?
Again, thanks for your (and of course Patricks and all the other
syncevolution developers) great work!
Best regards,
Uwe Kaminski (aka jukey)
12 years, 5 months
[SyncEvolution] git update + testing
by Patrick Ohly
Hello!
I had a look at the work done in git while I was on vacation. I think we
need to discuss config template handling further and thus moved master
back a bit (see MB #7838).
I merged quite a bit of code into the syncevolution-0-9-branch and
changed the nightly testing to exercise that branch.
Are there any branches which are ready for merging and haven't been
merged yet? I know that some are not merged, I'm just not sure whether
they are considered ready ;-)
Congwu, can you review the "pohly" branch? I have more patches coming
which I will add there tomorrow, so you might wait a bit.
--
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.
12 years, 5 months
[SyncEvolution] SyncEvolution in Fremantle
by Patrick Ohly
Hello Maemo!
It has been a while that I posted anything here. Ironically, since I
started working on SyncEvolution full-time beginning of this year, I
seem to have *less* time left compared to the previous years when I did
it in my spare time ;-)
For those who haven't heard about it:
* SyncEvolution is a SyncML client synchronizing PIM data with
SyncML servers [1]. The versions <= 0.8.1 are available for
Maemo [2] and work with the builtin address book and the Dates
calendar.
* This year it became the sync solution in Moblin and switched to
the Synthesis SyncML engine [3], with the goal of using that
also as SyncML server on a desktop [4].
* We have direct client to server synchronization working in the
development branch, without depending on closed third party
software [5].
I'd love to see the latest SyncEvolution releases packaged properly for
Maemo, and so do users [6]. 0.8.1 still works fine on the older Maemo
releases it is available for, but 0.9 has several relevant improvements,
for example synchronization with Google Contacts and a GTK GUI.
I'm posting here because I hope that an interested developer or
maintainer will step up and take over packaging for Maemo. You can be
sure that this will have full support when it comes to merging patches
and including the Maemo port as first-class citizen in releases.
Another interesting area to work on would be support for other local
databases. GPE has been asked for several times. There is a plugable
backend API which would allow that, if a developer is interested [7].
That article is a bit dated, but still relevant. 0.9.1 (about to be
released) has several improvements that make writing a backend simpler,
for example it is not necessary to have your own
vCard/iCalendar/vCalendar encoder/decoder. Instead, it is possible to
exchange properties directly with the internal Synthesis format [8]. The
sqlite backend demonstrates that. For an introduction to the Synthesis
engine see [9].
I'm cross-posting to the SyncEvolution list to keep the other
SyncEvolution developers informed. If there's anything that I can help
with, please don't hesitate to reply here or contact me directly.
[1] http://syncevolution.org
[2] http://maemo.org/downloads/product/OS2008/syncevolution/
[3] http://www.estamos.de/blog/2009/05/13/syncevolution-09-beta-1-full-time-p...
[4] http://syncevolution.org/development/direct-synchronization-aka-syncml-se...
[5] http://article.gmane.org/gmane.comp.mobile.syncevolution/434
[6] http://talk.maemo.org/showthread.php?t=32515
[7] http://www.estamos.de/blog/2008/08/04/syncml-client-do-it-yourself-style/
[8] http://article.gmane.org/gmane.comp.mobile.syncevolution/136
[9] http://syncevolution.org/development/pim-data-synchronization-why-it-so-hard
--
Bye, Patrick Ohly
--
Patrick.Ohly(a)gmx.de
http://www.estamos.de/
12 years, 5 months
Re: [SyncEvolution] Problem with Syncevolution
by Chen, Congwu
Hello & Happy New Year.
Suyog wrote:
>Hi,
>
>Happy New Year to you and other members in moblin team.
>
>I am facing strange issue and need your help to resolve it. I have reinstalled
>syncevolution 0.9.1.
>
>Also I have configured OVI.com as service and made required configuration
>changes as per my How-to.
>
>Now I Open GUI, I don't see Contacts/Addressbook as source. I tried to enable
>it via config file, but still same issue.
I am not particularly sure about the UI things, but in command line when you
create a new configuration if the underlying database (Evolution Addressbook in
your case) is not available, the corresponding entry is marked as disabled.
So does running "syncevolution" (without parameters) in command line gives you
a list of datasources under Evolution Address Book?
Jussi, do you have any other hints about this problem?
>Also when can we see 1.0 available in Beta? Currently its in Alpha and tricky
>to install and use.
We have scheduled 1.0 beta release on end of Jan.
Best Regards,
Congwu
12 years, 5 months
[SyncEvolution] Compiling SyncEvolution/Synthesis for Android
by Patrick Ohly
Hello!
I've been wondering whether compilation of the open source libsynthesis
and SyncEvolution for Android is possible. There is of course the
official Synthesis SDK for Android, which is the better alternative for
those who need something which works right away *and* has the Java
bindings that are needed for GUI apps on Android.
For those who prefer compiling from source and/or want a working SyncML
client to play with, keep reading...
After some fiddling, I was able to compile both and run syncs with the
SyncEvolution file backend. Limitations:
* no GUI, only the command line tool
* no Java bindings (they are not part of the open source code
base)
* every exception aborts the program (does not happen during
normal runs)
Setup:
* install Android SDK and NDK
* install NDK wrappers (http://umbel.mooo.com/)
* ensure that the arm-linux-* binaries from the NDK wrappers are
in the PATH
* add a symbolic link from arm-linux-pkg-config to /bin/false in
the PATH: this prevents calling the build machine's native
pkg-config and thus detecting packages which don't exist on
Android
* download and compile libcurl, using --host=arm-linux as
configure flag
Compilation of libsynthesis and SyncEvolution uses the normal autotools
scripts. The source of libsynthesis required some fixes to compile
cleanly on Android. These patches were pushed into the "android" branch
on git.moblin.org.
SyncEvolution changes for Android were also pushed into an "android"
branch. The biggest change is a patch which makes exception handling
optional, because that is not supported by the Android compiler and
runtime libraries.
One change in both repos is for static linking: as you will see below,
installing a single binary is fairly easy, so that's how I wanted to
compile syncevolution. The Synthesis engine expects to load plugins
dynamically. Our previous solution for static linking depended on
dlsym(RTLD_DEFAULT) and --export-dynamic. The latter didn't have any
effect on the resulting Android executable, therefore I had to find a
different solution. I went for specifying the addresses of all plugin
functions in the XML config which is generated at runtime.
Another complication was SyncEvolution's dependency on Boost header
files. They work without exceptions, but some of them use typeinfo(),
which is not supported either. As a crude solution (not done 100%
correctly for non-Android platforms and with unknown implications for
the code which depends on runtime type information) I patched the header
files (patch attached).
Copy and prepare some set of Boost header files (I
used /usr/include/boost from Debian's 1.34.1-14) like this:
* mkdir <boost_path>/include
* cp -a /usr/include/boost <boost_path>/include
* cd <boost_path>/include/boost && patch -p1 <boost.patch
Finally, here's how I compiled SyncEvolution:
./configure --with-synthesis-src=<path>/libsynthesis \
CFLAGS="-g -Wall -Werror -Wno-unknown-pragmas" \
CXXFLAGS="-g -Wall -Werror -Wno-unknown-pragmas" \
LDFLAGS=-L<path>/ndk-wrappers/stlport/build/lib/obj/arm-linux-gcc/so/ \
--disable-shared --enable-static --enable-libcurl \
--disable-unit-tests --disable-integration-tests \
--disable-ecal --disable-ebook \
--with-boost=<boost_path> \
--with-xmltok=builtin \
--host=arm-linux
I originally also used --disable-sqlite --disable-ical --disable-reqgex,
but with the arm-linux-pkg-config link that should no longer be
necessary.
Copy SyncEvolution into a running emulator (started via "android"
command earlier):
adb push syncevolution /data/local/bin/syncevolution && \
adb shell chmod 755 /data/local/bin/syncevolution
Configure SyncEvolution for contact sync with ScheduleWorld:
adb shell "cd /data && /data/local/bin/syncevolution --configure
--source-property type=file:text/vcard:3.0
--source-property evolutionsource=file:///data/syncevolution/addressbook
--source-property sync=two-way
--sync-property username=<username>
--sync-property password=<password>
scheduleworld addressbook"
The "cd" is important because there is no HOME env variable;
SyncEvolution then defaults to the current directory. Files created
above and during a sync end up in /data/.config/syncevolution
(config), /data/.cache (logs) and /data/syncvolution/addressbook (one
vcard file per contact).
Run the initial sync:
adb shell "cd /data && /data/local/bin/syncevolution
--run --sync-property sync=slow
scheduleworld"
I was using the "slow-sync" branch, therefore a slow sync is only done
when expected by the user. All following runs:
adb shell "cd /data && /data/local/bin/syncevolution
scheduleworld"
This was just an experiment. I have not tried to get the automated
testing via "client-test" working, because that depends on CPPUnit and
thus another set of "no exception" patches.
Some of the resulting patches might be generally useful. Lukas, I
suggest that you pick whatever you find useful from the libsynthesis
repo. The static linking part would also be useful for Mac OS X, where
--export-dynamic is not a valid option to start with.
For SyncEvolution I'll probably let this settle a bit and then propose
patches for merging into master.
--
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.
12 years, 5 months
