Bug 339327 - StartTime format wrong
Summary: StartTime format wrong
Status: RESOLVED FIXED
Alias: None
Product: kresources
Classification: Miscellaneous
Component: groupdav (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL: http://sourceforge.net/p/davmail/bugs...
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-23 13:31 UTC by Volker Christian
Modified: 2014-10-31 08:10 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.14.2


Attachments
proposed solution (586 bytes, patch)
2014-09-25 19:38 UTC, luisfe
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Volker Christian 2014-09-23 13:31:01 UTC
As of 4.14.1 of the kdepim-runtime package a new "feature" (Only fetch events for the last 3 months) was introduced with the patch f488ed52. In this patch a variable startTime was introduced. The format of this startTime-string is wrong making the akonadi-davgroupware-resource incompatible with MailDav. The startTime-string lakes a "Z" at the end.
Without the "Z" DavMail reports 
    java.text.ParseException: Unparseable date: "20140622T080639" Unparseable date: "20140622T080639"

With the "Z" appended everything works well again!

Reproducible: Always

Steps to Reproduce:
1. Install kdepim-runtime version 4.14.1 
2. Install DavMail
3. Configure an exchange-server in DavMail and a akonadi-davgroupware-resource for the exchange-server
4. Try to sync

Actual Results:  
DavMail reports a java.text.ParseException: Unparseable date: "20140622T080639" Unparseable date: "20140622T080639"

Expected Results:  
DavMail reports no error
Comment 1 luisfe 2014-09-24 09:58:29 UTC
I can confirm this error with debian packages 4.14.1 and davmail
Comment 2 mschnide 2014-09-24 11:56:21 UTC
same effect here: kdepim-runtime 4:4.14.1-1 amd64
Comment 3 luisfe 2014-09-25 19:38:55 UTC
Created attachment 88838 [details]
proposed solution

Volker's solution works for me. I assume that it is a valid solution as long as the date is expected to be in UTC time.
Comment 4 Grégory Oestreicher 2014-09-26 14:55:01 UTC
Stupid error on my part indeed… I'll integrate the patch from #3 for 4.14.2. The date is expected to be in UTC time according to the RFC.

Thanks,
Grégory
Comment 5 Grégory Oestreicher 2014-09-26 14:56:40 UTC
Git commit cb58f624a43b8f63296f5bd1a1becca584624f56 by Grégory Oestreicher.
Committed on 26/09/2014 at 14:55.
Pushed by goestreicher into branch 'KDE/4.14'.

Fix start time to be RFC-compliant

Fix by lftabera-at-yahoo.es

M  +1    -1    resources/dav/protocols/caldavprotocol.cpp

http://commits.kde.org/kdepim-runtime/cb58f624a43b8f63296f5bd1a1becca584624f56
Comment 6 Grégory Oestreicher 2014-09-26 14:58:23 UTC
Adding the Fixed-In field
Comment 7 Samuele Kaplun 2014-10-31 08:10:57 UTC
Hi,
is there a workaround, while waiting for the fixed version to hit mainstream distributions?

Cheers,
    Samuele