[SyncEvolution] How to select the evolution target calendar
by Matthias Urlichs
Hello,
I have one small problem: I cannot select which local Evolution calendar
SyncEvolution actually talks to.
Apparently it uses the first entry in
the /apps/evolution/calendar/sources gconf entry that it can find. Since
the order of these entries isn't changeable and I need to separate
"work" from "home" calendar entries (with separate mobiles to sync to
…), I'd like some way to change that.
Either this is not possible yet, or I'm blind and didn't find it in the
documentation …?
Otherwise, thanks for the excellent tool; it works with our Oracle
calendar like a charm (using the values in the Oracle branch).
-- Matthias
12 years, 3 months
[SyncEvolution] preventing slow syncs - enable by default? (MB #2416)
by Patrick Ohly
Hello!
I have a question to users of SyncEvolution. In 1.0 beta 1, we added a
feature that gives you more control over error handling - but it is not
enabled by default yet:
$ syncevolution --sync-property preventSlowSync=?
'--sync-property preventSlowSync=?'
During a slow sync, the SyncML server must match all items
of the client with its own items and detect which ones it
already has based on properties of the items. This is slow
(client must send all its data) and can lead to duplicates
(when the server fails to match correctly).
It is therefore sometimes desirable to wipe out data on one
side with a refresh-from-client/server sync instead of doing
a slow sync.
When this option is enabled, slow syncs that could cause problems
are not allowed to proceed. Instead, the affected sources are
skipped, allowing the user to choose a suitable sync mode in
the next run (slow sync selected explicitly, refresh sync).
The following situations are handled:
- running as client with no local data => unproblematic,
slow sync is allowed to proceed automatically
- running as client with local data => client has no
information about server, so slow sync might be problematic
and is prevented
- client has data, server asks for slow sync because all its data
was deleted (done by Memotoo and Mobical, because they treat
this as 'user wants to start from scratch') => the sync would
recreate all the client's data, even if the user really wanted
to have it deleted, therefore slow sync is prevented
Slow syncs are not yet detected when running as server and in the
client when the server's anchor is wrong.
This option is not enabled by default because it forces users
to deal with slow syncs, which is a deviation from previous
behavior.
Is this something that you would find useful?
--
Best Regards
Patrick Ohly
Senior Software Engineer
Intel GmbH
Open Source Technology Center
Hermuelheimer Strasse 8a Phone: +49-2232-2090-30
50321 Bruehl Fax: +49-2232-2090-29
Germany
12 years, 7 months
[SyncEvolution] Data Munging
by Jim Rorie
I've noticed two issues cropping up intermittently in syncing.
Typically, these are inserting a lot of duplicates and screwy entries.
Not convinced that they are SE issues. Probably more like
Evolution-SE-funambol interactions and data capture bugaboos.
a) Duplications on contact entries that are companies. i.e. They don't
have a first name, last name. Typically something like "ACME Water
company". My thinking is that you put the entry in once and it's ok.
But, Evolution will try to map the "file as" to the "full name" field.
I think that under certain conditions evolution will change the sort
order after this type of mapping and end up with "Water company, ACME"
which may look like a new record. Thus a duplicate is born. Just a
theory.
b) Weird Suffix handling. I have a lot of Jr./Sr. in my contact. i.e.
"Joe blow, Jr." I've noticed that if I enter these records properly in
evolution using the suffix field box, after a bit of churning, I end up
with "Jr. Joe Blow". I'm thinking that the funambol server might be the
culprit in this one as it doesn't handle suffixes that I know of.
12 years, 8 months
[SyncEvolution] SyncEvolution 0.9.2 and 1.0 beta released, support Maemo 5/Nokia N900
by Patrick Ohly
SyncEvolution 0.9.2 and 1.0 beta are available. 0.9.2 replaces 0.9.1 as
the official stable release. Binary packages are provided. Changes in
both releases are listed below. 1.0 beta contains all changes included
in 0.9.2. Development has shifted towards 1.0, but if you find issues
in either version, please report them: http://syncevolution.org/support
SyncEvolution synchronizes personal information management (PIM) data like
contacts, calenders, tasks, and memos using the SyncML information
synchronization standard. Up to and including 0.9.x, a third-party
SyncML server is required.
In the 1.0 beta, SyncEvolution itself is already able to act as a SyncML
server, both via HTTP and Bluetooth (direct sync with phones). Because of
incompatible versions of libbluetooth in different distros, the precompiled
1.0 beta packages do not include Bluetooth support. One has to compile
from source to use that.
To learn more about SyncEvolution, come to FOSDEM 2010:
* Lightning Talk for users, Saturday 18:00,
http://www.fosdem.org/2010/schedule/events/syncevolution
* Cross-desktop devroom talk for developers, Sunday 15:15,
http://www.fosdem.org/2010/schedule/events/xd_syncml
SyncEvolution 0.9.2
===================
0.9.2 is available again for Maemo 5 and the Nokia N900, thanks to the
work done by Ove Kaaven. Support for the native calendar is included.
SyncEvolution Maemo packages are available via the Maemo extras-devel
repository. Bug reports can be submitted both in http://bugs.maemo.org
and http://bugzilla.moblin.org. The latter is the tracker that is
monitored by the SyncEvolution team, which will also incorporate
patches. In general, Ove is the main maintainer of the new backend.
New XMLRPC backend, contributed by Franz Knipp/M-otion. It accesses
data inside a web service via a SOUP API and thus allows synchronizing
it via SyncML. See src/backends/xmlrpc/README for more information.
Added templates for Oracle Beehive and Goosync. Both are not currently
part of the regular testing. In 1.0 beta, ZYB.com for contacts is tested
and supported.
In addition to that, 0.9.2 is an incremental update, with several
updated translations and addressing all of the issues reported by
users for 0.9.1:
* vCard dialects: added "X-GENDER/X-SIP" (used by Maemo) and X-SKYPE
(used by Maemo and recent Evolution, MB #8948)
* Evolution Address Book: avoid picking CouchDB by default (MB #7877, evolution-couchdb #479110)
CouchDB address books are appended at the end of the local database
list, otherwise preserving the order of address books. The initial
release of evolution-couchdb in Ubuntu 9.10 is unusable because it
does not support the REV property.
Reordering the entries ensures that the CouchDB address book is not
used as the default database by SyncEvolution, as it happened in
Ubuntu 9.10. Users can still pick it intentionally via
"evolutionsource".
* installation: templates now in $(datadir)/syncevolution/templates (MB #7808)
This are files used internally, meant to be extended by distributors.
Storing them in /etc is no longer supported, but also unlikely to be
needed. Added warnings that these files cannot simply be copied into
.config because they are not complete configurations.
* installation: "make install" populates $(docdir) (MB #7168)
Previously README, COPYING, NEWS, and server READMEs were copied
into syncevolution.org .tar.gz/.deb/.rpm archives as part of
custom make rules and thus missing in other installations.
* building: --with-boost had no effect (MB#7856), detect incorrect
use of --with-synthesis-src, workaround for lack of --with-docdir
in older autoconf, do not unnecessarily depend on CPPUnit header
files and GNOME/EDS libs (MB#8338), workaround for libtool bug
("cannot install `syncecal.la' to a directory not ending in ..."),
* clarified documentation of properties for file backend (MB#8146)
* stderr redirection: detect "error" messages and show them (MB#7655)
The "GConf Error: Failed to contact configuration server..." error
message was suppressed by the code which catches noise from libraries
invoked by SyncEvolution. Now it is printed as ERROR, making it
easier to detect why running SyncEvolution inside cron needs
additional changes:
http://www.estamos.de/blog/2009/05/08/running-syncevolution-as-cron-job/
* importing contacts from SyncML server without full name (MB#5664):
Evolution expects the name to be set and shows an empty string if
it is missing. Now the name is re-added by appending first, middle and
last name.
* Evolution calendar: work around 'cannot encode item' problem (MB #7879)
Happens when the calendar file contains broken events which reference
a timezone that is not defined. Now the event is treated like one in
the local timezone.
* "http_proxy" env variable is supported regardless which HTTP transport
is used (MB#8177).
* avoid crashes when libecal sets neither error nor pointer (MB#8005)
and when aborting a running sync in the syncevo-dbus-server (MB#8385)
* "--status" output: fixed missing total item counts (MB #9097)
Known issue:
* ZYB.com is not supported because of a known anchor handling
problem in the server (MB#2424), worked around in 1.0.
* The IPv6 configuration in Ubuntu 9.10 "Karmic Koala" in combination
with libsoup and myFUNAMBOL causes network connectivity problems:
https://bugs.launchpad.net/libsoup/+bug/473042
Upgrading from 0.9:
* nothing to do, upgrading and downgrading should work seamlessly
Upgrading from 0.8.1:
* After switching from a 0.8.x release to a 0.9.x one, or vice versa,
do a "syncevolution --sync refresh-from-server" or
"--sync refresh-from-client" (depending on which side has the
authoritative copy of the data) once, to get client
and server into a consistent state. Not doing so can result in
applying the same changes to the server multiple times, and thus
duplicates.
SyncEvolution 1.0 beta
======================
Compared to the current stable release, this beta release can also:
* synchronize directly with a phone over Bluetooth/OBEX
* accept Bluetooth/OBEX connections in cooperation with obexd 0.19
* run SyncEvolution as a rudimentary HTTP SyncML server
These feature were already available in a source-only 1.0 alpha
release. For the beta, we fixed some issues (nothing major)
and in addition to the source, also make binaries available. As
before, we hope to get feedback on where we are going with 1.0 and its
SyncML server and direct synchronization features. If you want to get
involved, now is a good time because a) there is something which works
and b) there is still time to influence the final 1.0, scheduled for
March 2010.
Documentation of the new features can be found in the "Development"
section (http://syncevolution.org/development) for HOWTOs or ask on
the mailing list (http://syncevolution.org/support).
Here is a more complete list of features compared to the stable
release. The full (and up-to-date) list can be retrieved from the
Moblin Bugzilla (MB) issue tracking system with this query:
http://bugzilla.moblin.org/showdependencytree.cgi?id=7892&hide_resolved=0
For changes compared to the 1.0 alpha please consult the
change log.
Implemented features are marked with a plus +, open ones with a minus -.
ZYB.com
+ now works thanks to a workaround for anchor handling (MB #2424)
- only contacts tested because everything is considered legacy
by ZYB.com
Slow sync handling (MB #2416)
+ Unexpected slow syncs can be detected when running as client and
if configured (see "preventSlowSync"), abort the session so that
the situation can be analyzed. A refresh from client or server
might be more suitable. Because this required manual intervention
by the user, the feature is off by default.
- Catching slow syncs does not work yet when running as server and
in one corner case in a client.
Improved sync-UI:
+ settings for HTTP servers are now done inside the list of
all configs and server templates instead of poping up a
separate window
+ uses the new D-Bus API
+ no longer uses private gconf key to select default peer,
replaced by "defaultPeer" in SyncEvolution config
+ added recovery features like handling of unexpected slow syncs (MB #2416)
- restoring from backup only supported by command line (MB #8050)
- spinner to indicate network activity missing (MB #2229)
- interactive password request not implemented yet (MB #6376)
Command line:
+ fixed printing of rejected items (MB #7755)
+ improved error reporting (textual descriptions instead of plain
error codes MB #2069, partial success MB #7755, record and show
first ERROR encountered MB #7708)
+ can create new sources (MB #8424)
Redesigned and reimplemented D-Bus API, required by sync-UI:
+ central syncevo-dbus-server controls configurations and sync sessions:
http://syncevolution.org/development/direct-synchronization-aka-syncml-se...
+ accepts incoming SyncML connection requests and messages received by
independent transport stubs (obexd, HTTP server, ...)
+ can be used by multiple user interfaces at once
+ fully documented, see src/dbus/interfaces
+ no longer depends on dbus-glib with hand-written glue code for C++,
instead uses gdbus plus automatic C++ binding generated via C++ templates
- 'syncevolution' command line tool bypasses D-Bus server and runs
sync sessions itself (MB #5043)
- availability of peers not detected (connected for HTTP, paired for
Bluetooth; MB #7700)
- Bluetooth peers can only be configured via command line (MB #9216)
Revised configuration layout (MB #8048, design document at
http://syncevolution.org/development/configuration-handling):
+ several peer-independent sync and source properties are shared
between multiple peers
+ they can be accessed without selecting a specific peer, by using an
empty config name or with the new "@<specific context>" syntax
+ user interface in command line and D-Bus API unchanged
+ old configurations can be read and written, without causing
unwanted slow syncs when moving between stable and unstable
SyncEvolution versions
+ old configurations can be migrated with the "--migrate" command
line switch; however, then older SyncEvolution can no longer
access them and migrating more than one old configuration causes
the second or later configuration to loose its "deviceId" property
(which is shared now), causing a slow sync once
+ config names may contain characters that are not allowed in the
file names used for the underlying files; will be replaced with
underscores automatically (MB #8350)
- users of the sync-ui will not know about the --migrate option,
so if they have only one configuration, it should be migrated
automatically
SyncML server in general:
+ incoming connections are accepted by syncevo-dbus-server via
the D-Bus Connection API; because this is a "personal SyncML
server", all local data is meant to belong to a single user,
and only one sync session can be active at any point in time
+ different users on the same machine can run their own server,
as long as they ensure that listening for incoming connections
does not conflict with each other (different port in HTTP)
+ the session of an HTTP client which stops sending messages expires
after "RetryDuration" seconds instead of blocking the server
forever (MB #7710)
- suspend/resume support is untested (MB #2425)
- automatic backup of server databases is inefficient (done
even when client is not allowed to do a sync; always backs up
all data, including sources which are not active; MB #7708)
- the progress events and statistics reported for a SyncML client
are not generated when running as SyncML server, will require
a fair amount of refactoring in the Synthesis engine (MB #7709)
- the Synthesis server example config contains workarounds for
specific phones, but SyncEvolution does not currently use those;
adding new workarounds should be made very simple (MB #7712)
HTTP SyncML server:
+ test/syncevo-http-server.py provides an experimental HTTP server
based on Python and Twisted
- a configuration must be created for each peer manually, including
a remoteDeviceId value that contains the peer's SyncML device ID
(MB #7838)
OBEX SyncML server ("sync with phones"):
+ peers are contacted via a builtin transport that uses libopenobex (MB #5188)
+ Server Alerted Notification (SAN) message triggers syncs; server ID
and URI are configurable (MB #7871)
- a configuration must be created for each peer manually, including
a syncURL that contains the peer's MAC address (MB #7838)
- should be integrated into the system's Bluetooth pairing (MB #7089)
OBEX SyncML client:
+ obexd 0.19 contains a plugin which passes SyncML messages to syncevo-dbus-server
- parsing of SAN message is rudimentary and depends on an existing local
configuration, needs to be refined depending on which SyncML server software
it is meant to work with (MB #6175)
Automatic sync (MB #6378):
- no support for the various server push notification mechanisms
- no intelligent detection of local changes
- no regular background sync
- depends on safe handling of concurrent editing, which is blocked
by merging of a new Evolution Data Server API (MB #3479)
Upgrading from 0.9.x:
* Upgrading and downgrading should work seamlessly when using existing
configurations. But this being a beta, better ensure that you have
backups of both your data and your configurations in
~/.config/syncevolution.
* The new configuration layout is only used when creating new
configurations or explicitly invoking "syncevolution --migrate" (see
above). Such configs cannot be used by older SyncEvolution releases.
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2010/syncevolution-092-and-10-released
Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources
i386, amd64 and lpia binaries of 0.9.2 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
For 1.0 beta, use the "unstable" repository.
These binaries include the new "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).
Because of incompatible libbluetooth versions in the different
distributions, the packages of 1.0 beta do not contain Bluetooth support.
One has to compile from source to use that.
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 0.9 .tar.gz archives have to be unpacked and the
content must be moved to /usr, because several files would not be found
otherwise.
SyncEvolution Maemo packages for 0.9.2 are available via the Maemo
extras-devel repository.
After installation, follow the getting started steps:
http://syncevolution.org/documentation/getting-started
--
Patrick Ohly, on behalf of everyone who has helped
to make SyncEvolution possible:
http://syncevolution.org/about/contributors
12 years, 8 months
Re: [SyncEvolution] Problem with Syncevolution
by Suyog
Patrick,
I got it working after installing libbluetooth2 which was available in
Ubuntu Hardy packages, I read that it will work without any issues along
with libbluetooth3. I got it from following location.
http://packages.ubuntu.com/hardy/i386/libbluetooth2/download
Now I am getting various kind of issues while doing sync from GUI, i
tried google and OVI and both failed.
I will try to play more with this and report issues to you later.
Also I did try 0.9.2 but still getting same issue which i have send to
Congwu, i.e I do not see addressbook in GUI. I did everything from clean
uninstall and install but still problem continues, Also I have ensured in
config file that addressbook sync is enabled.Seems very strange issue.
Can you help here?
One good thing is that more people have tried and used syncevolution
successfully by following how-to which i posted on my blog, comments have
been encouraging.I wish you could add local bluetooth sync with phones to
GUI soon.That's really pain area right now with opensync.
Best Regards,
Suyog
> ----- Original message -----
> From: "Patrick Ohly" <patrick.ohly(a)intel.com>
> To: Suyog <suyog(a)ovi.com>
> Subject: Re: [SyncEvolution] Problem with Syncevolution
> Date: Fri, 29 Jan 2010 21:10:56 +0100
>
>
> On Fr, 2010-01-29 at 19:47 +0000, Suyog wrote:
> > Hi,
> >
> > I tried to install 1.0 beta but got error because of libbluetooth2 ,
i
> > can't install it. How to do it?
>
> You can't: http://bugzilla.moblin.org/show_bug.cgi?id=9289
>
> I thought I had changed the compilation of 0.1 beta so that the
binaries
> didn't use and thus didn't depend on Bluetooth, but apparently I made a
> mistake with that (like not publishing the right binaries, etc).
>
> I'll recompile the packages and publish new binaries, probably later
> today.
>
>
> --
> 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: Get mail on your mobile or the web
http://mail.ovi.com
12 years, 8 months
Re: [SyncEvolution] binaries + bluetooth
by Ian Reid
I just compiled SyncEvolution 1.0 beta on a clean Ubuntu 9.10
installation. Adding the recommended packages for compilation added
458MB of additional executables and libraries to my system.
So, please consider compiling Bluetooth sync capability into the future
binaries.
Also, after I installed the compiled binaries I realized that I had no
idea how to sync my phone using the new capability. It appears that the
sync capability with Evolution is more or less theoretical at this
point. There seems to be a lot of discussion on how to make it work
with specific phones. Mine is a Nokia 2760.
12 years, 8 months
Re: [SyncEvolution] Bluetooth sync with N900 ?
by Chen, Congwu
As reported by Klas Hultqvist, url 'Calendar' works for his calendar.
>I walked away with the phone by mistake before the end of the
> initial sync operation, which caused a timeout and a segfault.
I am interested in this segfault. Is it possible for you to provide a
stack trace for this? I may already fixed this in the master though.
> I then deleted it on the laptop again and tried a new sync.
> I may have misremembered some of the steps above, but the end
> result was that most of the events on my laptop got doubled.
The duplicated item is usually caused by an out-of-sync of the peers.
Why does this happen is still not clear. If you want help, set the log
level in ~/.config/default/peers/yourphone/.config.ini to 5 and sent
us the logs (both html and xml) located in ~/.cache/syncevolution/
and the exact steps reproducing the problem.
> Perhaps I should swap to use the git master. Would that get me the
> synthesis code as well (like the tarball did) or would I need to get
> that separately?
Yes, there are some bug fixing in the master branch which may solve your
problem. You also need to check out the synthesis code located in git.mobin.org
Note we are coming close a 1.0 beta release end of this month, you may wait
for that also.
Best Regards,
Congwu
From: Klas Hultqvist [mailto:klas_hultqvist@hotmail.com]
Sent: Tuesday, January 19, 2010 5:24 AM
To: Chen, Congwu
Subject: RE: [SyncEvolution] Bluetooth sync with N900 ?
Hallo again,
I walked away with the phone by mistake before the end of the initial sync operation, which caused a timeout and a segfault. When I tried again it printed a lot more information, listing the events it was adding etc. Afterwards, I tried adding an event in the phone and syncing again, which brought it back to the laptop. I then deleted it on the laptop and synced again. Seemed this removed the
event on the phone, but added it back on the laptop. I then deleted it on the laptop again and tried a new sync. I may have misremembered some of the steps above, but the end result was that most of the events on my laptop got doubled. I'm hoping that as long as I don't delete any events after they have been synced it will be OK. Perhaps I should swap to use the git master. Would that get me the synthesis code as well (like the tarball did) or would I need to get that separately?
Thanks a lot for your prompt response, and for your work on this code! I find it very useful.
Klas
________________________________
From: congwu.chen(a)intel.com
To: klas_hultqvist(a)hotmail.com; syncevolution(a)syncevolution.org
Date: Mon, 18 Jan 2010 09:14:22 +0800
Subject: RE: [SyncEvolution] Bluetooth sync with N900 ?
Yes, that's possible.
We already have some discussions about this:
http://lists.syncevolution.org/pipermail/syncevolution/2009-December/0008...
The code is already in master now, so the latest code should work.
I tested synchronize with N900's addressbook worked, I am also interested in whether it works
With calendar/task/memo though (which I thinks should be).
Best Regards,
Congwu
From: syncevolution-bounces(a)syncevolution.org [mailto:syncevolution-bounces@syncevolution.org] On Behalf Of Klas Hultqvist
Sent: Sunday, January 17, 2010 11:50 PM
To: syncevolution(a)syncevolution.org
Subject: [SyncEvolution] Bluetooth sync with N900 ?
I have an N900, and would like to synch it to my evolution calendar. Funambol accounts only last for three months, and it would be much neater to synch via bluetooth anyway, so I decided to try the 1.0 alpha release. I have a few questions:
1. Is it possible?
2. If it is possible, should it be enough to install syncevolution on my laptop (ubuntu 9.10), or do I need to change something on the phone?
3. If it is possible, what arguments should I give to the configure script? I tried without arguments. It says (among other things):
...
checking for LIBSOUP... no
checking for LIBSOUP... yes
checking for LIBOPENOBEX... yes
checking for BLUEZ... yes
checking for xsltproc... /usr/bin/xsltproc
checking for KEYRING... no
...
checking for PCRE... yes
checking for SQLITE3... yes
...
CONFIGURATION SUMMARY
addressbook: no
ebook: yes
ecal: yes
file: yes
sqlite: no
DBus service: no
UI (DBus client): no
However, the ENABLE_BLUETOOTH name is not defined when ./src/syncevo/SyncContext.cpp is compiled,
and so I get an error about unsupported transport type when I run syncevolution.
I don't know too much about autoconf/automake/configure/make, and I don't seem to be able to figure out what is missing for the ENABLE_BLUETOOTH flag to be switched on. Maybe I need to install some additional package?
Thanks,
Klas
________________________________
Windows Live: Make it easier for your friends to see what you're up to on Facebook.<http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/...>
________________________________
Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail(r).<http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/...>
12 years, 8 months
Re: [SyncEvolution] Problem with Syncevolution
by Suyog
Hi,
I tried to install 1.0 beta but got error because of libbluetooth2 , i
can't install it. How to do it?
Best Regards,
Suyog
----- Original message -----
From: "Chen, Congwu" <congwu.chen(a)intel.com>
To: Suyog <suyog(a)ovi.com>
Subject: RE: RE: Problem with Syncevolution
Date: Fri, 29 Jan 2010 14:24:51 +0800
Suyog
Since SyncEvolution 1.0 beta1 and 0.9.2 just released, I suggest you
try the new version.
�
http://lists.syncevolution.org/pipermail/syncevolution/2010-January/00093...
�
Best Regards,
Congwu
�
From:Suyog [mailto:suyog@ovi.com]
Sent: Wednesday, January 27, 2010 8:23 AM
To: Chen, Congwu
Cc: syncevolution(a)syncevolution.org; jku(a)linux.intel.com
Subject: Re: RE: Problem with Syncevolution
�
Hi,
Sorry for late reply, but I was busy with other activities. I did
syncevolution on command line and following is output. Addressbook is
shown but still have problems with GUI.I am using latest 9.10 Ubuntu.
Please help.
Evolution Address Book = Evolution Contacts = evolution-contacts: ��
Ubuntu One (couchdb://127.0.0.1) <default> �� Personal
(file:///home/suyog/.evolution/addressbook/local/system) � Evolution
Calendar = evolution-calendar: �� Personal
(file:///home/suyog/.evolution/calendar/local/system) <default> ��
Birthdays & Anniversaries (contacts:///) � Evolution Task List =
Evolution Tasks = evolution-tasks: �� Personal
(file:///home/suyog/.evolution/tasks/local/system) <default> �
Evolution Memos = evolution-memos: �� Personal
(file:///home/suyog/.evolution/memos/local/system) <default> � Show
available sources: ��syncevolution Show information about
configuration(s) and sync sessions: ��syncevolution --print-servers
��syncevolution --print-config [--quiet] <server> [sync|<source ...]
��syncevolution --print-sessions [--quiet] <server> Show information
about SyncEvolution: ��syncevolution --help|-h ��syncevolution
--version Run a synchronization: ��syncevolution <server> [<source>
...] ��syncevolution --run <options for run> <server> [<source> ...]
Restore data from the automatic backups: ��syncevolution --restore
<session directory> --before|--after [--dry-run] <server> <source>
... Remove a configuration: ��syncevolution --remove <server> Modify
configuration: ��syncevolution --configure <options for
configuration> <server> [<source> ...] ��syncevolution --migrate
<server>
�
Best Regards,
Suyog
> ----- Original message -----
> From: "Chen, Congwu" <congwu.chen(a)intel.com>
> To: Suyog <suyog(a)ovi.com>
> Subject: RE: Problem with Syncevolution
> Date: Wed, 6 Jan 2010 14:50:52 +0800
>
>
> 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
>
--------------------------------------------------------------
Ovi Mail: Being used by users in 178 countries
http://mail.ovi.com
--------------------------------------------------------------
Ovi Store: New apps daily
http://store.ovi.com/?cid=ovistore-fw-bac-na-acq-na-ovimail-g0-na-3
12 years, 8 months
Re: [SyncEvolution] Problem with Syncevolution
by Suyog
Hi,
Sorry for late reply, but I was busy with other activities. I did
syncevolution on command line and following is output. Addressbook is
shown but still have problems with GUI.I am using latest 9.10 Ubuntu.
Please help.
Evolution Address Book = Evolution Contacts = evolution-contacts: ��
Ubuntu One (couchdb://127.0.0.1) <default> �� Personal
(file:///home/suyog/.evolution/addressbook/local/system) � Evolution
Calendar = evolution-calendar: �� Personal
(file:///home/suyog/.evolution/calendar/local/system) <default> ��
Birthdays & Anniversaries (contacts:///) � Evolution Task List =
Evolution Tasks = evolution-tasks: �� Personal
(file:///home/suyog/.evolution/tasks/local/system) <default> � Evolution
Memos = evolution-memos: �� Personal
(file:///home/suyog/.evolution/memos/local/system) <default> � Show
available sources: ��syncevolution Show information about
configuration(s) and sync sessions: ��syncevolution --print-servers
��syncevolution --print-config [--quiet] <server> [sync|<source ...]
��syncevolution --print-sessions [--quiet] <server> Show information
about SyncEvolution: ��syncevolution --help|-h ��syncevolution --version
Run a synchronization: ��syncevolution <server> [<source> ...]
��syncevolution --run <options for run> <server> [<source> ...] Restore
data from the automatic backups: ��syncevolution --restore <session
directory> --before|--after [--dry-run] <server> <source> ... Remove a
configuration: ��syncevolution --remove <server> Modify configuration:
��syncevolution --configure <options for configuration> <server>
[<source> ...] ��syncevolution --migrate <server> �
Best Regards,
Suyog
> ----- Original message -----
> From: "Chen, Congwu" <congwu.chen(a)intel.com>
> To: Suyog <suyog(a)ovi.com>
> Subject: RE: Problem with Syncevolution
> Date: Wed, 6 Jan 2010 14:50:52 +0800
>
>
> 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
>
--------------------------------------------------------------
Ovi Mail: Making email access easy
http://mail.ovi.com
12 years, 8 months
[SyncEvolution] building 1.0 alpha 1 with libobex but without bluez
by David Bremner
Currently it seems that having libopenobex in the build environment but
not bluez causes syncevolution to fail to build.
See e.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566940, and
following links to build logs, we see
checking for LIBSOUP... no
checking for LIBSOUP... yes
checking for LIBOPENOBEX... yes
checking for BLUEZ... no
checking for xsltproc... /usr/bin/xsltproc
checking for KEYRING... yes
checking for KEYRING_2_20... yes
I'm not sure if such a configuration makes sense for syncevolution; if
not maybe the configure script could detect it and only enable libopenobex
if both libobex and bluez are found.
All the best,
David
12 years, 8 months
