Description of problem: The Akismet plugin packaged with WordPress for EPEL is 2.5.6 but 2.5.7 is available. WordPress reports that an update is available but presumably one should not install it over the one in the RPM. Version-Release number of selected component (if applicable): wordpress-3.5-3.el6.noarch How reproducible: Always Steps to Reproduce: 1. Install and run wordpress RPM 2. Log into WordPress as an administrator 3. Actual results: WP reports Akismet update available Expected results: Akismet is current Additional info: Alternatively, I suppose Akismet could be packaged separately as wordpress-plugin-akismet. Not sure why it is included in the base package.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.