Bug 725250
Summary: | zarafa-admin --list-companies generates error | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Erik M Jacobs <ejacobs> |
Component: | zarafa | Assignee: | Robert Scheck <redhat-bugzilla> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | el5 | CC: | ejacobs, redhat-bugzilla, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | zarafa-7.0.1-1.fc15 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-08-28 05:32:03 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
Erik M Jacobs
2011-07-24 17:14:44 UTC
Forwarded to upstream via e-mail. Did not yet receive a reference ID. Upstream reference for now is Ticket#2011072610000202. A Zarafa employee will try to debug this issue together with a developer. This issue seems only to show up in the Fedora build, not in the official builds. I assume at the moment, that the issue exists due to more strict compiler flags at Fedora. We had similar issues in the past already. Feedback from Zarafa was, that we should build using "--enable-release" at %configure to avoid assertion errors at all. Will do so starting with Zarafa 6.40.10 and 7.0.1. zarafa-6.40.10-1.el4 has been submitted as an update for Fedora EPEL 4. https://admin.fedoraproject.org/updates/zarafa-6.40.10-1.el4 zarafa-7.0.1-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.fc16 zarafa-7.0.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.fc15 zarafa-7.0.1-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.fc14 zarafa-7.0.1-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.el6 php53-mapi-7.0.1-1.el5,zarafa-7.0.1-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/php53-mapi-7.0.1-1.el5,zarafa-7.0.1-1.el5 Package zarafa-7.0.1-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing zarafa-7.0.1-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/zarafa-7.0.1-1.fc16 then log in and leave karma (feedback). zarafa-6.40.10-1.el4 has been pushed to the Fedora EPEL 4 stable repository. If problems still persist, please make note of it in this bug report. zarafa-7.0.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. zarafa-7.0.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. php53-mapi-7.0.1-1.el5, zarafa-7.0.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. zarafa-7.0.1-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. zarafa-7.0.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. |