Your message dated Mon, 28 Apr 2014 07:51:20 +0200 with message-id <[email protected]> and subject line Evolution bug has caused the Debian Bug report #740828, regarding DAViCal expects timestamp in REV field of vCard to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 740828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740828 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: davical Version: 1.1.1-1 Severity: serious I mark this as serious because DAViCal no longer interoperates with Evolution, the default contact/calendar client in Debian Evolution submits a vCard to DAViCal with a REV field like this: REV:"d3b07384d113edec49eaa6238ad5ff00" In the RFCs it suggests it should be a time value and that Evolution may be at fault: http://tools.ietf.org/html/rfc2426#section-3.6.4 https://tools.ietf.org/html/rfc6350#section-6.7.4 DAViCal tries to put it in a timestamp column in PostgreSQL, where it is rejected: Query: QF: SQL error "22007" - ERROR: invalid input syntax for type timestamp with time zone: ....... Query: QF: UPDATE caldav_data SET caldav_data=:dav_data, dav_etag=:etag, logged_user=:session_user, modified=:modified, user_no=:user_no, caldav_type='VCARD' WHERE dav_name=:dav_name If this is a fault in evolution, please confirm and reassign the bug there If clients are behaving like this, however, should DAViCal support them in some way? Related issues: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740827 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699353
--- End Message ---
--- Begin Message ---Confirmed as an upstream bug in Evolution: https://bugzilla.gnome.org/show_bug.cgi?id=704740 I've tested the patch on wheezy and it resolves the issue for me.
--- End Message ---
