This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora EPEL. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. 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]
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1141310,1141314 # Description of your update notes=Security fix for # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi update submission link instead: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1141310,1141314
Since this package got update for Fedora, Can this is also build for epel5 branch?
(In reply to Praveen Kumar from comment #2) > Since this package got update for Fedora, Can this is also build for epel5 > branch? I never did it because epel5 is still on the 1.1 series, but right now I see no more point in trying to backport stuff on a product I mostly stopped hacking on. If I build it, are you able to test the upgrade procedure (involves a schema upgrade) and add karma to the fedora update?
mantis-1.2.17-3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/mantis-1.2.17-3.el5
Package mantis-1.2.17-3.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.17-3.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3784/mantis-1.2.17-3.el5 then log in and leave karma (feedback).
Thank you for building it for epel5, this weekend I will check those build and add karma as required.
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
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.