[SyncEvolution] Syncevolution - data preservation of unique fields
by Jeffrey Perry
I just read the Data conversion and testing page on the wiki
(http://syncevolution.org/development/data-conversion-testing)
A number of scenarios are covered, but the one which
currently interests me is the preservation of unique fields
across clients...the last test scenario covered on the wiki page.
Apparently the Synthesis library is quite capable in this regard and
so Syncevolution should be robust as well.. provided that 1) (as
mentioned in the second scenario on the page) that the XML that defines
mapping from native to internal synthesis server format is complete and
2) that the server accurately advertise their capabilities
I'm still reviewing the source code and getting my head around the
architecture... but I think I'd like to look at the XML and/or
the code segments which advertise capabilities....
The syncevolution scenario of interest to me is: N900 with gui front-end
and HTTP server setup of syncevolution on the "server" ie: desktop side.
Actually, if someone has reviewed the N900 with HTTP server use case
already, then I might be more assured - perhaps I'm worrying too much.
Thank you for your thoughts...
--Jeff
10 years, 8 months
[SyncEvolution] syncevolution-frontend 0.3 on meamo
by rustonm2005＠yahoo.co.uk
Hi All,
I have been using the sync-ui on maemo for a few weeks now and all has
been going well.
Have however recently come across a small peculiarity where it
constantly believes a sync is in progress when it isn't.
i.e.
Have tried clearing out the cache files but doesn't help so seems to be
something specific with how the gui checks for running syncs.
Sync still works fine from the command line.
Am running
syncevolution 1:0.9.2-4
and
syncevolution-frontend 0.3
Any ideas?
Matt
10 years, 8 months
Re: [SyncEvolution] Syncevolution on Nokia N900 : Force SyncML 1.1 ?
by Patrick Ohly
On Fri, 2010-04-23 at 15:46 +0100, MCm wrote:
> >> What exactly do you mean with:
> >> "In the settings profile, there is a key called "syncmlvers" which
> >> stores the SyncML version that should be used for the next sync
> >> (0=unknown, 1=1.0, 2=1.1, 3=1.2)"
> >
> > The property is called "SyncMLVersion". Who said something about
> > "syncmlvers" and gave you these numbers? We don't use 0, 1, 2, 3 in
> > SyncEvolution. We use 1.0, 1.1, 1.2:
>
> Lukas Zeller from Synthesis is saying that in this thread.
He was talking about the Synthesis XML configuration, which is not
something that you can easily edit as a SyncEvolution user.
> >> => where exactly do i have to put the string: "syncmlvers=2" ?
> >> I didn't get that...putting it in the config.ini(s), won't work...
> >
> > The easiest way to do this is via the command line:
> > syncevolution --configure --sync-property SyncMLVersion=1.1<config name>
>
> If i do this on my N900 with Syncevolution 0.9.2, i get the follwing error:
> "ERROR: '--sync-property SyncMLVersion=1.1': no such property"
Ah, I forgot. You need a 1.0 release for that. Directly editing a config
file won't help either, 0.9.x simply doesn't have this option.
Ove, I think the 1.0 beta 3 is stable enough to use it in Maemo. Do you
see a chance to update to it with your port? I remember that you said
something about making assumptions about the config.
--
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.
10 years, 8 months
Re: [SyncEvolution] Syncevolution on Nokia N900 : Force SyncML 1.1 ?
by MCm
Hello List,
unfortunatly i don't understand this:
What exactly do you mean with:
"In the settings profile, there is a key called "syncmlvers" which
stores the SyncML version that should be used for the next sync
(0=unknown, 1=1.0, 2=1.1, 3=1.2)"
=> where exactly do i have to put the string: "syncmlvers=2" ?
I didn't get that...putting it in the config.ini(s), won't work...
You will save my weekend for a little hint ;-)
Thanks in advance,
// MC Menkes
10 years, 8 months
[SyncEvolution] v1.0 beta 3 - build from source - syncevo-phone-config problem
by Bocklage, Jens
Hi,
I downloaded v1.0 beta 3 and build it.
I tried to start the syncevo-phone-config script. But it fails:
user@ubuntu:~$<mailto:user@ubuntu:~$> syncevo-phone-config --bt-address 00:XX:XX:XX:XX:XX --advanced --create-template=SonyEricsson --create-config=T610
/usr/local/bin/syncevo-phone-config:24: DeprecationWarning: The popen2 module is deprecated. Use the subprocess module.
import sys, optparse, os, time, popen2, tempfile
Traceback (most recent call last):
File "/usr/local/bin/syncevo-phone-config", line 707, in <module>
main()
File "/usr/local/bin/syncevo-phone-config", line 700, in main
tempfile = tempfile.mkdtemp(prefix="syncevo-phone-config")
UnboundLocalError: local variable 'tempfile' referenced before assignment
I am not really familiar with python, but I made some changes to the script... And now it works for me:
##################################
user@ubuntu:~$<mailto:user@ubuntu:~$> diff -Naur /home/user/Downloads/syncevolution-1.0beta3/src/syncevo-phone-config /usr/local/bin/syncevo-phone-config
--- /home/user/Downloads/syncevolution-1.0beta3/src/syncevo-phone-config 2010-04-22 02:53:40.354935678 -0700
+++ /usr/local/bin/syncevo-phone-config 2010-04-22 06:55:31.950068119 -0700
@@ -673,6 +673,8 @@
pass
def main():
+ global testFolder
+ global testResult
versions = []
sources = []
ctcaps = []
@@ -697,9 +699,9 @@
config = TestingConfiguration (versions, sources, uris, types, ctcaps,
identifiers, options.btaddr)
- tempfile = tempfile.mkdtemp(prefix="syncevo-phone-config")
- testFolder = testfile+'/data'
- testResult = testfile+'/cache'
+ testFile = tempfile.mkdtemp(prefix="syncevo-phone-config")
+ testFolder = testFile+'/data'
+ testResult = testFile+'/cache'
print "Running test with test data inside %s and test results inside %s" %(testFolder, testResult)
config.run()
##################################
Just wanted you to know,
Jens Bocklage
10 years, 8 months
[SyncEvolution] syncevolution.org reorganization: 1.0, Wiki, translations
by Patrick Ohly
Hello!
It's time to think about updating syncevolution.org to cover 1.0 and
current features. Before I actually go ahead, let me outline what I have
in mind. I'm hoping that people perusing the information there will
provide feedback so that the site remains (or becomes...) useful.
Here's roughly what I intend to do:
* Introduce a Wiki as part of the main Drupal engine. More on that
below. The goal is that this setup should make it easier to
gather user-contributed documentation (howtos, information about
compatible phones or HTTP SyncML servers).
* Improve the description of what SyncEvolution is and does.
There's a draft in http://syncevolution.org/wiki/features which
will end up "/documentation/features" and partly replace
"/documentation" itself.
* Make it as clear as possible when a certain feature was
introduced, so that we can avoid creating different copies of
the pages for different releases.
* Split up "Compatibility" and move most of the content into the
Wiki.
* Same with "Known Issues".
* Add information about sync-ui.
* Move "Development" content entirely into Wiki, with tags to find
it.
* Make more information from the source code (API, config
properties) available online (long term goal and long overdue, I
fear).
There was a offer to help with translating syncevolution.org into
Japanese. I replied back to that person that in principle I appreciate
the offer, but I'm a bit afraid of the translated content getting stale.
What do others think?
About the Wiki at http://syncevolution.org/wiki/ - right now, it is very
similar to editing normal Drupal pages, with less restrictions for
creating and editing pages. New pages all show up under "/wiki/". Mike
looked into creating overview pages based on tags. I didn't see a need
immediately, but now I think this would be useful to mark pages as
"Development", for example.
Markdown+plain HTML is the main markup method. There are no dedicated
Wiki features, like camel casing a word to create a link and then create
that page. The advantage of this approach is that content can be copied
back and forth between the "main" site and the Wiki. The disadvantage is
that linking, markup and organization is a bit more limited compared to
full-blown Wikis.
I myself would have found reStructuredText useful. Even extended Markup
was a bit limited for tables, whereas HTML is very verbose for that
purpose. But there doesn't seem to be good support for it in Drupal, so
we don't have it at the moment.
Nothing is set in stone here. Feedback welcome...
--
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.
10 years, 8 months
[SyncEvolution] Maemo 5 port + GUI
by Patrick Ohly
Hello Ove!
What's a good URL for your Maemo 5 port and its GUI? I'm looking for
something where users visiting syncevolution.org can find more
information about what it does and how to install it.
--
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.
10 years, 9 months
[SyncEvolution] SyncEvolution 1.0 beta 3 released
by Patrick Ohly
SyncEvolution 1.0 beta 3 is available. This release is feature complete
and has been tested thoroughly, so only minor bug fixes are expected
before releasing 1.0. Beta 3 is ready for day-to-day use and for
getting packaged in staging distros as replacement for 0.9.2 or previous betas.
If you find issues, please report them: http://syncevolution.org/support
Binary packages are provided, including Bluetooth support. Major improvements:
* automatic, time-driven synchronization in the background
* command line integrates properly into the daemon concept
* full support for suspend&resume and message resend when using
SyncEvolution as client and server
* compatible with more phones
* a tool to determine a working configuration for a phone
automatically ("syncevo-phone-config")
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 the release of 1.0 is close, the documentation on syncevolution.org
is getting updated to cover it. A Wiki was set up as part of the site to
simplify the editing of certain pages, in particular HOWTOs and compatibility
reports.
*Call for action*: test with your phone and report which config works
and how well synchronization works. See
http://syncevolution.org/development/sync-phone
http://syncevolution.org/wiki/phone-compatibility-template
Details
=======
Automatic synchronization is supported by the syncevo-dbus-server (MB
#6378). When that is installed, it will be started as part of a user
session and keep running to trigger syncs in the
background. Notifications are emitted when syncs start, end or fail
(MB #10000).
Automatic synchronization can be enabled separately for each peer
("autoSync=0/1", off by default), will be done at regular intervals
("autoSyncInterval=30" minutes) when online long enough
("autoSyncDelay=5" minutes). That last option ensures that a) an
automatic sync does not attempt to use a network connection unless it
was already active and b) hopefully is also around long enough to
complete the sync.
Detecting online status depends on ConnMan. Without it, SyncEvolution
assumes that the network is available. For Bluetooth it is enough to
have a peer paired.
When SyncEvolution is compiled with a backend sync daemon
("syncevo-dbus-server"), then conceptually that daemon controls the
configuration and coordinates manually and automatically started sync
sessions. Previously, the command line tool bypassed the daemon by
running operations itself. Now it can hand over the command line
parameters to the daemon to be executed there ("--daemon=yes", the
default if the daemon is available; MB #5043). Command line parameters
and output of "syncevolution" are the same as before. Note that the
daemon only runs one operation at a time, which delays the command
line client when the daemon is busy. For testing purposes (like
running a client which talks to a local server in the daemon) it is
still possible to ignore the daemon (--daemon=no).
Thanks to fixes and improvements in both Synthesis engine and
SyncEvolution, suspend and resume are fully supported in client and
server (MB #2425). Previously it failed in some cases, as mercilessly
exposed by our automated testing. Now all of these tests pass. The
HTTP server now also handles message resends by clients correctly.
Direct synchronization with older phones (like Sony Ericsson K750i)
can be started now by switching to an older version of the SyncML
standard ("SyncMLVersion" property, MB #9312). No further
interoperability testing with such phones has been done at this
time. When acting as client, that same property allows talking to
older SyncML servers, like desknow.com.
A minor workaround and the right configuration make it possible to
synchronize with Nokia N85 and probably also other S60
devices. Added a template for "Nokia S60". Also made the template
for "Nokia N900" accessible in the GTK GUI.
Because determining which configuration works for a phone involves
a lot of trial-and-error, the new "syncevo-phone-config" script
automates that process.
Other changes:
* Mobical.net (and other, similar services): fix vCalendar 1.0 alarm
specifications before importing them (MB #10458)
* Nokia N900: added a config template for it and disabled the redundant
RespURI when using Bluetooth. Preliminary testing shows that this solves
some of the issues seen before (MB #10224).
* workaround for Evolution 2.30: "timezone cannot be retrieved because it
doesn't exist" is triggered incorrectly when importing non-standard
timezone definitions because libecal change an error code (MB #9820)
* "syncevo-http-server" HTTP server script is included in normal install
* syncevolution.org binaries: finally solved the libbluetooth3
incompatibility (MB #9289). Binaries of beta 2 crashed on more
recent distros because of that.
* SyncML client and Bluetooth: a mobile device running SyncEvolution
creates a configuration automatically (MB #6175). The peer contacting
us has to use the standard SyncEvolution URIs (addressbook, calendar,
todo, memo).
* command line: when dealing with the shared non-peer part of a config,
it checks for properties which are unsuitable only prints
those (MB #8048)
* GTK GUI: improved setup of devices, automatic sync switch,
some fixes for crashes and other tweaks
* Nokia 7210c: send time as UTC instead of relying on time zone
information (MB #9907).
* command line: setting up a configuration for a "SyncEvolution"
server on a client was not possible because the "SyncEvolutionClient"
configuration was picked instead (MB #10004). The latter has to
be used when configuring a SyncEvolution server to talk to a
SyncEvolution client.
* restore: no longer updates the time of the backup (MB #9963)
* various minor improvements and fixes, see ChangeLog
Upgrading:
* The new "RetryInterval" property causes messages to be resent
after 2 minutes (increased from 1 minute in previous 1.0 betas).
At least the Funambol server is known to not handle this correctly
in all cases (http://funzilla.funambol.com/show_bug.cgi?id=7910).
So in the Funambol config template the interval is set to zero,
disabling the feature. Enabling or disabling the feature must
be done manually in existing configurations.
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2010/syncevolution-10beta3-released
Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources
i386, amd64 and lpia binaries of 1.0 beta 3 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
--
Patrick Ohly, on behalf of everyone who has helped
to make SyncEvolution possible:
http://syncevolution.org/about/contributors
10 years, 9 months
[SyncEvolution] sync-ui/syncevolution in Ubuntu 10.04?
by thomas
Hi
What are the plans for sync-ui/syncevolution in Ubuntu 10.04?
Currently, latest versions are
sync-ui is version 0.9.1+ds1.1
syncevolution is version 0.9.1+ds1-1
libsynthesis0 is version 3.4.0.5-ds1-1
I have been using the latest alpha and beta versions of Ubuntu 10.04,
and sync has been broken long time now. Syncevolution say:
Fatal: Cannot connect to datastore implementation module specified in
<plugin_module>
Fatal error 20010, no valid configuration could be read from XML file
[ERROR] Synthesis XML config parser error
When running sync-ui, it fails with "Fatal database error" and the log says:
*[2010-04-11 22:00:41.782] Resolving - <name unknown>, ctx=0x92F52C8,
VarDefs:
* [2010-04-11 22:00:41.795] Resolving - incomingscript, ctx=0x92F4CE0,
VarDefs:
* [2010-04-11 22:00:41.796] 0: string MATCHES[]
* [2010-04-11 22:00:41.796] 1: string CAT
* [2010-04-11 22:00:41.796] 2: string CN
* [2010-04-11 22:00:41.796] 3: string EM
* [2010-04-11 22:00:41.796] 4: integer i
* [2010-04-11 22:00:41.796] 5: timestamp exdate
* [2010-04-11 22:00:41.796] Resolving - outgoingscript, ctx=0x92F4CE0,
VarDefs:
* [2010-04-11 22:00:41.796] 0: string MATCHES[]
* [2010-04-11 22:00:41.797] 1: string CAT
* [2010-04-11 22:00:41.797] 2: string CN
* [2010-04-11 22:00:41.797] 3: string EM
* [2010-04-11 22:00:41.797] 4: integer i
* [2010-04-11 22:00:41.797] 5: timestamp exdate
* [2010-04-11 22:00:41.797] Resolving - incomingscript, ctx=0x92F4CE0,
VarDefs:
* [2010-04-11 22:00:41.797] 0: string MATCHES[]
* [2010-04-11 22:00:41.798] 1: string CAT
* [2010-04-11 22:00:41.798] 2: string CN
* [2010-04-11 22:00:41.798] 3: string EM
* [2010-04-11 22:00:41.798] 4: integer i
* [2010-04-11 22:00:41.798] 5: timestamp exdate
* [2010-04-11 22:00:41.798] Resolving - outgoingscript, ctx=0x92F4CE0,
VarDefs:
* [2010-04-11 22:00:41.798] 0: string MATCHES[]
* [2010-04-11 22:00:41.798] 1: string CAT
* [2010-04-11 22:00:41.798] 2: string CN
* [2010-04-11 22:00:41.798] 3: string EM
* [2010-04-11 22:00:41.799] 4: integer i
* [2010-04-11 22:00:41.799] 5: timestamp exdate
* [2010-04-11 22:00:41.799] SyncML server account:
####################
* [2010-04-11 22:00:41.799] client: SyncEvolution 0.9.1 for desktop
* [2010-04-11 22:00:41.799] device ID:
################################
* [2010-04-11
22:00:41.859] creating /home/thomas/.cache/syncevolution/memotoo-2010-04-11-22-00/addressbook.before
* [2010-04-11
22:00:41.861] /home/thomas/.cache/syncevolution/memotoo-2010-04-11-22-00/addressbook.before created
* [2010-04-11
22:00:41.861] creating /home/thomas/.cache/syncevolution/memotoo-2010-04-11-22-00/calendar.before
* [2010-04-11
22:00:41.862] /home/thomas/.cache/syncevolution/memotoo-2010-04-11-22-00/calendar.before created
* [2010-04-11
22:00:41.863] creating /home/thomas/.cache/syncevolution/memotoo-2010-04-11-22-00/memo.before
* [2010-04-11
22:00:41.864] /home/thomas/.cache/syncevolution/memotoo-2010-04-11-22-00/memo.before created
* [2010-04-11
22:00:41.864] creating /home/thomas/.cache/syncevolution/memotoo-2010-04-11-22-00/todo.before
* [2010-04-11
22:00:41.865] /home/thomas/.cache/syncevolution/memotoo-2010-04-11-22-00/todo.before created
* [2010-04-11 22:00:42.893] Resolving - <name unknown>, ctx=0x92FE638,
VarDefs:
* [2010-04-11 22:00:42.911] Resolving - initscript, ctx=0x93072E0,
VarDefs:
* [2010-04-11 22:00:42.911] 0: string itemdata
* [2010-04-11 22:00:42.911] Resolving - afterreadscript,
ctx=0x93072E0, VarDefs:
* [2010-04-11 22:00:42.912] 0: string itemdata
* [2010-04-11 22:00:42.912] Resolving - beforewritescript,
ctx=0x93072E0, VarDefs:
* [2010-04-11 22:00:42.912] 0: string itemdata
* [2010-04-11 22:00:42.912] 1: integer i
* [2010-04-11 22:00:42.912] 2: integer wanted
* [2010-04-11 22:00:42.912] 3: integer cell_phones
* [2010-04-11 22:00:42.913] Resolving - initscript, ctx=0x9365828,
VarDefs:
* [2010-04-11 22:00:42.913] 0: string itemdata
* [2010-04-11 22:00:42.913] Resolving - afterreadscript,
ctx=0x9365828, VarDefs:
* [2010-04-11 22:00:42.913] 0: string itemdata
* [2010-04-11 22:00:42.913] Resolving - beforewritescript,
ctx=0x9365828, VarDefs:
* [2010-04-11 22:00:42.913] 0: string itemdata
* [2010-04-11 22:00:42.914] Resolving - initscript, ctx=0x9368190,
VarDefs:
* [2010-04-11 22:00:42.914] 0: string itemdata
* [2010-04-11 22:00:42.914] Resolving - afterreadscript,
ctx=0x9368190, VarDefs:
* [2010-04-11 22:00:42.914] 0: string itemdata
* [2010-04-11 22:00:42.914] Resolving - beforewritescript,
ctx=0x9368190, VarDefs:
* [2010-04-11 22:00:42.914] 0: string itemdata
* [2010-04-11 22:00:42.915] Resolving - initscript, ctx=0x9369130,
VarDefs:
* [2010-04-11 22:00:42.915] 0: string itemdata
* [2010-04-11 22:00:42.915] Resolving - afterreadscript,
ctx=0x9369130, VarDefs:
* [2010-04-11 22:00:42.915] 0: string itemdata
* [2010-04-11 22:00:42.915] Resolving - beforewritescript,
ctx=0x9369130, VarDefs:
* [2010-04-11 22:00:42.916] 0: string itemdata
* [2010-04-11 22:00:42.918] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_start' (size=12) err=0
* [2010-04-11 22:00:42.918] ##### DBApi (LNK): Connect:
fSDKversion=V1.6.0.0
* [2010-04-11 22:00:42.918] ##### SyncEvolution (LNK):
Module_CreateContext: 'SyncEvolution' (addressbook) => 0
* [2010-04-11 22:00:42.918] ##### DBApi (LNK): Connect:
mContext=0930A100 err=0
* [2010-04-11 22:00:42.918] ##### SyncEvolution (LNK): Module_Version:
01060000
* [2010-04-11 22:00:42.918] ##### SyncEvolution (LNK):
Module_Capabilities: 'PLATFORM:Linux
DLL:true
MINVERSION:V1.0.6.0
MANUFACTURER:SyncEvolution
DESCRIPTION:SyncEvolution Synthesis DB Plugin
plugin_datastore_str:no
plugin_datastore_key:yes
ITEM_AS_KEY:yes
plugin_datablob:no
'
* [2010-04-11 22:00:42.919] ##### DBApi (LNK): MinVersionCheck:
engine=010700FF >= 01000600 / err=0
* [2010-04-11 22:00:42.919] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_param' (size=4) err=0
* [2010-04-11 22:00:42.920] ##### DBApi (LNK): DBApi_Assign:
aKey='' (size=228) err=0
* [2010-04-11 22:00:42.920] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_se' (size=56) err=0
* [2010-04-11 22:00:42.920] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_sessionauth' (size=12) err=0
* [2010-04-11 22:00:42.920] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_deviceadmin' (size=16) err=0
* [2010-04-11 22:00:42.920] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_dbtime' (size=4) err=0
* [2010-04-11 22:00:42.920] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_sessionadapt' (size=4) err=0
* [2010-04-11 22:00:42.921] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_ds' (size=136) err=0
* [2010-04-11 22:00:42.921] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_datageneral' (size=20) err=0
* [2010-04-11 22:00:42.921] ##### DBApi (LNK): DBApi_Assign:
aKey='plugin_datablob_OLD2' (size=12) err=404
* [2010-04-11 22:00:42.921] ##### SyncEvolution (LNK):
Module_DisposeObj: free at 0936B048 'PLATFORM:Linux
DLL:true
MINVERSION:V1.0.6.0
MANUFACTURER:SyncEvolution
DESCRIPTION:SyncEvolution Synthesis DB Plugin
plugin_datastore_str:no
plugin_datastore_key:yes
ITEM_AS_KEY:yes
plugin_datablob:no
'
* [2010-04-11 22:00:42.922] ##### DBApi (LNK): DispGlobContext:
g=0932A200 mCB->gContext=0932A200
* [2010-04-11 22:00:42.922] ##### DBApi (LNK): DispGlobContext:
g=0932A200 g->ref=00000000 g->cnt=0 ''
* [2010-04-11 22:00:42.922] ##### DBApi (LNK): DispGlobContext:
g=0932A260 g->ref=00000000 g->cnt=0 ''
* [2010-04-11 22:00:42.922] ##### DBApi (LNK): DispGlobContext:
g=092F53B8 g->ref=00000000 g->cnt=0 ''
* [2010-04-11 22:00:42.922] ##### DBApi (LNK): DispGlobContext: (eof)
* [2010-04-11 22:00:42.922] ##### (LNK): DeleteGlobContext
* [2010-04-11 22:00:42.923] ##### DBApi (LNK): DispGlobContext:
g=00000000 mCB->gContext=0932A200
* [2010-04-11 22:00:42.923] ##### DBApi (LNK): DispGlobContext: (eof)
* [2010-04-11 22:00:42.923] ##### DBApi (LNK): Connect: err=404
'SyncEvolution' (DLL)
* [2010-04-11 22:00:42.924] Synthesis XML config parser error
* [2010-04-11 22:00:42.924] ##### enginemodulebase (LNK): Disconnect
Ubuntu 10.04 is soon ready to ship, so maybe it's time to make sure it
includes something that works.
Well, keep up the good work and thank you to all.
--
thomas <lianergoist(a)tj-software.dk>
10 years, 9 months
