| Summary: | app-pda/libopensync-plugin-google-calendar crashes if you have recurrent calendar entries | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Shawn Bohrer <shawn.bohrer> |
| Component: | Current packages | Assignee: | Ryan Hill (RETIRED) <rhill> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | pda |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 354423 | ||
| Attachments: |
patch to allow recurrent events in Google calendar
New ebuild that applies patch recurrent events patch |
||
Created attachment 124973 [details, diff] patch to allow recurrent events in Google calendar This patch was pulled from upstream: http://www.opensync.org/changeset/1898 Created attachment 124975 [details]
New ebuild that applies patch recurrent events patch
This new ebuild fixes the problem for me.
Thanks for the patch. Sorry it took 3 1/2 years to apply. Fixed. |
If your Google Calendar has recurrent events the libopensync-plugin-google-calendar will crash with an output similar to: Traceback (most recent call last): File "/usr/libexec/google-cal-helper", line 402, in ? sys.exit(main(sys.argv)) File "/usr/libexec/google-cal-helper", line 394, in main return fn(argv) File "/usr/libexec/google-cal-helper", line 286, in oper_get_all data = e.dumpOsync() File "/usr/libexec/google-cal-helper", line 200, in dumpOsync self.addElementContent(doc, event, 'DateStarted', xsdateToOsync(self.dtstart)) File "/usr/libexec/google-cal-helper", line 118, in xsdateToOsync raise DateConversionError("Invalid date/time: %s" % (s)) __main__.DateConversionError: Invalid date/time: Reproducible: Always