gmane.comp.mobile.syncevolution

Re: use syncevolution to sync nokia C5-00 withowncloud

Dustin Demuth — 2013-06-13T12:02:07

thanks patrick!

I'll give it a try, and report on success or failure...

br
dustin

Re: Memotoo <-> SyncEvolution SyncML protocolviolation => 400

Thomas Pequet — 2013-06-13T07:04:48

Daniel can you reproduce this problem each time ?
If Yes, tell me and I will log the synchronization, because your logs it 
is too difficult what is wrong...

Thomas



Le 12/06/2013 19:37, Daniel Betschart a écrit :

_______________________________________________
SyncEvolution mailing list
SyncEvolution< at >syncevolution.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution

Re: use syncevolution to sync nokia C5-00 with owncloud

Patrick Ohly — 2013-06-12T07:33:40

[sorry for the late reply - I was busy and only came back to this when
going through pending items in my inbox]

On Tue, 2013-05-14 at 14:45 +0200, Dustin Demuth wrote:

So you can already do things like

  syncevolution --print-items < at >default addressbook

and access your CardDAV contacts?


The relevant part is under "Finally, here is how the < at >webdav context
needs to be configured so that SyncML clients or servers can be added to
it": one must set databaseUsername/Password and database properties.
This ensures that the source works on its own, without additional
information from the "target-config".

The documentation uses "< at >webdav" as context for the WebDAV sources. It's
okay to use "< at >default", as you indicated above.

The documentation adds a SyncML server to that context. The same works
with a mobile phone via Bluetooth. Just use the same command that you
would normally use to set that up. From
https://syncevolution.org/wiki/sync-your-phone-bluetooth

syncevolution --configure --template ${template} --sy

Re: Memotoo <-> SyncEvolution SyncML protocolviolation => 400

Patrick Ohly — 2013-06-10T20:44:54

Here's the bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=65477


Daniel, may I share your log file with Thomas?

It might be more helpful to reproduce the problem while the log level
includes message dumps. Can you do
  syncevolution --configure loglevel=3 memotoo
and then try syncing until the problem happens again?

Then archive the entire content of the session directory and send it to
Thomas and myself.

Re: Memotoo <-> SyncEvolution SyncML protocolviolation => 400

Thomas Pequet — 2013-06-10T19:52:09

Le 10/06/2013 16:48, Patrick Ohly a écrit :
Hello Patrick !
May be but I have no users that tell me problem with SyncEvolution
Can you send me logs to understand what happen ?

_______________________________________________
SyncEvolution mailing list
SyncEvolution-iSTEHRHt8w9N2k9L2T2VtNi2O/JbrIOy< at >public.gmane.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution

Memotoo <-> SyncEvolution SyncML protocol violation=> 400

Patrick Ohly — 2013-06-10T14:48:19

Hello Thomas!

One of your user reported that the SyncEvolution<->Memotoo combination
started failing for him more often since April. Have you changed
anything in the SyncML implementation of Memotoo?

The Synthesis engine in the client complains about a Sync command which
comes too late:

[2013-06-09 18:38:07.564] 'processCmd' - Processing incoming command,
Cmd=Sync, IncomingMsgID=4, CmdID=2 [--][++] [->end] [->enclosing]

    [2013-06-09 18:38:07.565] Created command 'Status' (outgoing)
    [2013-06-09 18:38:07.565] Processing Sync, Source='note', Target='./memo'
    [2013-06-09 18:38:07.565] Sync command not allowed outside of sync phase (-> 403)
    –
    [2013-06-09 18:38:07.565] 'SessionAbort' - Aborting Session, Status=400, ProblemSource=LOCAL [--][++] [->end] [->enclosing]
    [2013-06-09 18:38:07.565] WARNING: Aborting Session with Reason Status 400 (LOCAL problem) ***

The log that I got didn't include message dumps, but I suspect that the
engine was right - that part hasn't changed for a long ti

how are you?

M R — 2013-06-05T05:36:36

http://www.robertospremulli.com/ufyijxmoy.php/robertospremulli.com/ufyijxmoy.php 









  








_______________________________________________
SyncEvolution mailing list
SyncEvolution-iSTEHRHt8w9N2k9L2T2VtNi2O/JbrIOy< at >public.gmane.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution

Re: google CARDDAV 404

Patrick Ohly — 2013-05-21T10:04:44

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.

Re: sync timeouts for syncevo-http-server + nokia e51 phone

Patrick Ohly — 2013-05-20T19:14:35

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
   explic

Re: sync timeouts for syncevo-http-server + nokiae51 phone

Christof Schulze — 2013-05-20T15:42:46

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

Re: google CARDDAV 404

Juan Antonio Zuloaga Mellino — 2013-05-20T09:24:01

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/<https://google.com/m8/carddav/principals/__uids__/default/lists/default/>
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 <patrick.ohly-ral2JQCrhuEAvxtiuMwx3w< at >public.gmane.org>

_______________________________________________
SyncEvolution mailing list
SyncEvolution-iSTEHRHt8w9N2k9L2T2VtNi2O/JbrIOy< at >public.gmane.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution

Re: baseline distro for SyncEvolution 1.4?

Patrick Ohly — 2013-05-15T06:41:03

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.

use syncevolution to sync nokia C5-00 with owncloud

Dustin Demuth — 2013-05-14T12:45:42

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://syncevo

Re: sync timeouts for syncevo-http-server + nokiae51 phone

Lukas Zeller — 2013-05-13T20:37:42

Hello Patrick,

On 13.05.2013, at 17:55, Patrick Ohly <patrick.ohly-ral2JQCrhuEAvxtiuMwx3w< at >public.gmane.org> 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< at >public.gmane.org - www.plan44.ch

Re: sync timeouts for syncevo-http-server + nokiae51 phone

Lukas Zeller — 2013-05-13T20:30:58

Hello Patrick,

On 23.04.2013, at 18:17, Patrick Ohly <patrick.ohly-ral2JQCrhuEAvxtiuMwx3w< at >public.gmane.org> 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 <requestmaxtime>. However it is possible to set a per-device <requestmaxtime> 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

Re: google CARDDAV 404

Patrick Ohly — 2013-05-08T07:24:03

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.

google CARDDAV 404

Juan Antonio Zuloaga Mellino — 2013-05-08T05:35:51

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=<user>< at >gmail.com \
              password=<password> \
              addressbook/backend=carddav \
              addressbook/database=https://google.com/m8/carddav/principals/__uids__/default/lists/default/
\
              target-config< at >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 whitelistin

baseline distro for SyncEvolution 1.4?

Patrick Ohly — 2013-05-06T09:04:10

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.

Re: Syncevolution 1.3.99.3 with kde akonadi

Patrick Ohly — 2013-04-25T08:08:56

That makes sense. Looking at the SyncEvolution source, I see that it
already uses application/x-vnd.akonadi.<something> 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.

Re: Syncevolution 1.3.99.3 with kde akonadi

Diane Trout — 2013-04-25T07:41:59


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&a=tree&h=f4202c8fc8cb0e6c9047119b9ae09d06f431863a&hb=be213b813ecf60179c48fb40d27a6b120ac92821&f=kcalcore%2Ftests%2Fdata

Diane

Re: sync timeouts for syncevo-http-server + nokia e51 phone

Patrick Ohly — 2013-04-23T16:17:12

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 <requestmaxtime>?

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