<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.mobile.syncevolution">
    <title>gmane.comp.mobile.syncevolution</title>
    <link>http://blog.gmane.org/gmane.comp.mobile.syncevolution</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4338"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4337"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4336"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4335"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4334"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4333"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4332"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4331"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4330"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4329"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4328"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4327"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4326"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4325"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4324"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4323"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4322"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4321"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4320"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4319"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4338">
    <title>Re: google CARDDAV 404</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4338</link>
    <description>&lt;pre&gt;
That URL works for me here when using an account on a Google Apps
instance, using HTTP authentication. It fails for a normal GMail account
because Google requires authentication via GoogleLogin, which is the new
OAuth mechanism.

The filtering is not based on a user-agent string. Instead the app has
to be registered with Google and has to present a valid, known private
key during SyncEvolution.

SyncEvolution can't do that because a) it is not registered (Google has
not replied to my requests to accept SyncEvolution as client) and b) the
necessary code for the new authentication mechanism hasn't been written.


&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-05-21T10:04:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4337">
    <title>Re: sync timeouts for syncevo-http-server + nokia e51 phone</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4337</link>
    <description>&lt;pre&gt;
Not in the normal SyncEvolution, because it didn't use the feature that
Lukas described.

But in the meantime I have implemented the necessary changes
(thread-safety, config option) in SyncEvolution, so when compiling from
source it is possible. Hmm, I thought I had sent you an email about
that, but I can't find it.

If you want a tar ball, try this:
http://downloads.syncevolution.org/tmp/syncevolution-1.3.99.3%2b20130514%2bSE%2bde24470%2bunclean%2bSYSYNC%2b3366831.tar.gz

It should use the feature by default. The full documentation is this:

'--sync-property SyncMLVersion=?'
   On a client, the latest commonly supported SyncML version
   is used when contacting a server. One of '1.0/1.1/1.2' can
   be used to pick a specific version explicitly.
   
   On a server, this option controls what kind of Server Alerted
   Notification is sent to the client to start a synchronization.
   By default, first the format from 1.2 is tried, then in case
   of failure, the older one from 1.1. 1.2/1.1 can be set
   explicitly, which disables the automatism.
   
   Instead or in adddition to the version, several keywords can
   be set in this property (separated by spaces or commas):
   
   - NOCTCAP - avoid sending CtCap meta information
   - NORESTART - disable the sync mode extension that SyncEvolution
     client and server use to negotiate whether both sides support
     running multiple sync iterations in the same session
   - REQUESTMAXTIME=&amp;lt;time&amp;gt; - override the rate at which the
     SyncML server sends preliminary replies while preparing
     local storages in the background. This helps to avoid timeouts
     in the SyncML client. Depends on multithreading.
     This SyncEvolution binary is thread-safe and thus this feature
     is enabled by default for HTTP servers, with a delay of 2 minutes
     between messages. Other servers (Bluetooth, local sync) should not
     need preliminary replies and the feature is disabled, although
     it can be enabled by setting the time explicitly.
     &amp;lt;time&amp;gt; can be specified like other durations in the config,
     for example as REQUESTMAXTIME=2m.
   
   Setting these flags should only be necessary as workaround for
   broken peers.

&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-05-20T19:14:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4336">
    <title>Re: sync timeouts for syncevo-http-server + nokiae51 phone</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4336</link>
    <description>&lt;pre&gt;Hello,

Am Montag, 13. Mai 2013, 22:30:58 schrieb Lukas Zeller:




Does that mean I can already set a larger timeout for my nokia e51?
Say... 2 hours?

Christof

&lt;/pre&gt;</description>
    <dc:creator>Christof Schulze</dc:creator>
    <dc:date>2013-05-20T15:42:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4335">
    <title>Re: google CARDDAV 404</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4335</link>
    <description>&lt;pre&gt;As ssl is now mandatory, after some lab work I managed to mitm an Ipod
Touch.
It uses as addressbook/database :
https://google.com/carddav/v1/principals/[username]%40gmail.com/lists/default/&amp;lt;https://google.com/m8/carddav/principals/__uids__/default/lists/default/&amp;gt;
where [username] is the gmail user.

In case of future user-agent filtering, ios uses:
iOS/6.1 (10B144) dataaccessd/1.0


2013/5/8 Patrick Ohly &amp;lt;patrick.ohly-ral2JQCrhuEAvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

_______________________________________________
SyncEvolution mailing list
SyncEvolution-iSTEHRHt8w9N2k9L2T2VtNi2O/JbrIOy&amp;lt; at &amp;gt;public.gmane.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution
&lt;/pre&gt;</description>
    <dc:creator>Juan Antonio Zuloaga Mellino</dc:creator>
    <dc:date>2013-05-20T09:24:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4334">
    <title>Re: baseline distro for SyncEvolution 1.4?</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4334</link>
    <description>&lt;pre&gt;
Thanks for the information. Ubuntu 10.04 for desktops will reach its end
of life (= no more security updates) this month. 10.04 for servers will
be supported longer, but I guess I'll make the jump to a newer baseline
for SyncEvolution 1.4.

I'll make sure that the source still compiles on older distros. That's
necessary for the Nokia Internet Tablets and the N9.


I'm sure it'll take a few more months before 1.4 is ready. I don't have
a firm timeline yet, though.



The syncevolution-bundle can be installed without also having to install
Evolution libs or KDE. The backends for these PIM storages will just not
be usable without them. syncevolution-evolution and syncevolution-kde
are meta packages with additional dependencies on the Evolution resp.
KDE/Akonadi libraries, so when installing those, one can be sure to have
a usable system.


&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-05-15T06:41:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4333">
    <title>use syncevolution to sync nokia C5-00 with owncloud</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4333</link>
    <description>&lt;pre&gt;Good Day Ladies and Gentlemen,

I have the a setup consisting of a simple nokia-symbian phone which is
connected via bluetooth to my linux+kde machine and a server running
owncloud.

Until some days ago, I used Akonadi to synchronize my PC with owncloud
contacts and calendars and used syncevolution to synchronize my Nokia
Phone with Akonadi.

That was working quite well...

Unfortunately Akonadi is a little bit buggy, so I switched from kde-pim
to Thunderbird.


Consequently, I can't use akonadi as a datasource for syncevolution.


So I wondered If I could tell syncevolution to access my
owncloud/caldav/carddav directly.

How does my config look like right now:

default
  |
  |-peers
      |-nokiaPhoneRelatedStuff
  |-sources
      |-addressbook, with CardDav Config
       -etc.


But somehow, I don't get the thing working.
Do you know some kind of tutorial how to uses syncevolution to sync a
Mobile phone via bluetooth with a CalDav / CardDav Server?


I already had a look at the instructions
https://syncevolution.org/documentation/syncevolution-usage#caldav-and-carddav
but couldn't put the acquired knowledge to any use.





Best Regards

Dustin
&lt;/pre&gt;</description>
    <dc:creator>Dustin Demuth</dc:creator>
    <dc:date>2013-05-14T12:45:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4332">
    <title>Re: sync timeouts for syncevo-http-server + nokiae51 phone</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4332</link>
    <description>&lt;pre&gt;Hello Patrick,

On 13.05.2013, at 17:55, Patrick Ohly &amp;lt;patrick.ohly-ral2JQCrhuEAvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


Thanks!


:-) Neither time nor motivation is unlimited...


No, once again just me pressing the wrong buttons in my mailer :-(

Best Regards,

Lukas


Lukas Zeller, plan44.ch
luz-DkgZRUgWWJ3tRgLqZ5aouw&amp;lt; at &amp;gt;public.gmane.org - www.plan44.ch
&lt;/pre&gt;</description>
    <dc:creator>Lukas Zeller</dc:creator>
    <dc:date>2013-05-13T20:37:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4331">
    <title>Re: sync timeouts for syncevo-http-server + nokiae51 phone</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4331</link>
    <description>&lt;pre&gt;Hello Patrick,

On 23.04.2013, at 18:17, Patrick Ohly &amp;lt;patrick.ohly-ral2JQCrhuEAvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


Years ago, the device that caused me implementing this was the Ericsson T68i which had no more than 30 seconds "patience". 

Looking at the default config of the server, it seems that we settled on 120 seconds for the global &amp;lt;requestmaxtime&amp;gt;. However it is possible to set a per-device &amp;lt;requestmaxtime&amp;gt; in the remote rule. Curiously, the T68i in the sample config does not set 30 seconds, though. Maybe later revisions had a more generous timeout, or nobody used that device ever again...

Best Regards,

Lukas
&lt;/pre&gt;</description>
    <dc:creator>Lukas Zeller</dc:creator>
    <dc:date>2013-05-13T20:30:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4330">
    <title>Re: google CARDDAV 404</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4330</link>
    <description>&lt;pre&gt;
I need to check this when I have more time.


There's some preliminary code for a google-api to vcard converter in the
gdatasource branch. But work on that stopped before it was usable as a
backend in SyncEvolution.

&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-05-08T07:24:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4329">
    <title>google CARDDAV 404</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4329</link>
    <description>&lt;pre&gt;Google carddav stopped working, but there was no announcement.
The only reference I could find was this thread:

https://inverse.ca/sogo/lists/arc/users/2013-04/msg00008.html

I used to connect with this configuration:
--CODE--
syncevolution --keyring=no --configure \
              username=&amp;lt;user&amp;gt;&amp;lt; at &amp;gt;gmail.com \
              password=&amp;lt;password&amp;gt; \
              addressbook/backend=carddav \
              addressbook/database=https://google.com/m8/carddav/principals/__uids__/default/lists/default/
\
              target-config&amp;lt; at &amp;gt;webdav \
              addressbook
--/CODE--

It fails with:

--OUTPUT--
[INFO] addressbook: backend failed: error code from SyncEvolution object
not found (remote, status 404): PROPFIND: Neon error code 1: 404 Not
Found
[ERROR] error code from SyncEvolution object not found (remote, status
404): PROPFIND: Neon error code 1: 404 Not Found
--/OUTPUT--

Lack of complains indicates that iPod/Pad/Phone and windows[78] phone
sync still works.

So it might be true that google started whitelisting the server.

Can anyone confirm this?

Is anybody working on a google-api for syncevolution?
&lt;/pre&gt;</description>
    <dc:creator>Juan Antonio Zuloaga Mellino</dc:creator>
    <dc:date>2013-05-08T05:35:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4328">
    <title>baseline distro for SyncEvolution 1.4?</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4328</link>
    <description>&lt;pre&gt;Hello!

So far, syncevolution.org binaries were compiled on Ubuntu Lucid 10.04
LTS, which made the binaries compatible with pretty much all distros
since then, including Debian Stable. Since then, another Ubuntu LTS
(Precise Pangolin, 12.04) was released and Debian Wheezy became Debian
Stable this weekend.

Does anyone still need SyncEvolution binaries for Ubuntu Lucid 10.04 and
Debian Squeeze?

I'd like to switch to Ubuntu Precise as new baseline distro because then
binaries can use features from glib 3.32.0, more precisely, the revised
multithreading API. Then SyncEvolution can prevent premature client
timeouts when acting as SyncML HTTP server by running long-running local
storage initialization in a background thread.

&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-05-06T09:04:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4327">
    <title>Re: Syncevolution 1.3.99.3 with kde akonadi</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4327</link>
    <description>&lt;pre&gt;
That makes sense. Looking at the SyncEvolution source, I see that it
already uses application/x-vnd.akonadi.&amp;lt;something&amp;gt; for events and memos,
just not for tasks. That seems like an oversight, so your patch is the
right solution.

I've committed it with you as author. Will be in 1.3.99.4.

&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-04-25T08:08:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4326">
    <title>Re: Syncevolution 1.3.99.3 with kde akonadi</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4326</link>
    <description>&lt;pre&gt;

So after the tiny patch I made todos seem to have synced correctly. I went 
looking through the kdepimlibs source code to see if I could understand why 
they're using the x-vnd mime type. 

Ok I got a reference from #akonadi.

They used the different mime types to "differentiate between events, journals 
and todo entries; there's a different mime type for each and text/calendar is a 
bit vague."

"Externally those are all ot be treated as text/calendar".

Through the freedesktop shared-mime-info system they declared the 
application/x-vnd.akonadi types as subtypes of the standard text/calendar 
type.

And if you want to double check I found their test data at:
http://quickgit.kde.org/?p=kdepimlibs.git&amp;amp;a=tree&amp;amp;h=f4202c8fc8cb0e6c9047119b9ae09d06f431863a&amp;amp;hb=be213b813ecf60179c48fb40d27a6b120ac92821&amp;amp;f=kcalcore%2Ftests%2Fdata

Diane
&lt;/pre&gt;</description>
    <dc:creator>Diane Trout</dc:creator>
    <dc:date>2013-04-25T07:41:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4325">
    <title>Re: sync timeouts for syncevo-http-server + nokia e51 phone</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4325</link>
    <description>&lt;pre&gt;
It seems to work, but I'll remove it again anyway.

One more question, to you and/or Christof: in your experience, how
quickly do phones give up? In other words, what is the recommended value
of &amp;lt;requestmaxtime&amp;gt;?

I'm currently considering to make one minute the default for all HTTP
clients.

&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-04-23T16:17:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4324">
    <title>Re: logging from syncevo-http-server</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4324</link>
    <description>&lt;pre&gt;

  --log-config=LOGCONFIG
                        configure logging via Python logging config file;
                        --debug and --quiet override the log level in the root
                        logger

In other words, the parameter does not take the log file name as value.
It's a bit more complicated (and powerful):
http://docs.python.org/2/howto/logging.html

The option was added because it was easy to implement and then offers
more flexibility than options which implement a subset of the logging
config file features. If it's more confusing than useful then I could
remove it.


If you just want to redirect the output as it is, then I suggest using
normal shell output redirection.

&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-04-22T07:42:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4323">
    <title>Re: Syncevolution 1.3.99.3 with kde akonadi</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4323</link>
    <description>&lt;pre&gt;
Right. I wonder what the difference is, because I fail to see one in the
quoted examples. Handling those extensions while syncing can become
tricky. If they cannot be mapped to iCalendar 2.0, then at least the
Synthesis field list and Synthesis profile for iCalendar 2.0 should
support them, because otherwise the extensions will get lost when
updating an item in Akonadi.

For the iCalendar 2.0 subset, syncing should already work with your
patch. If there are Akonadi resources using "text/calendar" with VTODO,
then a better solution would be to search for both by expanding the
parameter given to the AkonadiSyncSource from a single-value string to a
list.


That won't matter to the Synthesis parser, it treats both alike.


It's a standard attribute, but not currently supported by the Synthesis
configuration used by SyncEvolution.

http://tools.ietf.org/html/rfc5545

&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-04-22T07:30:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4322">
    <title>Re: transport problem: send() on connection which is not ready</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4322</link>
    <description>&lt;pre&gt;Am Sonntag, den 21.04.2013, 21:00 +0200 schrieb Patrick Ohly:
It's the Galaxy S2, also known as GT-I9100, with Android 4.1.2.
My guess would be, that it just allows to create an "account" called
SyncML, but there is no engine behind; or maybe a bad or primitive
implementation - just guessing.
I'll put it into a note about the device in your wiki in some days.
&lt;/pre&gt;</description>
    <dc:creator>Dietmar</dc:creator>
    <dc:date>2013-04-21T19:22:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4321">
    <title>Re: transport problem: send() on connection which is not ready</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4321</link>
    <description>&lt;pre&gt;
Which Samsung device was that? It would be nice to investigate why it
didn't work. OTOH, it might not be worth the effort, because using the
Synthesis app instead is known to work.

&lt;/pre&gt;</description>
    <dc:creator>Patrick Ohly</dc:creator>
    <dc:date>2013-04-21T19:00:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4320">
    <title>Re: transport problem: send() on connection which is not ready</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4320</link>
    <description>&lt;pre&gt;Sorry for having bothered you,
I tried the commercial Synthesis App and it works like a charm. 
So obviously the factory provided SyncML from Samsung does not work, no
issue with syncevolution.
I will write a Compatability wiki these days.

Thanks for this great program, I am free again, no need to use Guhgel's
service.
Dietmar

Am Sonntag, den 21.04.2013, 11:38 +0200 schrieb Dietmar:

_______________________________________________
SyncEvolution mailing list
SyncEvolution&amp;lt; at &amp;gt;syncevolution.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution
&lt;/pre&gt;</description>
    <dc:creator>Dietmar</dc:creator>
    <dc:date>2013-04-21T17:25:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4319">
    <title>logging from syncevo-http-server</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4319</link>
    <description>&lt;pre&gt;Hi

I try to log output from syncevo-http-server with
--log-config=/tmp/syncevo.log but I get errors:

~$ /usr/bin/syncevo-http-server --start-dbus-session
--log-config=/tmp/syncevo.log http://localhost:9000/syncevolution
Traceback (most recent call last):
  File "/usr/bin/syncevo-http-server", line 533, in &amp;lt;module&amp;gt;
    main()
  File "/usr/bin/syncevo-http-server", line 400, in main
    logging.config.fileConfig(options.logConfig)
  File "/usr/lib/python2.7/logging/config.py", line 70, in fileConfig
    formatters = _create_formatters(cp)
  File "/usr/lib/python2.7/logging/config.py", line 106, in _create_formatters
    flist = cp.get("formatters", "keys")
  File "/usr/lib/python2.7/ConfigParser.py", line 607, in get
    raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'formatters'


Without --log-config gives no error, and synchronization works:

~$ /usr/bin/syncevo-http-server --start-dbus-session
http://localhost:9000/syncevolution
[INFO] syncevo-http: new SyncML session for 192.168.178.34
[INFO] sync: /usr/lib/syncevolution/syncevo-dbus-server: ready to run
[INFO] sync: matched deviceID syncevolution-224...

The file /tmp/syncevo.log exists and is worl-readable/writable (mode 666).

I do not have a version number of syncevo-http-server, but I recently
installed it from the package sources (Ubuntu precise, 12.04.2).

Any idea how I get --log-config to work?

Best

Al_

PS: I encountered this while I try to move from manually started
syncevo-http-server [fully functional] to inetd [not working] on a headless
ubuntu server
&lt;/pre&gt;</description>
    <dc:creator>Al_</dc:creator>
    <dc:date>2013-04-21T12:46:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4318">
    <title>transport problem: send() on connection which isnot ready</title>
    <link>http://permalink.gmane.org/gmane.comp.mobile.syncevolution/4318</link>
    <description>&lt;pre&gt;Hi,

I am trying a local sync with syncevo-http-server to an Android 4.1.2
mobile phone to Evolution (Debian Wheezy).
Setup was done according to
https://syncevolution.org/wiki/synchronizing-evolution-http-howto .
Synchronization is started from the mobile phone. I am using the
pre-installed SyncML settings.

This is what syncevo-http-server says (entire protocoll):

against config xxx
inactive
inactive
addressbook: starting first time sync, two-way (peer is client)
complete data backup of source addressbook before sync (enabled with
dumpData and needed for printChanges)
data changes to be applied during synchronization:
addressbook ***
Comparison was impossible.
addressbook: started
addressbook: sent 1/83
addressbook: sent 2/82
addressbook: sent 3/81
addressbook: sent 4/80
addressbook: sent 5/79
addressbook: sent 6/78
addressbook: sent 7/77
addressbook: sent 8/76
addressbook: sent 9/75
addressbook: sent 10/74
addressbook: sent 11/73
transport problem: send() on connection which is not ready
addressbook: first time sync done unsuccessfully
on behalf of user (local, status 20017)
complete data backup after sync (enabled with dumpData and needed for
printChanges)
xxx/.cache/syncevolution/touchy-2013-04-21-11-03/syncevolution-log.html
for details.
+---------------|-----------------------|-----------------------|-CON-+
|
|
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
|
|
|
|
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
|
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
|
|
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
is not ready
addressbook ***
changes
code from SyncEvolution external transport failure (local, status
20043): sync failed

The relevant part in the log file is:


Here is a 5 minutes wait, which corresponds to the timeout of
syncevolution. About at the beginning of this wait the mobile phone
interrups with "Sychnronisationsproblems". 


So for some reasons the mobile phone interrupts the communication.

Can someone please help me to figure out why?
The same occurs with the calendar.

Thanks
        Dietmar

_______________________________________________
SyncEvolution mailing list
SyncEvolution-iSTEHRHt8w9N2k9L2T2VtNi2O/JbrIOy&amp;lt; at &amp;gt;public.gmane.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution
&lt;/pre&gt;</description>
    <dc:creator>Dietmar</dc:creator>
    <dc:date>2013-04-21T09:38:02</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.mobile.syncevolution">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.mobile.syncevolution</link>
  </textinput>
</rdf:RDF>
