Hi,

On http://owncloud.org/synchronisation/kde/ there's a description on how to integrate owncloud with
KDE, namely by using the akonadi's "DAV Groupware resource".
I'm running KDE on Debian (Sid/qt-kde.debian.net) which is now a combination of 4.7.4 and 4.8.3,
with more 4.8.x pkgs on the way. As far as I know it is planned to have KDE 4.8.x in Wheezy, but not all of it.
Most notable exception is KMail2, which includes the DAV Groupware resource. This will likely not be part of Wheezy's KDE.
Therefor I don't have the DAV Groupware resource, so I can not sync owncloud with my Kontact.

My goal (hope?) is to make it possible to do just that with KDE/Owncloud in Debian Wheezy.
So my question is:
What is needed to get dav support in akonadi, without having to upgrade the whole kdepim/akonadi
stuff to 4.8, so that dav support is available in the KDE version shipping with Debian Wheezy?

If any information is needed, just ask.

Thanks in advance,
Diederik

Which version of the PIM stack are you currently using?
If it is 4.7.x, it is probably recommended to upgrade to 4.8.x, as improvements in PIM are continuing to be made.

Hi,

bcooksley wrote:Which version of the PIM stack are you currently using?

I'm not sure, but it looks like the version of the PIM stack I have is 4.4.11.
Just in case, I'll list the version numbers of the main components:
Kontact: 4.4.11
KMail: 1.13.7
KAddressBook: 4.4.11
KOrganizer: 4.4.11
Akregator: 1.6.6
KJots: 4.4.11
KNotes: 0.5
If I need to provide more versions numbers, let me know from which components.

bcooksley wrote:If it is 4.7.x, it is probably recommended to upgrade to 4.8.x, as improvements in PIM are continuing to be made.

While your response makes perfect sense, the reason for this post is my expectation that that's exactly what won't happen (wrt PIM) before Wheezy's freeze, which is planned for June (ie this month).
But if it's one or some (supporting) components that need updating to get CalDAV/CardDAV working (with KAddressBook/KOrganizer) that may happen.
I'm trying to find out which (supporting) components those are.

Regards,
Diederik

I am not sure if it is possible to use DAV under Kontact 1.x.

If you are a heavy user of Kontact, you may wish to test the Kontact 2.x setup on another system until you are sure it will work for you.

bcooksley wrote:I am not sure if it is possible to use DAV under Kontact 1.x.

If that's the case, then me and other users of Debian Wheezy's KDE are out of luck.
I'm hoping one of the KDE PIM devs could provide a definitive answer.

bcooksley wrote:If you are a heavy user of Kontact, you may wish to test the Kontact 2.x setup on another system until you are sure it will work for you.

I use Kontact quite heavily, but I'm using the packages provided for Debian by it's Qt-KDE packaging team and because the freeze for Wheezy will happen not too long from now, that means that for the coming 6 months or so, the upgrade to Kontact 2.x won't happen.

While I personally may be able to figure out how to compile from source (which I haven't done before), that will not benefit users of Debian Wheezy.

While it is now unmaintained (and wasn't written by official PIM developers) you might want to take a look at http://code.google.com/p/kcaldav/

Thanks for the suggestion.
I'll keep looking for a solution which can make it into Wheezy though.

Cheers

There have been some interesting developments regarding this topic, so let me summarize it, in case someone else stumbles upon this thread.

On June 24, kdepim-runtime 4.8.4 was uploaded to Debian experimental which enables Akonadi's DAV Groupware resource, ie the connection from Kontact/KAddressbook/KOrganiser to owncloud and vice versa (also other providers, but I was interested in owncloud).
Note that it was only kdepim-runtime, not the whole kdepim suite.
After a week of testing it was decided (just before the freeze) that kdepim-runtime 4.8.4 would not make it into Debian Wheezy.
Although some things worked, there were others that didn't work and it also didn't work stable enough to be included in the next Debian Stable (ie Wheezy).
My expectation that kdepim2/KMail2 would not make it into Wheezy was correct, it will be/stay at version 4.4.11.1.

KMail2/kdepim2 (4.8.4) will be uploaded to experimental or qt-kde.debian.net in the not too distant future.
Little detour for ppl not too familiar with Debian and the various repos:
There's a saying wrt to Sid/Unstable that says: "If it breaks, you get to keep both halves".
In other words: if you don't know what to do when things break (and you should expect that to happen from unstable/experimental), don't use it.

KMail2/kdepim2 will also be made available to wheezy-backports when that opens up, which will be some time after wheezy becomes stable, so it could take a while.
More info in the ML thread started at the link at the top of this page, ie http://lists.debian.org/debian-kde/2012 ... 00084.html