Red Hat Bugzilla – Bug 824323
Please consider updating python-icalendar to 3.0+
Last modified: 2013-06-11 23:37:11 EDT
I would appreciate your consideration on bringing python-icalendar-3.0
to Fedora, as currently an old version (2.1) seems to be the latest
If needed, I'm willing to do the work, but it's probably some other
packages depend on python-icalendar and they may require
updating/rebasing on the changed API in python-icalendar 3.0, and I'm
not sure what help I can be with those packages.
New version needed a few licensing cleanups (see ). Fortunately upstream was quick to resolve this so next release should be better. I am also adding timeline owner to cc, since timeline is the only user of python-icalendar in Fedora. API changes have happened, but they are not that hard to patch.
To simplify testing, I've prepared a scratch build. You can install this on F16/17 as well so should be easy to prepare fix for timeline.
Few things from git repo are still missing in the source tarballs, but that can be solved gradually.
Hi, timeline maintainer here. So this is actually something of a mess.
First, in looking at this I see that somehow both I and the reviewer failed to notice that timeline bundles all it's python deps, so it's not using the system python-icalendar anyway. We have everything it needs in Fedora except pySVG, and I'll get that together and submit a review soon.
Second, python-icalendar 2.1 in Fedora 17 at present doesn't seem to work. Running import icalendar in a python shell fails complaining about timezone even though pytz is installed. Your scratch build of 3.0b2 works.
Given all this, I'd say go ahead and update to 3.0b at least in rawhide and f17, even possibly f16. I'll worry about timeline. Thanks for the heads up.
This makes the svg bits on timeline work.
I've built new icalendar for rawhide/F17 and also put it in the buildroot override for F17. However I was not able to reproduce those import problems on F17 (or F16 for that matter). I am actually using icalendar for one project development and didn't see any issues so far. Anyway, this is moot now.
Jeroen: It might be nice if you could do that package review for Jon to speed up the process :-)
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
python-icalendar-3.4-2.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-icalendar-3.4-2.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
python-icalendar-3.4-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.