[SyncEvolution] Announcement: New Mailing list for Genesis development
by Frederik Elwert
Hello SyncEvolution lovers,
as some might know, I’m the lead (and for a long time only) developer of
Genesis[1], a graphical frontend for SyncEvolution for the GNOME
desktop. In contrast to SyncEvolution’s new native GUI, sync-ui, Genesis
aims primarily at desktop rather than mobile systems.
Fortunately, Genesis development has gained momentum lately, thanks to
David Castellanos joining the development team. He developed a sync
application derived from Genesis which is part of the Spanish Molinux
distribution[2]. Now many improvements, like full account management,
will find their way back to Genesis.
So we set up a new development team on Launchpad[3] with its own mailing
list. We invite everybody interested in participating in Genesis
development to join that team and the mailing list.
Cheers,
Frederik
[1] https://launchpad.net/genesis-sync
[2] http://www.molinux.info/
[3] https://launchpad.net/~genesis-devs
11 years, 2 months
[SyncEvolution] code review: automatic D-Bus testing + Session.Sync()
by Patrick Ohly
Hello!
I did some work today on test-dbus.py. I want to have automated tests
which suffer from 7710 ("server session handling") before fixing that.
I found one major issue with test-dbus.py: I recently broke
Session.Sync().
My patches currently sit in the "server-config" branch. I'd like to get
all of them merged into "master" up to and including
"synevo-dbus-server: Session.Sync() signature fix".
Yongsheng, this is in your area of work, so would you mind reviewing the
changes?
--
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, 2 months
[SyncEvolution] SyncEvolution 0.9.1 beta 2 released
by Patrick Ohly
Hello!
For those of you running the 0.9.1 beta announced last week, please
update to beta 2. The bug hunt is still on, so please test and provide
feedback...
SyncEvolution 0.9.1 beta 1 -> 0.9.1 beta 2, 19.10.2009
======================================================
Several fixes:
* Receiving photos from Mobical failed because Mobical does not
quite follow the vCard 2.1 (Moblin Bugzilla #6668). Sending
photos worked, but added a few bytes of garbage at the end of
each photo (typically ignored when showing). Parser was made
more tolerant by Synthesis and encoder bug was fixed.
* Task priorities used by Mobical and Evolution did not match:
vCalendar 1.0 uses 1-3, iCalendar 2.0 uses 1-9 (MB #6664).
SyncEvolution now translates between the two ranges, with some
information getting lost when talking to a peer which only
supports the smaller range.
* The workaround for detecting an endless stream of Alert 222
messages (caused by misbehavior of certain servers when a
specific message has to be resent) aborted certain valid (albeit
somewhat pathologic) sync sessions. Improved the heuristic so
that it still catches the real loop without aborting in that
other case.
* sync-ui: now disables sources which are not supported when
setting up a configuration, like memos on Moblin (MB #6672).
Previously the source was enabled, which prevented using using
the configuration as-is on the command line.
* .rpms on syncevolution.org no longer specify a dependency on
certain Perl features. This depencency was a problem on
Mandriva. Unwanted hard dependencies on libecal in
syncevolution.org binaries are avoided for real this time
(MB#6552).
* Trying to remove a non-existent configuration via the command
line now raises an error, to catch typos (MB #6673).
* Message resend options: added sanity checks to catch negative
values, clarified that duration is given in seconds, 0s resend
interval disables resending (MB #6500).
* Spelling fix: "aboring" => "aborting"
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2009/syncevolution-091-beta-released
Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources
Binaries for Debian-based distributions are available via the "unstable"
syncevolution.org repository. Add the following entry to
your /apt/source.list, then install "syncevolution-evolution":
deb http://downloads.syncevolution.org/apt unstable main
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).
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.
After installation, follow the getting started steps:
http://syncevolution.org/documentation/getting-started
--
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, 2 months
[SyncEvolution] obexd build not supporting syncevolution
by Jason Grant
Hi again.
I was hoping to use/test the opensync binding that is described here:
http://syncevolution.org/documentation/sync-opensync-bluetooth
The libsyncml build/install seemed work OK.
Alas, when I build and run obexd, it does not support syncevolution as
shown below. I am currently trying to reverse-engineer the code, and
work through prior discussions on this list, but any tips/pointers in
the interim would be appreciated.
I'm not sure if the obexd build is meant to be finding libsyncml or
syncevolution. If so, one thing I noticed is that when configure is
invoked, the output shows the following:
checking for GLIB... yes
checking for DBUS... yes
checking for dbus_watch_get_unix_fd in -ldbus-1... yes
checking for OPENOBEX... yes
checking for BLUEZ... yes
checking for EBOOK... yes
checking for GTHREAD... yes
i.e. there is no reference to either syncml or syncevolution. Also,
when I do an lld on obexd, there is no coupling to libsyncml or
syncevolution.
Tips appreciated.
J.
----------------------------------------------
[1] Checkout, build, and test obexd
[jas@talby obexd]$ git clone http://git.kernel.org/pub/scm/bluetooth/obexd.git
[jas@talby obexd]$ ./bootstrap-configure
[jas@talby obexd]$ make
[jas@talby obexd]$ ./src/obexd -nd
No server selected (use either --opp or --ftp or both)
[jas@talby obexd]$ ./src/obexd -nd --syncevolution
Unknown option --syncevolution
11 years, 2 months
Re: [SyncEvolution] SAN generating for obex transport]
by Chen Congwu
>On Wed, 04 Nov 2009, Ohly, Patrick wrote:
> This makes the interpretation of the syncURL property dependent on
> another one (PeerIsClient). After thinking about this some more I find
> this confusing and unnecessarily complex. I think we can simply redefine
> "syncURL" as the property which lists the "method(s) to contact the
> peer". This works for peers which are clients and servers.
I agree, this is more clear.
For a server contacting clients (peer), the syncURL is the methods to contact
the client.
For a server contacted by clients, how do you define the syncURL?
I thing configuration has two types: configuration for a remote peer and
configuration for myself.
Will their be another tag to differenciate this?
>
> So do we need another "syncServerURL" setting for a server? I have my
> doubts about it. As Lukas pointed out, the externally visible way of
> contacting our server is transport specific. In our design with
> transport stubs, the configuration of those stubs determines the URL,
> not the peer configuration inside SyncEvolution.
I think "syncURL" is also transport specific, a remote peer can have syncURL
per transport, do you argree? So why do we handle "syncServerURL" and "syncURL"
differently?
>
> Let's look at specific transports. For OBEX, we need to set the right
> server identifier, because some phones expect certain strings like "PC
> Suite". This is a new per-peer configuration option. Along the same
> line, we also need "aliases" for source names. What we call
> "addressbook" locally might only be recognized as "./Contacts" by a
> peer.
>
> For HTTP, the SAN can only be sent by a transport-specific mechanism
> which doesn't exist at the moment. Once we create it, we can think about
> how the HTTP server URL can be fed into it. We don't have to worry about
> it now.
Again, why do we handle HTTP and OBEX differently?
--
Regards,
Chen Congwu
Moblin China Development
11 years, 2 months
[SyncEvolution] code review: credential checking
by Patrick Ohly
Hello Congwu!
Given that you are working with code affected by this (incoming OBEX
connections), would you mind having a look at the patches that I just
pushed into the "server-config" branch?
I've tested everything up to and including the "SyncML server: don't
check client credentials if not required" part. If you agree, I'll merge
into master. Note that you also need to pull the updated master branch
of libsynthesis from moblin.org and that I am waiting for Synthesis'
okay for the authentication change applied to that branch.
I'll continue to work on the revised server configuration
(http://syncevolution.org/development/configuration-handling) on that
branch.
--
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, 2 months
[SyncEvolution] Funambol interoperability status
by Patrick Ohly
Hello Stefano!
When going through old emails and my mental todo list I remembered that
we do have a few open issues. In order to not forget about those, I
created an issue:
http://bugzilla.moblin.org/show_bug.cgi?id=7806
Not urgent, but if you have heard back from your colleagues about these
issues, then please let us know.
--
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, 2 months
[SyncEvolution] calconnect test suite
by Patrick Ohly
Hello!
This is a useful document that you might find interesting:
http://www.calconnect.org/publications/MobileCalendarTestSuitev1.1.pdf
It describes several manual tests which cover calendar synchronization
use cases. From Appendix A - Supporting Information:
Time Zones and Daylight Savings
In order to correctly display an event and interoperate with
major calendar applications, it is necessary for mobile calendar
solutions to provide support for time zones. Unfortunately, most
mobile calendar solutions do not provide full support for time
zones currently and are therefore unable to correctly display
events in all situations.
The following different classes of device time zone support have
been identified:
Full Time zone support
* has time zone configuration option
* stores all events as local time, UTC or local time with
time zone rule (as appropriate)
* transfers recurring events in local time with a time
zone definition
[...]
The timezone and daylight savings test cases described in this
test suite assume that full time zone support has been correctly
implemented. Other implementations are simply considered broken.
SyncEvolution + Evolution fully support time zones, so we should be able
to pass these tests.
--
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, 2 months
[SyncEvolution] SyncEvolution 0.9.1 released
by Patrick Ohly
SyncEvolution 0.9.1 is available. It replaces 0.9 as the official stable
release. Changes since that version are listed below. Changes made between
beta releases (for those who helped testing them) are documented here:
http://syncevolution.org/blogs/pohly/2009/syncevolution-091-beta-released
There are some known issues, see below. The more issues get reported
and fixed, the sooner there will be a 0.9.2 maintenance update, so keep
the reports coming. If you want to report something or get involved, then
contact the team:
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 current "master" branch, SyncEvolution itself is already able
to act as a SyncML server. Support for direct synchronization via
Bluetooth is planned for 1.0. A snapshot release will be made available
as soon as possible - end of October obviously did not work out...
SyncEvolution 0.9 -> 0.9.1, 26.10.2009
======================================
Mobical and Memotoo are now officially supported.
Memotoo uses vCard 2.1 with several Evolution specific extensions. It
uses iCalendar 2.0, however, without actually supporting the advanced
features of it. Times are converted to UTC and meeting information are
lost.
Mobical uses vCard 2.1 and vCalendar 1.0 as data formats, with the
result that many properties used in Evolution are not supported by the
server. In particular calendar support is very limited (known issues
when events are in time zones different from the one selected locally
and on the server, no support for meetings). For details see
README.mobical.
*** Beware *** that the Mobical SyncML password is *not* the same as
the one for their web site. Log into mobical.net, then go to "my accounts
>> configure new device >> manual settings" to find the SyncML
credentials.
It is now possible to compile database backends outside of
SyncEvolution, install them and have SyncEvolution use them
automatically like any other backend. The backend API has been
enhanced considerably. For example, backend developers have
access to a modular set of utility classes that can be mixed
into a specific implementation. Backends can access the internal
Synthesis representation directly and therefore no longer need
their own vCard/vCalendar/iCalendar parser.
The sqlite demo backend can be enabled and compiled again with
--enable-sqlite. It demonstrates how to map directly from the
Synthesis field list to some internal format (an SQLite database
schema in this case).
Other changes:
* Resend messages to cope with intermittent loss of network
connectivity (Moblin Bugzilla #3427). See the new "ResendDuration"
and "ResendDelay" configuration properties for details.
* SyncEvolution command line uses the GNOME keyring when
the new --keyring option is given.
* The logging of added and updated items was enhanced. Events,
tasks and memos are logged with a short description instead of
just the local ID. The description for contacts was improved.
* Receiving photos from Mobical failed because Mobical
does not quite follow the vCard 2.1 (Moblin Bugzilla #6668).
Sending photos worked, but added a few bytes of garbage
at the end of each photo (typically ignored when showing).
Parser was made more tolerant by Synthesis and encoder bug
was fixed.
* Task priorities used by Mobical and Evolution did not match:
vCalendar 1.0 uses 1-3, iCalendar 2.0 uses 1-9 (MB #6664).
SyncEvolution now translates between the two ranges, with
some information getting lost when talking to a peer which
only supports the smaller range.
* Importing work and home phone numbers from Google into desktop
Evolution works better, because SyncEvolution now adds the "VOICE"
flag expected by Evolution (MB#6501).
* SSL certificate checking with Google is enabled by default
and enabled in Moblin, because libsoup in that distro has
the necessary fix. Without that fix, all connection attempts
fail. The binaries on syncevolution.org are compiled with
--disable-ssl-certificate-check, so users who want the
additional security must enable it.
* .rpms on syncevolution.org no longer specify a dependency
on certain Perl features. This depencency was a problem on
Mandriva. Unwanted hard dependencies on libecal in syncevolution.org
binaries are avoided for real this time (MB#6552).
* Some sync-UI enhancements (describe sync services, avoid crash
with very long input in some of the text boxes (MB#5219), set
application icon, improved some strings).
* sync-UI: now disables sources which are not supported when
setting up a configuration, like memos on Moblin (MB #6672).
Previously the source was enabled, which prevented using
using the configuration as-is on the command line.
* The sync UI allowed to enable calendar and task synchronization
with Google although Google does not support that (MB#5871).
In new installations this is prevented by clearing the URI
for those data categories.
* Trying to remove a non-existent configuration via the command
line now raises an error, to catch typos (MB #6673).
* Improved checks which logs in the logdir belong to the current
server (MB#5215).
* Improved sanity checking of integer configuration parameters
(MB#6500).
* Spelling fix: "aboring" => "aborting"
Known issue:
* Mobical and Memotoo do not have a description in the GUI yet.
* ZYB.com is not supported because of a known anchor handling
problem in the server (MB#2424).
* When running as a cron job with GNOME >= 2.24, a D-Bus session
must be created manually as described here:
http://www.estamos.de/blog/2009/05/08/running-syncevolution-as-cron-job/
In 0.9.1, the "GConf Error: Failed to contact configuration server"
message is hidden from the user, leading to a failed syncs with
error code 500 and no further explanation (MB #7655).
* There is an unreproducible report that a refresh-from-client sync
of the Evolution "Birthday & Anniversaries" calendar no longer
works with 0.9.x, comment here if you run into this:
http://bugzilla.moblin.org/show_bug.cgi?id=7759
* 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
* Local problems during a sync are recorded with ERROR messages, but
do not affect the overall sync result and thus might go unnoticed:
http://bugzilla.moblin.org/show_bug.cgi?id=7755
The local problem in that report is "calendar: extracting event",
with no explanation at this point.
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.
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2009/syncevolution-091-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 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).
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.
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 0.9.x possible:
http://syncevolution.org/about/contributors
11 years, 2 months
[SyncEvolution] SE under Karmic Koala
by Jim Rorie
Seeing a consistent failure after upgrade to Ubuntu Karmic Koala (Version .9)
Major error: http://my.funambol.com/sync via libsoup: Cannot connect to
destination
I've seen some references to libsoup and SSL, but thought that this was a compiling problem. Any suggestions?
If you want the full dump, let me know where. I don't want to spam the list.
Jim
[2009-10-30 13:34:42.256] End of 'SyncML_Outgoing' [->top]
* [2009-10-30 13:37:51.250] TransportException thrown
at /work/runtests/head/syncevolution/src/core/SoupTransportAgent.cpp:161
*
* [2009-10-30 13:37:51.250] http://my.funambol.com/sync via
libsoup: Cannot connect to destination
*
* –[2009-10-30 13:37:51.250] 'SessionAbort' - Aborting Session,
Status=20017, ProblemSource=LOCAL [--][++] [->end]
* [2009-10-30 13:37:51.250] WARNING: Aborting Session with
Reason Status 20017 (LOCAL problem) ***
* [2009-10-30 13:37:51.250] --------------- Ignoring all
commands in this message (after 188 sec. request
processing, 188 sec. total) with Status 514 (0=none)
from here on
* –[2009-10-30 13:37:51.250] 'DSAbort' - Aborting
datastore sync, abortStatusCode=20017, localProblem=yes,
resumable=yes [--][++] [->end] [->enclosing]
* –[2009-10-30 13:37:51.250] 'SaveSuspendState' -
Saving state for
suspend/resume [--][++] [->end] [->enclosing]
* –[2009-10-30 13:37:51.250]
'SaveAdminData' - Saving changelog,
target and map
info [--][++] [->end] [->enclosing]
–[2009-10-30 13:37:51.250] End of
'SaveAdminData' [->top] [->enclosing]
–[2009-10-30 13:37:51.250] End of
'SaveSuspendState' [->top] [->enclosing]
* [2009-10-30 13:37:51.250] ***************
Warning: Datastore flagged aborted (after 188
sec. request processing, 188 sec. total) with
LOCAL Status 20017
–[2009-10-30 13:37:51.250] End of
'DSAbort' [->top] [->enclosing]
* –[2009-10-30 13:37:51.250] 'DSAbort' - Aborting
datastore sync, abortStatusCode=20017, localProblem=yes,
resumable=yes [--][++] [->end] [->enclosing]
* –[2009-10-30 13:37:51.251] 'SaveSuspendState' -
Saving state for
suspend/resume [--][++] [->end] [->enclosing]
* –[2009-10-30 13:37:51.251]
'SaveAdminData' - Saving changelog,
target and map
info [--][++] [->end] [->enclosing]
–[2009-10-30 13:37:51.251] End of
'SaveAdminData' [->top] [->enclosing]
–[2009-10-30 13:37:51.251] End of
'SaveSuspendState' [->top] [->enclosing]
* [2009-10-30 13:37:51.251] ***************
Warning: Datastore flagged aborted (after 189
sec. request processing, 189 sec. total) with
LOCAL Status 20017
–[2009-10-30 13:37:51.251] End of
'DSAbort' [->top] [->enclosing]
* +[2009-10-30 13:37:51.251] 'DSAbort' - Aborting
datastore sync, abortStatusCode=20017, localProblem=yes,
resumable=yes [--][++] [->end] [->enclosing]
* +[2009-10-30 13:37:51.251] 'DSAbort' - Aborting
datastore sync, abortStatusCode=20017, localProblem=yes,
resumable=yes [--][++] [->end] [->enclosing]
–[2009-10-30 13:37:51.252] End of 'SessionAbort'
11 years, 2 months