[SyncEvolution] configuration parameters: command line update
by Patrick Ohly
Hello!
I'd like to solicit some feedback about configuring local sync, in
particular command line options for it. I'm still debating this with
myself, so consider the following email as "thinking aloud"...
As you might remember from the "local sync" mail thread, local sync uses
two configurations (using a "foo" server implementing some protocol
"bar" as example):
1. "source" config @foo defines sources which access "foo" using
the "bar" protocol; source-config@foo provides additional
per-peer settings like a URL or username/password
2. "sync" config foo has syncURL=local://@foo and does a sync
involving local databases (the same ones also used with other
peers) and the databases accessible via @foo
The original plan was to avoid the need for the source-config@foo
settings. But that neglected that credentials for "foo" should be tried
to the @foo context, instead of putting them elsewhere, and that there
was no other property which could have been used for the URL, to name
just one example.
This setup with two configs leads to two usability problems:
* How can such a config be created from a template? "syncevolution
--configure foo" would be nice.
* How can properties of both contexts be modified in a single
command? This is necessary for the single configure command
above and for running a sync.
Related to this is the question:
* How can multiple source properties be set in a single command?
Not being able to do that has made the instructions for
configuring SyncEvolution as a server unnecessarily complex.
Syntax for property values
==========================
Currently there is "--[sync|source]-property <property>=<value>".
<property> is the name of one of the builtin properties. I can imagine
extending this syntax as follows:
[<config>/]<property>[/<source>]=<value> (syntax I)
where <config> is a configuration name (which may contain @ signs) and
<source> is a source name (like "addressbook"). The rational for
introducing the slash as separator is that neither config nor source
names are allowed to contain it.
Examples:
evolutionsource=My Address Boook
evolutionsource/addressbook=My Address Book
@foo/evolutionsource/addressbook=Foo's Address Book
The drawback is that splitting the left side of the assignment is
ambiguous. In "foo/bar", either "foo" or "bar" could be the property
name. This can only be decided when property names are well-known. Typos
would break this detection, leading to bad error messages.
So perhaps the following syntax would be better:
[<source>/]<property>[@<config>]=<value> (syntax II)
The ordering of source, property and config is more natural:
addressbook/evolutionsource=My Address Book
syncURL@foo=local://@foo
But now the meaning of @ is overloaded:
syncURL@source-config@foo=Foo's URL
That is not a problem for a syntax parser, but less readable. The
ambiguity is resolved by declaring that @foo always a context.
I prefer the second syntax. Any other opinions?
As before, unqualified properties apply to all sources and all configs.
Templates for local sync
========================
The current set of templates provide properties for just one
configuration, the one which uses SyncML to talk to a server or a
client. Creating a local sync involves creating two configs.
There is no 1:1 mapping between the two. It is possible to define the
@foo sources, then synchronize them with a) the @default sources with
foo@default and b) with a second set of sources in @bar config with
foo@bar.
In the "syncevolution --configure foo" invocation, "foo" is the name of
the sync config. But what is the name of the source config? I propose
the following heuristic:
* if syncURL=local:// (no explicit context): use @foo for peer
name foo[@context]
* if syncURL=local://@bar: use @bar
That way a command line user still has the chance to override the source
context name, while the right thing will happen by default. Examples:
syncevolution --configure \
--sync-property username=xyz \
--sync-property password=abc \
foo
=> create or update @foo and foo, setting username/password in both
because they apply to both contexts
syncevolution --configure \
--sync-property syncURL=local://@bar \
foo
=> create or update @bar and foo; credentials must have been set in
@bar before
A template for "foo" then might look like this:
--------------------
=== template.ini ===
fingerprint = Foo Server
description = sync with Foo using protocol Bar
=== config.ini ===
PeerIsClient = 1
syncURL = local://
=== sources/addressbook/config.ini ===
sync = two-way
uri = addressbook
=== config.ini@source-config@foo ===
syncURL = http://foo.com/
=== sources/addressbook/config.ini@foo ===
uri = /contacts
type = Bar Protocol
--------------------
In the D-Bus interface, this would be returned by GetConfig() with "" as
key for "config.ini", "source-config@foo" for config.ini inside the
source-config@foo config, "sources/addressbook" for
sources/addressbook/config.ini and sources/addressbook@foo for
sources/addressbook/config.ini@foo.
My hope is that sync-ui will simply preserve these additional entries in
the hash. When it does a "SetConfig()" call with the modified hash
(credentials inserted, sync mode for "adddressbook" set), these
additional entries tell the syncevo-dbus-server to do its magic and also
configure the @foo context. The advantage is that no or only minimal
changes to sync-ui and D-Bus interface will be needed.
The drawback is that this additional magic increases the complexity. For
example, SetConfig() is called for the "foo" config, but suddenly ends
up modifying a different config.
Password handling in local sync
===============================
Credentials in the sync config are not needed for the sync itself,
because the peer is part of the same process. But users and frontends
like the GTK sync-ui are used to setting credentials in the sync config.
Therefore I suggest that local sync should always apply sync credentials
to the context it is synchronizing with, if they are set in the sync
config. If they are empty, the values from the source config are used.
Make --sync-property/--source-property optional
===============================================
A purely cosmetic change. It has irked me for a long time that the
command line was not able to determine automatically what username=foo
means. It had to be told explicitly that this is a property assignment,
and more specifically, a sync property (--sync-property username=foo).
This was necessary because theoretically, there might be sync and source
properties with the same name. But that would be confusing and thus was
avoided (and should be in the future).
That leaves the question of distinguishing parameters and the config
name from property assignments. That's easy, anything starting with a
dash is a parameter, anything with an equal sign an assignment. Explicit
--sync-property and --source-property parameters can be used to resolve
ambiguities.
--
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, 3 months
[SyncEvolution] syncevo-http-server: planning of new functionality
by Patrick Ohly
Hello!
As usual, I'd like to write down some thoughts on future functionality
before actually implement it. This email is about syncevo-http-server,
the HTTP server which allows SyncML HTTP clients to synchronize with
SyncEvolution running as server.
There are some open issues to be solved:
1. http://bugs.meego.com/show_bug.cgi?id=10031 "needs to be
restarted after loss of connection"
2. http://bugs.meego.com/show_bug.cgi?id=1367 "nightly testing:
include SyncEvolution <-> SyncEvolution testing"
3. http://bugs.meego.com/show_bug.cgi?id=6369 "Error reporting in
HTTP server is sucky (Or: HTTP server ignores LogOutput dbus
signals)"
4. simplify startup (no issue filed)
The first one is still something that I haven't tried to reproduce. My
goal is to set up a test case first, automate it (second issue) and then
fix the problem.
Error reporting has been an issue, because users need to monitor the
output of syncevo-dbus-server and syncevo-http-server. The intention
here is to keep syncevo-dbus-server running in the background (as
before) and improve the output of syncevo-http-server:
1. catch the rather cryptic Twisted error messages
2. translate them into INFO/DEBUG/ERROR messages
3. show syncevo-dbus-server errors together with the messages from
syncevo-http-server itself
Finally, the rather complex startup for the "SyncEvolution on headless
server" case (start D-Bus session, start syncevo-dbus-server +
syncevo-http-server) should be combined into one invocation of
syncevo-http-server.
This needs to be optional, because on a normal desktop,
syncevo-http-server should not start another D-Bus session (would
confuse Evolution Data Server).
So here are the new command line options that I intend to implement:
-d|--debug enables debug messages
-q|--quiet limits output to real error messages; ignored if -d is given
--start-dbus-session creates a new D-Bus session for communication with
syncevo-dbus-server and (inside that server) with other
D-Bus services like Evolution Data Server; should only
be used if it is guaranteed that the current user will
not have another session running, because these services
can get confused when started multiple times; without this
option, syncevo-http-server a) uses the session specified
in the environment or b) looks for a session of the current
user (depends on recent ConsoleKit and might not always work)
--start-syncevolution[=<path>]
sets up the right environment for <path>/sbin/syncevo-dbus-server
and starts it explicitly, instead of depending on D-Bus auto-activation;
to be used when SyncEvolution is not installed at the location
it was compiled for (typically /usr); the <path> is optional,
if not given, then it'll be derived from the location of the
syncevo-http-server script
Does that make sense? Are there better names for these options?
--
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, 8 months
Re: [SyncEvolution] Fwd: Syncevolution: synchronization between two Linux-Based notebook
by Patrick Ohly
On Do, 2010-12-16 at 15:39 +0000, Giuseppe Gerace wrote:
> Excuse me, the one I've previously posted is syncevo-dbus-server
> output.
What you posted (Thu, 16 Dec 2010 12:27:52 +0000) is the output from
syncevo-http-server, the Python script which implements the HTTP part.
The error message you show is related to something which has gone wrong
earlier in syncevo-dbus-server, so the output from that process would be
more useful.
syncevo-dbus-server also writes very detailed -log.html files (see
"syncevolution --print-sessions @default"), which is what is needed if
the stdout output of syncevo-dbus-server doesn't explain the problem.
I understand that is all not as easy as it could be. Issues are open to
improve it (http://bugs.meego.com/show_bug.cgi?id=10270,
http://bugs.meego.com/show_bug.cgi?id=6369), but no-one has had the time
to work on those.
--
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, 8 months
[SyncEvolution] Sync problem: myFunambol -> Nokia n900 PR 1.3 with syncevolution
by Kyros Hariri
Hello all,
I have a sync problem with my Nokia n900 running syncevolution to
connect to myFunambol. This worked under PR 1.3 but now after I
new setup the n900 to PR 1.3 the sync process stops and a
message "Synchronization failed" appears although internet
is available.
I tried to uninstall syncevolution and deleted all directories
I could find with "find / -name syncevolution" as well. Then
Then I reinstalled and resetup my account but it failed again.
The Funambol account is OK since Thunderbird can sync with it.
Does someone has a solution for this?
Regards, Kyros
9 years, 8 months
[SyncEvolution] syncml-plugin installation
by a.chandna＠accenture.com
Hi,
I am ashish and I am trying to install libsyncml and syncml plugins in my ubuntu desktop.
After giving some try now I am able to install libsyncml -
I followed the following procedure for it:
svn co http://svn.opensync.org/libsyncml/trunk libsyncml
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=$prefix /path/to/libsyncml/source/
make
make test
make install
But I dnt know how to check its version and now when I am trying to install syncml-plugin I got follwing error:
root@ashish:/home/ashish/Downloads/build1# cmake -DCMAKE_INSTALL_PREFIX=$prefix /home/ashish/Downloads/syncml-plugin/trunk/
-- checking for one of the modules 'libopensync1;>=0.40'
CMake Error at cmake/modules/FindPkgConfig.cmake:357 (message):
None of the required 'libopensync1;>=0.40' found
Call Stack (most recent call first):
cmake/modules/FindOpenSync.cmake:27 (PKG_SEARCH_MODULE)
CMakeLists.txt:16 (FIND_PACKAGE)
CMake Error at cmake/modules/FindOpenSync.cmake:46 (MESSAGE):
OpenSync cmake modules not found. Have you installed opensync core or did
you set your PKG_CONFIG_PATH if installing in a non system directory ?
Call Stack (most recent call first):
CMakeLists.txt:16 (FIND_PACKAGE)
n Configuring incomplete, errors occurred!
Please help me out of this and if possible please send me simple steps to install syncml-plugins and to synchronize my phone with ubuntu desktop through Bluetooth.
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
9 years, 9 months
[SyncEvolution] sync via bluetooth with Nokia N900 doesn't work
by Daniel Jung
Hi,
i'm trying to directly sync my new Nokia N900 with Gnome's Evolution via
bluetooth, but unfortunately i can't make it work:
My system: Ubuntu 10.04.1 amd64
syncevolution-evolution 1.0beta3 and 1.1.1 (both tested, but didn't help)
i did not install syncevolution on the phone.
I paired my phone, and i can access the phone's filesystem via
bluetooth.
i created a template according to the docs:
syncevolution --configure --template "Nokia N900" --sync-property syncURL=obex-bt://XX:XX:XX:XX:XX:XX MyPhone
but if i run "syncevolution MyPhone", i get:
[WARNING] Cancel disconncting process
[WARNING] Cancel disconncting process
[ERROR] ObexTransprotAgent: Underlying transport error
Synchronization failed, see
/home/dj/.cache/syncevolution/nelson2-2010-12-28-18-32-b/syncevolution-log.html
for details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| memo | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| todo | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Tue Dec 28 18:32:51 2010, duration 0:01min |
| external transport failure (local, status 20043) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: ObexTransprotAgent: Underlying transport error
[ERROR] command line execution failure
sync-ui doesn't work, either.
syslog just sais:
bluetoothd[5299]: link_key_request (sba=... , dba=... )
some running processes:
$ ps ax | grep -i obex
7765 ? S 0:00 /usr/bin/obex-data-server --no-daemon
8032 ? S 0:00 /usr/lib/gvfs/gvfsd-obexftp --spawner :1.6 /org/gtk/gvfs/exec_spaw/2
$ ps ax | grep -i sync
14 ? S 0:00 [async/mgr]
17 ? S 0:00 [sync_supers]
7866 ? SLl 0:00 /usr/libexec/syncevo-dbus-server
$ ps ax | grep -i blue
733 ? S 0:00 [bluetooth]
5299 ? S<Ls 0:00 /usr/sbin/bluetoothd --udev
7696 ? Sl 0:00 /usr/bin/python /usr/bin/blueman-applet
7706 ? S 0:00 bluetooth-applet
8008 ? Sl 0:09 /usr/bin/python /usr/bin/blueman-manager
please help me, i've already spent several hours on this problem... :(
cya,
Daniel
--
\!/
@^@
--------------------------oOO-(_)-OOo-------------------
Daniel Jung Daniel.Jung(a)dj-web.de
Linux-User #118180 http://www.boogie-woogie.co.uk
9 years, 9 months
[SyncEvolution] SyncEvolution 1.1.1 release candidate
by Patrick Ohly
Hello!
I have prepared a pre-release of the 1.1.1 bug fix update. It is
available as version 1.1.0.99.1 at syncevolution.org (unstable .deb
repos, download area).
I would appreciate some feedback whether it really addresses the
problems it is meant to solve (see below). I'm a bit under the weather
right now and have done no manual testing of this release; it did pass
the automated testing, though.
My goal is to release 1.1.1 between Christmas and New Year.
----------------------------------
SyncEvolution 1.1 -> 1.1.1, xxxxxxxxxx
======================================
Maintenance release, in particular improving syncing with phones.
There was a bug that could cause all kinds of weird behavior after
a failed sync with a phone, so updating is highly recommended.
* Synthesis engine: fixed a corruption issue in internal meta data which
caused duplicates and other problems in a pretty indeterminstic way;
apparently caused by failed syncs (BMC #10358, #11044).
* Synthesis engine: recurrence rules with end date now sent correctly to phones (BMC #11241).
The RRULE property was not encoded correctly previously during the
iCalendar 2.0 -> vCalendar 1.0 conversion. Events with recurrence count
were okay. Probably also affected SyncML servers without iCalendar 2.0
support.
* Synthesis engine: fixed broken time zone information when sending to phone;
previously that broke sending calendar updates to Nokia phones (BMC #9600).
iCalendar 2.0 time zone definitions imported from libical were not
encoded correctly in vCalendar 1.0 items as sent to phones. Nokia
phones accepted such data when part of a new event, but rejected
updates of it.
* Synthesis engine: shorter TZIDs, might help N900 calendar (BMC #6680).
The shorter TZIDs will be included in iCalendar 2.0 data exported
by libsyntesis and thus SyncEvolution. This change is motivated primarily
by the observation that the N900 calendar storage can handle TZID=<location>,
but not TZID=/softwarestudio.org/Tzfile/<location>.
* ScheduleWorld: disable configuration template because service has shut down.
The template is only hidden from the GTK sync-ui, but remains in SyncEvolution
for the time being because it is referenced in several places.
* GTK sync-ui: workaround for "Sync Now" button not reacting to online
status changed (BMC #9949).
* Changed slow sync handling. Some users have complained about getting
duplicated contacts (BMC #10081). The exact reason is not known (no
useful logs provided yet), but it might be due to using "duplicate"
as resolution strategy during slow syncs.
This caused slightly different contacts to be duplicated instead of
merging the two copies, reasoning that "no data loss" is better than
"duplicates". This release switches to a mode where the engine
tries harder to avoid duplicates by merging data if modification
time stamps are available for contacts (usually they are). When fields
differ, the more recent data is kept.
* convert absolute alarm back to relative (BMC #11233)
Experiments show that at least Nokia phones (and thus perhaps also
Mobical.com) interpret a fixed alarm as "repeat alarm with the same
relative offset as on first occurrence". The same transformation to
relative alarm times is applied whenever the transformation to
absolute alarm is enabled for a peer.
* Sony Ericsson: enable conversion to absolute alarm times (BMC #10092)
Like Nokia and Mobical.net, Sony Ericsson phones also seem to be unable
to deal with relative alarm times - verified with t700.
* Sony Ericsson C510: workaround for SyncML violation
The phone does not sent identifiers for the target database;
using the source identifier as fallback allows a sync to
run.
* Fixed a regression affecting users who had created a config
with SyncEvolution < 1.0. Using the config worked once, then
failed with "No configuration for ... found". Users must
manually remove the empty "peers" directory inside their
affected configuration, the fix only makes configs without that
directory usable again (BMC #9381).
* Removed obsolete workaround for older mKCal calendar storage.
* Fixed error message in QtContacts backend.
* Same SYNCEVOLUTION_DEBUG code as in master branch.
* Some updates to synccompare, including a workaround for a Perl
bug seen on Debian Testing with Perl 5.10.1-16 (Perl panic).
* Fix compilation of syncevo-dbus-server with libnotify 0.7.0 (BMC #10453).
* Fixed compilation on Debian GNU/Hurd (no MAX_PATH, Mac OS X confusion).
----------------------------------
--
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, 9 months
[SyncEvolution] SyncEvolution 1.1.1 released
by Patrick Ohly
SyncEvolution 1.1.1 "Christmas Edition"
=======================================
Maintenance release, in particular improving syncing with phones.
There was a bug that could cause all kinds of weird behavior after
a failed sync with a phone, so updating is highly recommended.
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).
Changes 1.1 -> 1.1.1
====================
* Synthesis engine: fixed a corruption issue in internal meta data which
caused duplicates and other problems in a pretty indeterminstic way;
apparently caused by failed syncs (BMC #11044).
* Synthesis engine: recurrence rules with end date now sent correctly to phones (BMC #11241).
The RRULE property was not encoded correctly previously during the
iCalendar 2.0 -> vCalendar 1.0 conversion. Events with recurrence count
were okay. Probably also affected SyncML servers without iCalendar 2.0
support.
The fix was confirmed to work with Nokia phones. It also helps with Sony Ericsson
phones, but at least the t700 still has a problem: depending on the phone's
time zone, it repeats the event for one day too long (BMC #10092).
* Synthesis engine: fixed broken time zone information when sending to phone;
previously that broke sending calendar updates to Nokia phones (BMC #9600).
iCalendar 2.0 time zone definitions imported from libical were not
encoded correctly in vCalendar 1.0 items as sent to phones. Nokia
phones accepted such data when part of a new event, but rejected
updates of it.
* Synthesis engine: shorter TZIDs, might help N900 calendar (BMC #6680).
The shorter TZIDs will be included in iCalendar 2.0 data exported
by libsyntesis and thus SyncEvolution. This change is motivated primarily
by the observation that the N900 calendar storage can handle TZID=<location>,
but not TZID=/softwarestudio.org/Tzfile/<location>.
* ScheduleWorld: disable configuration template because service has shut down.
The template is only hidden from the GTK sync-ui, but remains in SyncEvolution
for the time being because it is referenced in several places.
* Evolution CalDAV: added workaround for "must sync twice" (BMC #10265)
The Evolution CalDAV backend seems to update its data when closing the
database, not when opening it. As a result, syncevolution had to be run
twice to see all data changes. The workaround is to open the database
twice at the start of the sync. This is done for all calendar databases,
regardless of which backend they use, in case that some other (yet unknown)
backend needs the same workaround.
* GTK sync-ui: workaround for "Sync Now" button not reacting to online
status changed (BMC #9949).
* Changed slow sync handling. Some users have complained about getting
duplicated contacts (BMC #10081). The exact reason is not known (no
useful logs provided yet), but it might be due to using "duplicate"
as resolution strategy during slow syncs.
This caused slightly different contacts to be duplicated instead of
merging the two copies, reasoning that "no data loss" is better than
"duplicates". This release switches to a mode where the engine
tries harder to avoid duplicates by merging data if modification
time stamps are available for contacts (usually they are). When fields
differ, the more recent data is kept.
* convert absolute alarm back to relative (BMC #11233)
Experiments show that at least Nokia phones (and thus perhaps also
Mobical.com) interpret a fixed alarm as "repeat alarm with the same
relative offset as on first occurrence". The same transformation to
relative alarm times is applied whenever the transformation to
absolute alarm is enabled for a peer.
* Sony Ericsson: enable conversion to absolute alarm times (BMC #10092)
Like Nokia and Mobical.net, Sony Ericsson phones also seem to be unable
to deal with relative alarm times - verified with t700.
* Sony Ericsson C510: workaround for SyncML violation
The phone does not sent identifiers for the target database;
using the source identifier as fallback allows a sync to
run.
* Fixed a regression affecting users who had created a config
with SyncEvolution < 1.0. Using the config worked once, then
failed with "No configuration for ... found". Users must
manually remove the empty "peers" directory inside their
affected configuration, the fix only makes configs without that
directory usable again (BMC #9381).
* Removed obsolete workaround for older mKCal calendar storage.
* Fixed error message in QtContacts backend.
* Same SYNCEVOLUTION_DEBUG code as in master branch.
* Some updates to synccompare, including a workaround for a Perl
bug seen on Debian Testing with Perl 5.10.1-16 (Perl panic).
* Fix compilation of syncevo-dbus-server with libnotify 0.7.0 (BMC #10453).
* Fixed compilation on Debian GNU/Hurd (no MAX_PATH, Mac OS X confusion).
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2010/syncevolution-111-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
9 years, 9 months
[SyncEvolution] How to specify which evolution calendar when syncing to Nokia E63
by Irihapeti
I am playing with the Darwin Calendarserver on Ubuntu 10.04. I have two
calendars in Evolution which are in the default location: Personal and
Caldav. I need to be able to specify that SyncEvolution use only the
Personal calendar and not Caldav, or everything gets deleted off the
phone. (Thank goodness for the recovery options!)
Because the E63 uses the calendar+todo option, I'm having trouble
figuring out how to edit the config file. If I change
~/.config/syncevolution/default/sources/calendar+todo/config.ini so that
"evolutionsource = "anything other than "calendar,todo" I get an error.
Is this the file I'm supposed to be editing, and what should I be
putting in it?
Best wishes to all for the festive season.
Irihapeti
9 years, 9 months
