Bug 732551
Summary: | Alarm Procedure unreliable and representation in calendar file is inconsistent | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paul DeStefano <prd-fedora> |
Component: | orage | Assignee: | Kevin Fenzi <kevin> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | kevin |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | orage-4.8.2-1.fc15 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-10-02 18:18:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Paul DeStefano
2011-08-22 21:54:19 UTC
Would you be willing to file this upstream? I could do so if you prefer, but you seem to have a very good handle on the issue and could try things from them. Sure, of course. I'll file upstream. This bug was reported and fixed upstream (see v4.8.1.11) https://bugzilla.xfce.org/show_bug.cgi?id=7920 I'm not sure how this will find it's way into the repositories. I would appreciate knowing if this will come to F15 or F16 repositories, if you know. Well, when there's a new orage release we would get it. ;) But I can also look at backporting this fix to the 4.8.1 we have... will see how difficult that will prove to be. Great, thanks! That would be really awesome. Sorry about the extra work; I thought maybe 4.8.1.11 was just bug-fixes and you could just roll it out. But, I don't know what I'm talking about; however the packaging works is fine. It would be cool if there was an update to F15, at least, since (I gather) it was a lib change rolled out with F15 that necessitated in this patch. But, whatever is convenient will be great. The fix exists up-stream, so that's a relief. I looked at backporting this, but it's somewhat messy. I've asked upstream if they are going to be doing a 4.8.2 release soon. That would be more ideal. ;) Sorry, Kevin. Thanks so much for looking into it. Looking forward to the next release, but that is typical. Cheers. orage-4.8.2-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/orage-4.8.2-1.fc16 orage-4.8.2-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/orage-4.8.2-1.fc15 Package orage-4.8.2-1.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing orage-4.8.2-1.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/orage-4.8.2-1.fc15 then log in and leave karma (feedback). Wow! That was fast. Update installed, will report back after testing in a few days. Excellent! Seems to be working perfectly, again. Many thanks. orage-4.8.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. orage-4.8.2-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. |