ValueError: unsupported DTSTART parm: VALUE=DATE-TIME

[potuz]

I am not sure where to report this. It is an issue with python-dateutil module, more than khal, but nonetheless I report here (and radicale) in search for help. When trying to sync a calendar built from khal to radicale I get

Traceback (most recent call last):
File "/usr/lib/python3.4/site-packages/vobject/base.py", line 183, in transformToNati
ve
return self.behavior.transformToNative(self)
File "/usr/lib/python3.4/site-packages/vobject/icalendar.py", line 989, in transformT
oNative
obj.registerTzinfo(obj.tzinfo)
File "/usr/lib/python3.4/site-packages/vobject/icalendar.py", line 150, in gettzinfo
return tz.tzical(buffer).get()
File "/usr/lib/python3.4/site-packages/dateutil/tz/tz.py", line 1109, in init
self._parse_rfc(fobj.read())
File "/usr/lib/python3.4/site-packages/dateutil/tz/tz.py", line 1230, in _parse_rfc
cache=True)
File "/usr/lib/python3.4/site-packages/dateutil/rrule.py", line 1603, in call
return self._parse_rfc(s, **kwargs)
File "/usr/lib/python3.4/site-packages/dateutil/rrule.py", line 1562, in _parse_rfc
raise ValueError("unsupported DTSTART parm: "+parm)
ValueError: unsupported DTSTART parm: VALUE=DATE-TIME

Which is due to rrule.py not wanting any parameter to DTSTART. Can I do something about this, or where should be the correct place to report it?

[geier]

When and where does this error occur? This traceback doesn't really look vdirsyncer or khal related, or is the .ics that khal causing these errors somewhere else?

Could you also link the radicale issue?

[potuz]

On Jun 23, Christian Geier wrote: When and where does this error occur? This traceback doesn't really look vdirsyncer or khal related, or is the .ics that khal causing these errors somewhere else?

This issue happens when trying to sync a local .ics produced with khal, using vdirsyncer to a remote radicale server. The .ics produced with khal has lines of the form: DTSTART;VALUE=DATE-TIME:20171015T010000 and the traceback is raised in the server running radicale. The issue is ultimately caused by the python-dateutil module in rrule.py:1490 def _parse_rfc(self, s, dtstart=None, cache=False, unfold=False, forceset=False, compatible=False, ignoretz=False, tzinfos=None): which seems not to like any parameters for DTSTART. I think the easiest would be to fix there, but I'm only starting to look at that code, and am not used to python.

Could you also link the radicale issue?

Sure, the issue is here: Kozea/Radicale#646

…

— You are receiving this because you authored the thread. Reply to this email directly, [1]view it on GitHub, or [2]mute the thread.* References: [1] #679 (comment) [2] https://github.com/notifications/unsubscribe-auth/APTTdoR43iDTMKgpzioL6BAfC_YQayoAks5sG5ongaJpZM4OC-t4

[geier]

quick note: dateutil is actually on github these days: https://github.com/dateutil/dateutil, I'll look at this later properly.

[potuz]

On Jun 23, Christian Geier wrote: quick note: dateutil is actually on github these days: [1]https://github.com/ dateutil/dateutil, I'll look at this later properly.

The following simple patch to dateutil is working for me on a few tests. It's only ignoring the parameter VALUE=DATE-TIME for DTSTART. Until someone comes up with an actual fix this at least has my calendars working. I'll report on dateutil as well. $ cat /tmp/python-dateutil-fix-dtstart.patch diff --git a/dateutil/rrule.py b/dateutil/rrule.py index da94351..b447600 100644 --- a/dateutil/rrule.py +++ b/dateutil/rrule.py @@ -1559,7 +1559,8 @@ class _rrulestr(object): exdatevals.append(value) elif name == "DTSTART": for parm in parms: - raise ValueError("unsupported DTSTART parm: "+parm) + if parm != "VALUE=DATE-TIME": + raise ValueError("unsupported DTSTART parm: "+parm) if not parser: from dateutil import parser dtstart = parser.parse(value, ignoretz=ignoretz, $

…

— You are receiving this because you authored the thread. Reply to this email directly, [2]view it on GitHub, or [3]mute the thread.* References: [1] https://github.com/dateutil/dateutil [2] #679 (comment) [3] https://github.com/notifications/unsubscribe-auth/APTTdiPOPfAP55y3lMtc7Z7F0MPLYSrvks5sG56XgaJpZM4OC-t4

[geier]

You'll probably want to ignore VALUE=DATE as well.

I'll close this, because I believe our code generates standard compliant .ics files.