[SyncEvolution] N900 - Mozilla Lightning / Sunbird Support via Bluetooth?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, This project looks very interesting, and hopefully what I'm looking for. I was wondering if there is a way to synchronise calendar data primarily, from an N900 over Bluetooth to a Linux desktop running Mozilla Lightning or Sunbird? On my old Nokia phone, an N82, I used OpenSync to achieve this, but even then it strictly only supports Mozilla Sunbird and not Mozilla Lightning, in my experience. Thanks, I'd appreciate the help. Jon Pritchard -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk1l+50ACgkQV/z7jdey4lGuVgCfcGFNOdgik1TpRSrKx+k75qX7 snYAnAjKhLfyynQ91MsvWBLc1d7gLwP8 =yCP/ -END PGP SIGNATURE- ___ SyncEvolution mailing list SyncEvolution@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution
Re: [SyncEvolution] N900 - Mozilla Lightning / Sunbird Support via Bluetooth?
On Thu, 2011-02-24 at 11:04 +0100, Patrick Ohly wrote: Regarding CalDAV, I now (finally) have permission to make SyncEvolution backends for that available. I'm writing a README as we speak and will push the code once that's done. More about that in a separate email. I'm mentioning it in this context because synchronization could be simplified to: - run Darwin Calendar Server - connect Lightning to it - synchronize N900-Calendar Server with SyncEvolution That would be awesome. Thanks, Xav ___ SyncEvolution mailing list SyncEvolution@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution
[SyncEvolution] CalDAV/CardDAV backends available
Hello! I am happy to report that the mysterious new backend that I alluded to earlier is now available as source code: src/backends/webdav in the master branch of SyncEvolution provides access to CalDAV and CardDAV servers. Together with the work on local sync (already discussed on the list and public all the time) this allows synchronizing calendars or address books accessible to SyncEvolution (Evolution, directory with files, ...) with servers like Google or Yahoo. Devices without support for CalDAV/CardDAV can be synchronized with local files (file backend in SyncEvolution) and then these files can be synchronized with a CalDAV or CardDAV server. The CalDAV/CardDAV work was originally done for the Intel MeeGo Tablet UX shown at Mobile World Congress. When used in MeeGo, synchronization is done in a Buteo sync plugin which comes with XML configurations for Yahoo (calendar and addressbook, the latter not enabled) and Google (calendar only). The plugin configures and invokes SyncEvolution. Source is in src/backends/buteo. The goal always was to release as open source, only the exact time was uncertain. What I pushed to the public git repo is the full development history, rebased onto the current master. It is unlikely that the intermediate versions all compile, but the history is worthwhile to have nevertheless. The src/backends/webdav/README (attached) contains setup instructions, debug hints and an overview of the implementation. There are no binaries available yet; compile from source or wait for SyncEvolution 1.1.99.3. Google Calendar works reasonably well, despite quite a few quirks in the server that SyncEvolution has to work around. Yahoo Calendar worked a lot better. On the other hand, Yahoo's CardDAV implementation is barely usable. SyncEvolution has not been tested with anything else yet. There's quite a bit of work left to do: * CardDAVSource does not provide summaries for items (affects --print-items) * support multiple collections * test with additional servers * verify the DNS SRV/.well-known service discovery with a server which supports both * preserve vCard/iCalendar extensions on the servers * get rid of the source-config: would allow using CalDAV/CardDAV as normal sources inside a SyncML session (direct sync with phone or HTTP server) * need some way how synchronization can be configured via the UI * avoid race conditions, either with locking or ETags If anyone wants to help, please let me know and I'll provide further information about what would have to be done. Otherwise I'll tackle these issues as time permits. -- 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. Usage = The webdav backend provides sync sources for CalDAV and CardDAV. They can be selected with backend=CalDAV resp. backend=CardDAV. In contrast to other backends, these sources need additional information about a peer: * syncURL: Specifies URL of calendar or contacts collection. %u gets replaced with the username. A ?SyncEvolution=keyword,keyword,... parameter provides further control. Currently implemented keywords: UpdateHack = work around Google's REV CalDAV quirks ChildHack = avoid storing calendar items which contain VEVENTs with RECURRENCE-ID and no corresponding VEVENT with RRULE; Google Calendar can store such items but reading them fails AlarmHack = when storing a VEVENT without VALARM, store it multiple times, because otherwise Google Calendar adds a default alarm Google = enables all hacks needed for Google Specifying a syncURL is optional. If not given, then DNS SRV lookups based on the domain name in the username are used to find the right host. In theory, .well-known URIs are then used to find the right path on that host, but in practice none of the peers that were tested (Google and Yahoo) seemed to support that. Therefore the code contains a fallback for well-known Yahoo paths when .well-known URIs fail. * username/password: credentials, if available use the email address (needed for auto discovery of CalDAV or CardDAV server) They also use: * loglevel: = 3: basic logging of HTTP traffic = 4: also logging of HTTP body = 5: also SSL and WebDAV lock handling = 6: detailed information about XML parsing = 11: plaintext HTTP authentication The recommended way of using the CalDAV and CardDAV backends is to configure a context with the source-config peer inside it. Such a context then can be used as part of a local sync with other sources. See the Google section below for examples. Multiple calendars/address books This is not yet implemented. The
Re: [SyncEvolution] N900 - Mozilla Lightning / Sunbird Support via Bluetooth?
Patrick Ohly patrick.ohly@... writes: On Do, 2011-02-24 at 09:08 +, Irihapeti wrote: ... Evolution and Lightning have different ways of interpreting repeating events with exceptions, and there may be other quirks as well. ... Can you elaborate on that? Which events are handled differently? It's been a while since I tested this, but I recall that one of the issues was that if I removed one occurrence from a series in Evolution, it - naturally enough - showed as blank in Evolution, but still appeared in Lightning. I can do a bit of testing in the next day or so to give you more detail. Please let me know what you'd need in the way of logs etc. ... I'm mentioning it in this context because synchronization could be simplified to: - run Darwin Calendar Server - connect Lightning to it - synchronize N900-Calendar Server with SyncEvolution Would that mean that it wouldn't be necessary to have Evolution itself installed? I currently have it there mostly as a means for SyncEvolution to do its job. Currently, though, I can't sync tasks with DCS. I very rarely use them anyway, so no problem for me, but might be for others. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution
Re: [SyncEvolution] N900 - Mozilla Lightning / Sunbird Support via Bluetooth?
Jonathan Pritchard jonathanr.pritchard+ml...@googlemail.com writes: I was wondering if there is a way to synchronise calendar data primarily, from an N900 over Bluetooth to a Linux desktop running Mozilla Lightning or Sunbird? I have found I can just point Lightning to my Evolution calendar file and it shows correctly. Evolution ignores appointments added in Lightning, though. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution
Re: [SyncEvolution] N900 - Mozilla Lightning / Sunbird Support via Bluetooth?
Patrick Ohly patrick.ohly@... writes: On Do, 2011-02-24 at 09:08 +, Irihapeti wrote: ... Evolution and Lightning have different ways of interpreting repeating events with exceptions, and there may be other quirks as well. Can you elaborate on that? Which events are handled differently? I got the opportunity today to do some testing. Here are the notes I made. Create appointment with six recurrences in total. Using Evolution. 25 Feb to 1 April. Attempt to remove one occurrence in Evolution. It won't let me. I get an unknown error. Change one occurrence in Evolution. Make it movable does not remove the original fixed event from the series. It creates a single separate event, which initially is a duplicate of one of the occurrences. Create appointment with six recurrences in total. Using Lightning. 12 March to 23 April. Remove one occurrence (9 April) in Lightning. Occurrence has disappeared in Lightning. It's still displaying in Evolution. But if I go into the Edit recurrence dialog, the exception is listed correctly. Change one occurrence (26 March -same day but different time) in Lightning. Displays correctly in Evolution. Displays correctly in Lightning. Change one occurrence (from 19 March to 20 March - same time) in Lightning. Displays correctly in Evolution and Lightning. Evolution vers. 2.28.3 (Lucid) and 2.30.3 (Maverick) behave the same. When synced to E63 phone: 9 April event (removed in Lightning) still displayed. Moved events display correctly. Deleted both series of events from Evolution and synced phone again. First series (created in Evolution and which had no modified events) deleted OK. Second series (created in Lightning) deleted only the modified events and left the unchanged ones on the phone. --- To summarise, Lightning interprets a specific recurrence as deleted where Evolution and E63 don't. You might recall that I had some errors with recurring events created on the E63. For these reasons, I prefer not to use recurring events. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution
[Syncevolution-issues] [MeeGo Projects - Bug 5609] nightly testing: integrate syncevo-dbus-server testing
https://bugs.meego.com/show_bug.cgi?id=5609 --- Comment #27 from pohly patrick.o...@intel.com 2011-02-24 06:35:39 PST --- What's the current status? D-Bus testing currently fails. libsysnthesis-fetch-configFAIL FATAL: Unable to connect to relay host, errno=110 ssh_exchange_identification: Connection closed by remote host fatal: The remote end hung up unexpectedly testSyncStatusSuspendFAIL testSyncStatusAbortFAIL testSyncFAIL testSyncSecondSessionFAIL text: backend 'select backend' not supported - missing/incomplete configuration? testCheckSourceUpdateConfigTempERROR temp: opening calendar: No such calendar - hmm, problem with Evolution? -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching someone on the CC list of the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution-issues
[Syncevolution-issues] [MeeGo Platform - Bug 2148] Overlapping in the fix a sync emergency dialog
https://bugs.meego.com/show_bug.cgi?id=2148 pmccarty patrick.mcca...@linux.intel.com changed: What|Removed |Added Status|NEW |RESOLVED CC||patrick.mccarty@linux.intel ||.com Resolution||DUPLICATE --- Comment #6 from pmccarty patrick.mcca...@linux.intel.com 2011-02-24 14:49:39 PST --- *** This bug has been marked as a duplicate of bug 4836 *** -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution-issues
[Syncevolution-issues] [MeeGo Projects - Bug 4836] Overlapping in the fix a sync emergency dialog
https://bugs.meego.com/show_bug.cgi?id=4836 --- Comment #2 from pmccarty patrick.mcca...@linux.intel.com 2011-02-24 14:49:39 PST --- *** Bug 2148 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching someone on the CC list of the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution-issues
[Syncevolution-issues] [MeeGo Projects - Bug 4836] Overlapping in the fix a sync emergency dialog
https://bugs.meego.com/show_bug.cgi?id=4836 pmccarty patrick.mcca...@linux.intel.com changed: What|Removed |Added CC||tomas.gali...@intel.com --- Comment #3 from pmccarty patrick.mcca...@linux.intel.com 2011-02-24 14:50:05 PST --- *** Bug 7246 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching someone on the CC list of the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution-issues
[Syncevolution-issues] [MeeGo Platform - Bug 2301] Sync: Top Add New Service button is visible, while the bottom one (Add New Device) is not
https://bugs.meego.com/show_bug.cgi?id=2301 pmccarty patrick.mcca...@linux.intel.com changed: What|Removed |Added Status|NEW |RESOLVED CC||patrick.mccarty@linux.intel ||.com Resolution||DUPLICATE --- Comment #8 from pmccarty patrick.mcca...@linux.intel.com 2011-02-24 14:57:25 PST --- *** This bug has been marked as a duplicate of bug 4837 *** -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org http://lists.syncevolution.org/listinfo/syncevolution-issues
