This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected Fedora versions. For comments that are specific to the vulnerability please use bugs filed against "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When creating a Bodhi update request, please include this bug ID and the bug IDs of this bug's parent bugs filed against the "Security Response" product (the top-level CVE bugs). Please mention the CVE IDs being fixed in the RPM changelog when available. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=800665 epel-5 tracking bug for mantis: see blocks bug list for full details of the security issue(s). [bug automatically created by: add-tracking-bugs]
I'm merging a bunch of these bugs. If this package is orphaned, maybe we should remove it? There's a lot of flaws in this package...
*** Bug 731855 has been marked as a duplicate of this bug. ***
*** Bug 830742 has been marked as a duplicate of this bug. ***
*** Bug 741403 has been marked as a duplicate of this bug. ***
It appears version 1.2.19 is available. https://www.mantisbt.org/download.php
Can you do this update in EPEL-5, please?
Ok, let's take the lesser devil and do the update
mantis-1.2.19-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/mantis-1.2.19-1.el5
Package mantis-1.2.19-1.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing mantis-1.2.19-1.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-1636/mantis-1.2.19-1.el5 then log in and leave karma (feedback).
mantis-1.2.19-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.