Description of problem:
Orage ships a copy of libical an builds against it. We should link it against the libical package.
Ugh. Good spotting. ;(
I guess we should first contact the upstream maintainer and ask what changes he made to his local copy. Upstream is currently not dead (although they have been in the past), so perhaps we can get their changes upstreamed.
The changelog only says:
* Orage is now dependent on local libical.
- standard libical cannot be used due to several fixes
done to Orage's private copy
Adding link to upstream bug report.
(In reply to comment #1)
> The changelog only says:
> * Orage is now dependent on local libical.
> - standard libical cannot be used due to several fixes
> done to Orage's private copy
The private copy of libical is horribly outdated (0.2.4 vs. 0.4.3 in F11). And it's not only libical but also tzdata in the orage tarball.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Just to update this from the upstream report:
The maintainer has 2 outstanding bugs filed with the ical folks, but has workarounds for them, so they have disabled the internal ical by default in favor of a system one when it's new enough. ;)
This will likely land with the 4.8 Xfce, not sure it's possible to backport from git head.
I'll leave this open for now as a reminder.
ok, I have landed orage 18.104.22.168 in rawhide, which uses the system libical. ;)
I'm going to go ahead and close this now.
If we want to keep it open to track getting rid of it in f12/f13/f14/el5/el6, feel free to re-open it.
I intend to push to those releases as testing indicates.
Hi Kevin, I show orage 4.6.1-2 currently in f14. What should be done now?
I don't consider this important enough to justify an update or of orage in F13 or F14. There are massive changes in the UI and this is incompatible with our our stable updates policy (https://fedoraproject.org/wiki/Updates_Policy)
Should we schedule it for f15?
It is already in F15, that's why the bug got closed.
Sorry, I see it now. Will update FES ticket to indicate status...thanks for your help.