Description of problem:
Current EPEL 6 version of Redis is 2.4.10. Current upstream is two major releases later - 2.8.x.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. look at EPEL
2. look at redis.io
I've successfully built 2.8.14-2 on el6 without issue. Any chance we can update redis on el6?
(In reply to James Laska from comment #1)
> I've successfully built 2.8.14-2 on el6 without issue. Any chance we can
> update redis on el6?
Also installed and running 2.8.14-2 on el6. No major issues so far.
One alternative solution is to use the redis28u or redis30u packages provided by the IUS project . These packages have the following properties.
* conflict with redis from EPEL
* use an alternate name so that the redis package doesn't get an unexpected major version update
* provide the latest upstream supported versions (currently 2.8.24 and 3.0.7)
It seems this package has changed ownership in the meantime.
Flavio, any change you can have a look?
Is there any news?
If anyone needs this, I've produced a COPR with a more
recent version (3.2.10 currently) for el6 and el7 here:
redis-3.2.10-2.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-0ad4c424f0
*** Bug 853029 has been marked as a duplicate of this bug. ***
redis-3.2.10-2.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-0ad4c424f0
redis-3.2.10-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
This is not a trivial update, a lot has changed in redis between these versions... so this breaks existing redis intallations.
I had the problem this weekend on a production server, after update, redis was broken.
Shouldn't EPEL stable be... stable ?
The comments here may help solve the failure you're observing:
And yes, this was unintentional fallout - my apologies there.
Souldn't the update be reverted ? It is very likely that it will break other installations soon.
Maybe revert the package to 2.4.10 and add maybe a redis3 package ?
Maybe. Its a tough call IMO - one problem is this would revert important
security fixes ... :(
This seems to indicate the change should not have happened, therefore a rollback should be the correct way, or am I mistaken ?
> This seems to indicate the change should not have happened
+1; there is no question on that and as I said it was some
unanticipated fallout from the security update. I believe
the damage is, unfortunately, done - the horse has bolted.
> therefore a rollback should be the correct way
That action does not seem to be indicated anywhere in that
document and its not clear that it will help at this stage.
It is also not a desirable outcome for those who want the
security fixes of course, which I'd presume is the silent
majority of users here.