[SyncEvolution] compiling more than one gui
by Peter Robinson
Hi All,
I'm trying to compile both the moblin and gtk guis for syncevolution
and there doesn't seem to be a way to do so. I've tried various
combinations of gtk and moblin on the --enable-gui= option but there
doesn't appear to be a way to get it to compile both. Is it possible
to add an "all" option so you can do --enable-gui=all and get both the
guis?
Cheers,
Peter
12 years, 9 months
[SyncEvolution] new web site, new mailing list(s)
by Patrick Ohly
Hello!
Things are moving fast... SyncEvolution is now on syncevolution.org. We
wanted to get this done quickly so that it could be announced as part of
SyncEvolution 0.9 beta 3, therefore there wasn't much time to discuss
the new site in advance.
Overall I'm happy with the result. I'm sure there will be some tweaks
necessary, in particular to cover 0.9. Right now the material is a
direct copy of the 0.8 estamos.de pages. If you notice something that
should be changed, please comment.
For the core developers, please consider a) whether you want to be
mentioned and b) how. I've already added some people just with their
names and a short summary of what they have done so far:
http://syncevolution.org/about/contributors
The mailing lists were also moved. I was told that this would be
entirely transparent (same subscribers, old email addresses and URL
remain valid, archive moved), but there were hickups. The @moblin.org
addresses still don't seem to work again, so if you want to post to this
list, please use syncevolution(a)syncevolution.org.
Earlier I had already added another mailing list which is copied on all
issue changes in Bugzilla, syncevolution-issues. The main purpose of
that list is to get the issues archived in a way that is visible to
search engines. People can subscribe, but if you want to follow all
issues, better create an account on bugzilla.moblin.org and "watch" the
"syncevolution AT lists.intel.com" account (" AT " replaced with @).
This allows filtering which changes should be reported by email.
I've had some discussions with the admins about listing the contents of
downloads.syncevolution.org and runtests.syncevolution.org (nightly test
results). The site runs under nginx, which supports directory listings
but isn't as flexible as Apache about it.
For downloads it works almost well enough, showing the content of
README.txt as part of the listing would be nice.
For runtests, much of the tweaking that went into estamos.de/runtests no
longer works, so reading the results is harder than before. Yongsheng
has started working on a conversion of the results into static HTML
pages, which would be useful to simplify navigation.
However, long-term I think it would be more productive to have an
interactive system which can answer queries that combine different test
results (over time, platform comparisons, ...). "Continuous integration"
systems [1] do that (and probably a lot more). We just need the
component which visualizes the results based on a simple data model of
"platform", "platform attributes", "test", "test attributes", "test
result link", "success/failure/skipped" and can accept such results via
mail or HTTP POST.
Does anyone have an recommendations for such a tool?
[1] http://en.wikipedia.org/wiki/Continuous_integration#Software
--
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, 9 months
Re: [SyncEvolution] SyncML Tests 2009-07-22: head-evolution-testing
by Patrick Ohly
Hi!
Analysis of nightly testing...
On Thu, 2009-07-23 at 03:05 +0100, Ohly, Patrick wrote:
> http://runtests.syncevolution.org/2009-07-22-22-00/head-evolution-testing
>
> libsynthesis successful
> syncevolution successful
> compile successful
> dist skipped: disabled in configuration
> evolution successful
These tests also worked without problems for the other build platforms.
> scheduleworld: failed
The server become unavailable half-way through the tests. For example:
ClientTest.cpp:3813:Assertion
Test name: Client::Sync::text::testManyItems
equality assertion failed
- Expected: 0
- Actual : 20043
>From the corresponding log:
# unexpected HTTP response: status 502/Bad Gateway, content type text/html, body:
<html>
<head>
<title>The page is temporarily unavailable</title>
<style>
body { font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body bgcolor="white" text="black">
<table width="100%" height="100%">
<tr>
<td align="center" valign="middle">
The page you are looking for is temporarily unavailable.<br/>
Please try again later.
</td>
</tr>
</table>
</body>
</html>
# TransportException thrown at /work/runtests/head/syncevolution/src/core/SoupTransportAgent.cpp:161
# http://ns5.scheduleworld.com/funambol/ds via libsoup: Bad Gateway
> memotoo skipped: disabled in configuration
> egroupware skipped: disabled in configuration
> synthesis successful
> funambol: failed
Only one failure:
ClientTest.cpp:3813:Assertion
Test name: Client::Sync::text::testItemsXML
equality assertion failed
- Expected: 0
- Actual : 20043
# TransportException thrown at /work/runtests/head/syncevolution/src/core/SoupTransportAgent.cpp:161
# http://my.funambol.com/sync via libsoup: Connection terminated unexpectedly
> zyb: failed
Not expected to pass at this point, not checked.
> google: failed
Hmm, didn't work with http://m.google.com/syncml
# unexpected HTTP response: status 404/Not Found, content type text/html; charset=UTF-8, body:
<html><head><title>404 Not Found</title>
[...]
</html>
# TransportException thrown at /work/runtests/head/syncevolution/src/core/SoupTransportAgent.cpp:161
# http://m.google.com/syncml via libsoup: Not Found
I get different responses in a web browser for
http://m.google.com/syncml and https://m.google.com/syncml. But that's
not the problem http works fine here on my desktop.
The URI also seems correct ("contacts"). Not sure why it failed. Perhaps
a temporary issue on the server?
--
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, 9 months
[SyncEvolution] status update 23.07.2009, SyncEvolution 0.9 beta 3 released
by Patrick Ohly
Hi!
This list is from Monday morning. Because of the preparations for 0.9
beta 3 and the mailing list issues I didn't sent it out earlier. Since
then, Google contact sync was merged. It's the first SyncML server with
SSL support. However, the certificate checking remains problematic with
libsoup/gnutls (Bugzilla #2431).
Intel QA did a full test and came to the conclusion that SyncEvolution
basically works as intended. Some issues in the GUI were found and since
then fixed. All the code issues for SyncEvolution 0.9 are now resolved.
As long as time permits, we keep working on server interoperability as
the main remaining work item for SyncEvolution 0.9:
* We finished testing of Funambol calendar and todo support and
enabled it, in addition to resting contact and notes support.
* Google contact sync is analyzed and ready to be merged. The
server is more limited than others (no refresh from client sync)
and has some unusual server-side policies (contacts cannot be
removed completely by client, which is problematic for testing
and leads to data loss when the server decides to preserve its
own, older copy instead of adding a newer version of the same
contact again).
* ZYB.com/Vodafone sync used to work, but currently fails to do
two-way syncs (anchor mismatch, root cause unknown). ZYB is
working with us on this.
Automated testing is fully operational now. It covers compilation with
multiple different Evolution releases/Linux distros via chroots in 32
and 64 bit mode, strict compiler warning checking, valgrind testing
(including leaks). Binaries are packaged for those users who want to
test/use the latest release but cannot build from source.
Development progress:
* Yongsheng: analyzed ZYB.com test failures (unexpected slow sync
due to local setting changes, unsupported properties, currently
fails due to anchor mismatch); finished Funambol testing
* Congwu: Google contact sync workarounds (improved libsynthesis
statistics code to cope with less informative status codes),
suspend/resume tests with Funambol (fails in some cases due to
server deficienies); OVI.com sync impossible (no credentials -
need assistance from Nokia, but don't have contact)
* Jussi: fixed password handling regressions, insufficient button
size in some locales, updated translation README
* Patrick: redirect stderr into log file to hide GNOME
debug/warning output from user, unified logging into .html file,
nightly testing on several platforms, SSL certificate checking
in Moblin (ca-certificates package still needs to be integrated
by distro team), Debian EDS crash (fatal errors in libical)
--
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, 9 months
[SyncEvolution] SyncEvolution 0.9 beta 3 released: binaries available on http://syncevolution.org
by Patrick Ohly
The end is near - SyncEvolution 0.9 is almost done. For the first time
in the 0.9 series, precompiled binaries are made available again
together with the new 0.9 beta 3 source snapshot. Users are encouraged
to upgrade now and give feedback before the final 0.9 release. See below
for upgrade and install instructions.
The project itself keeps growing. Therefore the main web presence has
been moved to its own independent home:
http://syncevolution.org
Changes since 0.9 beta 2
========================
Enabled calendar and task synchronization for myFunambol.com. Not all
iCalendar 2.0 features are supported by the server, most notably support
for meetings (drops attendees), meeting invitations (drops UID),
detached recurrences (drops RECURRENCE-ID). See README.funambol for
details.
Interoperability with the Funambol server was improved by adding support
for some vCard extensions (X-MANAGER/ASSISTANT/SPOUSE/ANNIVERSARY,
Bugzilla #2418). Lost ACTION property is worked around (#2422).
Synchronization with Google Contacts was enabled and tested. A
configuration template for that server is now provided. Google follows
the vCard 2.1 specification and thus does not support some of the vCard
3.0 additions, nor some of the common extensions. As a result, several
properties are not synchronized (nickname, birthday, spouse/manager,
URLs, ...). Only one top-level organization seems to be supported. For
details, see README.google.
Regarding Google's SyncML support, refresh-from-client and
one-way-from-client sync modes are not supported. Deleting contacts
moves them out of the main address without deleting them permanently.
When adding such a contact again, the server discards the data sent by
the client and recreates the contact with the data that it remembered.
SSL certificate checking with libsoup (the default transport) is now
supported (#2431). However, libsoup/gnutls are very strict about SSL
certificate checking and reject version 1 certificates, like the one
used by Verisign for Google (#4551). At the moment the only solution is
to fall back to plain http in the Google configuration template.
CTRL-C no longer kills SyncEvolution right away. Instead it asks the
server to suspend the session. If that takes too long, then pressing
CTRL-C twice quickly will abort the sync without waiting for the server
(warning, this may lead to a slow sync in the next session).
WBXML is enabled by default now, except for Funambol (#2415). Using
WBXML reduces message sizes and increases parsing performance. It was
not enabled initially in the 0.9 releases in order to test this new
feature more thoroughly. Old configs don't have an explicit enableWBXML
setting and therefore will automatically use the new default.
Various bug fixes and improvements:
* only show servers in GUI which are tested and supported (Bugzilla #3336)
* a single log file is written in .html format (#3474)
* added several translations of the GUI
* lots of testing improvements, build binary packages again
Upgrading
When enabling calendar and todo synchronization with Funambol in an
existing configuration, set the type so that iCalendar 2.0 is used:
syncevolution --configure --source-type sync=two-way \
funambol calendar todo
syncevolution --configure \
--source-type type='calendar:text/calendar!' \
funambol calendar
syncevolution --configure \
--source-type type='todo:text/calendar!' \
funambol todo
When creating a configuration anew, this is not necessary because the
configuration template contains those types.
When upgrading from 0.8 or downgrading again, do a "refresh-from-server"
or "refresh-from-client" sync (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.
If unsure, run a normal sync with the command line tool and check for
unwanted data modifications in its output. With the "--list-sessions"
and "--restore --before" options it is possible to revert to the local
state before that last sync and then update the server accordingly in a
normal, incremental sync.
Source, Installation, Further information
=========================================
Main project page: http://syncevolution.org/
Technical information: http://moblin.org/projects/syncevolution/
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).
.tar.gz archives are also available in
http://downloads.syncevolution.org/syncevolution/evolution. In contrast
to 0.8.x archives, the 0.9 files have to be unpacked and then moved
to /usr, because several files would not be found otherwise.
After installation, follow the
http://syncevolution.org/documentation/getting-started steps.
--
Bye, Patrick Ohly
--
Patrick.Ohly(a)gmx.de
http://www.estamos.de/
12 years, 9 months
