EPEL 6 upgraded redis package to version 3, which broke existing installations
My understanding is, usual practice is to keep version compatible during life of the RHEL6 and new version should have been added as redis3
In what way is it incompatible?
(there was an update to v3, which also involved configuration file changes to close security holes - but v2 and v3 are backward compatible)
oh, forgot to include that information, sorry.
after upgrade service failed to start:
*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 375
>>> 'vm-enabled no'
Bad directive or wrong number of arguments
Thanks Vadym. Yes, interesting - that class of problem definitely needs to be resolved - I'll look into it further & come up with a plan to get it fixed up.
Apologies for the delay. Since we cannot revert the 3.x changes we can resolve this problem by turning the error about that configuration file line (which was deprecated even within the end-of-life'd 2.x series) into a logged warning, and continuing on.
Auditing the 2.x code, there are a handful of vm-related options which could also be in use (all long since removed) - I'll ensure these are handled similarly.
Additional information about the VM configuration options if anyone needs it:
redis-3.2.11-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-92561ef37d
redis-3.2.11-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-92561ef37d
redis-3.2.11-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.