http://bugzilla.moblin.org/show_bug.cgi?id=10121





--- Comment #10 from pohly <[email protected]>  2010-04-21 03:07:04 PST ---
(In reply to comment #0)
> syncevolution: 0.9.99.11
> openobex: 1.5-4.1
> 
> Description:
> ====================
> This bug is following bug#9902 . Syncevolution via OBEX between two netbooks
> can pass, triggered on server side. But triggering syncevolution command 
> client
> side will meet error. 
> 
> Steps:
> ====================
> 1. Get two netbook paired.
> 2. On server side, make config1 for client with SyncEvolutionClient template.
> 3. On client side, make config2 for server with SyncEvolution template.
> 4. To avoid slow-sync affect, set preventSlowSync=0 on both sides.
> 5. Trigger on Server, PASS. 'syncevolution --run -s two-way config1
> addressbook'
> 6. Trigger on Client, FAIL. 'syncevolution --run -s two-way config2
> addressbook'
> 
> Expectation:
> ====================
> Syncevolution process should pass, triggered by both client and server sides.
> 
> Root Cause:
> ====================
> Tracked in comments.

This should work for "Netbook <-> Laptop" scenarios where the Netbook is the
SyncML server and initiates the pairing, assuming that the laptop runs some
Linux distro which accepts pairing requests.

I've been told that once such a pairing completes, files can be pushed onto the
Netbook by the Laptop via Bluetooth. So I would expect SyncEvolution as client
on the Laptop to also be able to initiate a connection.

-- 
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to