408777 – dev-db/redis-2.4.10 version bump

Bug 408777 - dev-db/redis-2.4.10 version bump

Summary: dev-db/redis-2.4.10 version bump

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	Normal enhancement (vote)
Assignee:	Robin Johnson

URL:
Whiteboard:
Keywords:

Duplicates (1):	411221 (view as bug list)
Depends on:
Blocks:

Reported:	2012-03-18 21:34 UTC by Johan Bergström
Modified:	2012-04-08 04:50 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Johan Bergström 2012-03-18 21:34:32 UTC

What's new in Redis 2.4.9
=========================

UPGRADE URGENCY: low. Mostly new features and minor bug fixing.

* [FEATURE] Redis server is now able to test your memory for broken RAM.
            Usage: ./redis-server --test-memory <megabytes>.
* [FEATURE] redis-benchmark backported from unstable. Pipelining, run selected
            tests, and a few more features.
* [BUGFIX] utils/install_server.sh script now works on Redhat / Centos.
* [BUGFIX] Minor fix to redis-cli (github issue #306).


Rename passes on amd64, x86.

Comment 1 Johan Bergström 2012-04-07 21:11:57 UTC

UPGRADE URGENCY: High for users using replication with a DB identifier higher than 9, or chaining replication so that slaves are attached to other slaves. Low for all the other users.

* [FEATURE] Redis --test-meory improved with new test testing addressing.
* [BUGFIX] Fixed a memory leak: happens when replication is used with DB > 9.
* [BUGFIX] Fixed a replication bug that happens in chained replicaiton when a slave is attached to a master that is later turned into a slave. Now the chained slave reconnection is properly forced.

Comment 2 Robin Johnson archtester

2012-04-08 02:43:46 UTC

InCVS

Comment 3 Robin Johnson archtester

2012-04-08 04:50:17 UTC

*** Bug 411221 has been marked as a duplicate of this bug. ***