Description of problem: KDE's akonadi CalDAV resource cannot find any calendars in a Zarafa server, apparently because the Zarafa CalDAV gateway does not properly handle the Depth header supplied by the resource. I originally reported this to KDE bugzilla here: https://bugs.kde.org/show_bug.cgi?id=283252 They say it's a Zarafa bug. Version-Release number of selected component (if applicable): zarafa-ical-7.0.1-1.fc14.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a calendar for a user in Zarafa and verify that you can fetch it as a .ical file with a web browser. 2. In Korganizer in KDE 4.7.2, do Settings-> Configure Korganizer-> General ->Calendars and create a new DAV groupware resource pointing to your Zarafa CalDAV gateway Actual results: No calendar found Expected results: A calendar, matching the one which can be imported as a file Additional info: Speculation: possible off-by-one error in use of value in Depth header? Possible disagreement about whether it's zero or 1 based? Will also affect F15 since Zarafa server version is the same.
This is upstream Ticket#2011102310000103 for now.
Zarafa 7.0.2 just popped out of the hat. This is fixed in 7.0.2
Are you *really* sure that 7.0.2 is solving this issue? From what I got told by upstream meanwhile is, that they need to rewrite the depth code, see https://jira.zarafa.com/browse/ZCP-8763 for further tracking.
OK, well, being more restrained in my assertions, I had zarafa 7.0.1 RPMs on the server. Shortly after I filed this I checked updates and got zarafa-utils-7.0.2-1.fc14.x86_64 zarafa-common-7.0.2-1.fc14.noarch zarafa-server-7.0.2-1.fc14.x86_64 zarafa-gateway-7.0.2-1.fc14.x86_64 zarafa-dagent-7.0.2-1.fc14.x86_64 zarafa-ical-7.0.2-1.fc14.x86_64 zarafa-webaccess-7.0.2-1.fc14.noarch zarafa-monitor-7.0.2-1.fc14.x86_64 zarafa-7.0.2-1.fc14.x86_64 zarafa-client-7.0.2-1.fc14.x86_64 zarafa-spooler-7.0.2-1.fc14.x86_64 Before the update, KDE's CalDAV resource could not find anything in Zarafa. After the update, it works. Being entirely honest, I did not re-capture the traces I reported to the KDE bugzilla, but simply enjoyed the fact that it now works for me. It may have gone from "not right" to "not right in a way that happens not to affect KDE's CalDAV resource".
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
zarafa-7.1.5-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/zarafa-7.1.5-1.fc19
zarafa-7.1.5-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/zarafa-7.1.5-1.fc18
zarafa-7.1.5-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
zarafa-7.1.5-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.