After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 398725 - vcalendar event recurrence does not import properly
vcalendar event recurrence does not import properly
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks: 317266
 
 
Reported: 2007-01-20 14:42 UTC by Tommi Asiala
Modified: 2012-12-30 15:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Tommi Asiala 2007-01-20 14:42:37 UTC 
Please describe the problem:
The event recurrences don't get imported when importing from a calendar file.




Steps to reproduce:
1. Download for example http://icalx.com/public/nstyka/Birthdays.ics
2. Import it as a single file (preferably to a new calendar)
3. Search for a event in the imported file (you have to go to year 2005)
4. See that event's have no recurrence
5. Export an event to a file and see error in the file

Actual results:
Following error is in the exported event file
X-LIC-ERROR;X-LIC-ERRORTYPE=VCAL-PROP-PARSE-ERROR:Invalid RRULE Frequency: RRULE:FREQ=YEARLY\;INTERVAL=1\;BYMONTH=11

Expected results:


Does this happen every time?
This happens everytime.

Other information:
This happens with calendar files from other sources too. I am not sure if the calendar file completely correct but it does work in sunbird.
Comment 1 André Klapper 2012-09-18 22:55:31 UTC 
Hi,

(In reply to comment #0)
> Steps to reproduce:
> 1. Download for example http://icalx.com/public/nstyka/Birthdays.ics

The requested calendar doesn't exist. 

If this is still an issue in recent versions, please attach a new testcase.
Comment 2 André Klapper 2012-12-30 15:58:17 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!