http://bugzilla.moblin.org/show_bug.cgi?id=9347
--- Comment #6 from dsolbach <d(a)vidsolbach.de> 2010-02-04 04:19:22 PST ---
Hi there. (once again, hopefully with CRs)
I received an email from one of the horde groupware developers:
SyncEvolution uses a device id (i.e. source URI) with a format that is
already
being used by Funambol clients: sc-pim-1b6ce05d-a34e-4157-aa77-4a19896b5126.
We use the source URIs to determine devices and enable workarounds for all kind
of problems with certain clients. Very old Funambol clients didn't send proper
DevInf data, so we always use Funambol's SIF format if we see a device that we
consider a Funambol client.
We could probably use a smarter detection method, or ignore this one rule
completely because there aren't any of this broken client out in the wild
anymore, but this won't happen before the next major release of Horde.
SyncEvolution should really use their own Source-URI naming scheme though, that
would solve the problem too.
After receiving this comment, I modified the device ID in config.ini (replacing
sc-pim with my-n900) and it worked flawlessly! *jumps in the air*
I used the funambol template when creating the configuration for horde which
works with some minor modifications (one of them beeing the device id) with
horde as well.
Shall I attach my configuration, so we can create a new template for horde
groupware servers?
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.