redis-4.0.11-bp151.2.1

- update systemd unit file to fix redis shutdown immedaiate after start

- make sure that disabling/restarting servers works
  https://nordisch.org/posts/hooking-up-instantiated-services-with-rpm/

- make check && true -> make check || true
  This was probably meant to catch an error in the test suite, but
  with && it would only return true if it would return true
  already.

- added systemd unit file file redis-sentinel
  - the unit file uses the same multiple instance mechanism as the
    normal redis unit file
    systemctl start redis-sentinel@default will look for
    /etc/redis/sentinel-default.conf
    and expects a pid file
    /var/run/redis/sentinel-default.pid
    Please make sure your sentinel config sets the pid file.
  - adapted the default sentinel.conf.example to set the pid file
    and the log file similar to the normal redis.conf:
    /var/log/redis/sentinel-<instancename>.log
    /var/run/redis/sentinel-<instancename>.pid
    The unit file checks for the pid file so please adapt your
    local sentinel configs.
    Changed: redis-conf.patch
  - adapt and restructure README.SUSE
  - move the LimitNoFile to the service file itself so the user
    do not have to manually do that step for every instance
  - move the apache integration into its own section
  - add section for redis-sentinel
  - install sentinel example config with group write permissions
    to indicate that the actually config needs to be writable.

- replace some duplicate binaries with symlinks similar to what the
  fedora package does

- Refresh spec-file.
- Update to 4.0.11
  * https://raw.githubusercontent.com/antirez/redis/4.0.11/00-RELEASENOTES
  * The disconnection time between the master and slave was reset
    in an incorrect place, sometimes a good slave will not be able
    to failover because it claims it was disconnected for too much
    time from the master.
  * A replication bug, rare to trigger but non impossible, is in
    Redis for years. It was lately discovered at Redis Labs and
    fixed by Oran Agra. It may cause disconnections,
    desynchronizations and other issues.
  * RANDOMKEY may go in infinite loop on rare situations. Now fixed.
  * EXISTS now works in a more consistent way on slaves.
  * Sentinel: backport of an option to deny a potential security
    problem when the SENTINEL command is used to configure an
    arbitrary script to execute.

- Add reproducible.patch to have fixed hostname and date (boo#1047218)

- update to 4.0.10 (boo#1097430) CVE-2018-11218 CVE-2018-11219
  https://raw.githubusercontent.com/antirez/redis/4.0.10/00-RELEASENOTES
  - Important security issues related to the Lua scripting engine.
    Please check https://github.com/antirez/redis/issues/5017 for
    more information.
  - A bug with SCAN, SSCAN, HSCAN and ZSCAN, that may not return
    all the elements.  We also add a regression test that can
    trigger the issue often when present, and may in theory be able
    to find unrelated regressions.
  - A PSYNC2 bug is fixed: Redis should not expire keys when saving
    RDB files because otherwise it is no longer possible to use
    such RDB file as a base for partial resynchronization. It no
    longer represents the right state.
  - Compatibility of AOF with RDB preamble when the RDB checksum is
    disabled.
  - Sentinel bug that in some cases prevented Sentinel to detect
    that the master was down immediately. A delay was added to the
    detection.
- refreshed patches to apply cleanly again
  redis-conf.patch
  redis-initscript.patch

- Update redis-enable-bactrace-on-x86-and-ia64-only.patch to handle
  arm and rename it to redis-enable-bactrace-on-x86-ia64-and_arm32_only.patch
- Add redis-disable_integration_logging.patch to disable logging test
  when backtrace is not enabled

- Update to 4.0.9
  * https://raw.githubusercontent.com/antirez/redis/4.0.9/00-RELEASENOTES
  * Critical upgrade for users using AOF with the fsync policy set to "always".
  * Latency monitor could report wrong latencies under certain conditions.
  * AOF rewriting could fail when a backgronud rewrite is triggered and
    at the same time the AOF is switched on/off.
  * Redis Cluster crash-recovery safety improved.
  * Redis Cluster has now the ability to configure certain slaves so that
    they'll never attempt a failover.
  * Keyspace notifications API in modules.
  * RM_Call() is now faster by reusing the same client.
  * Tracking of the percentage of keys already logically expired but yet
    not evicted.

- Update to 4.0.8
  * Release notes: https://raw.githubusercontent.com/antirez/redis/4.0.8/00-RELEASENOTES
  * Fix crash Redis Cluster instances during deletions.

- Update to 4.0.7
  * Release notes: https://raw.githubusercontent.com/antirez/redis/4.0.7/00-RELEASENOTES
  * Many 32 bit overflows were addressed in order to allow to use Redis with
    a very significant amount of data, memory size permitting.
  * MEMORY USAGE fixed for the list type.
  * Allow read-only scripts in Redis Cluster.
  * Fix AOF pipes setup in edge case.
  * AUTH option for MIGRATE.
  * HyperLogLogs are no longer converted from sparse to dense in order
    to be merged.
  * Fix AOF rewrite dead loop under edge cases.
  * Fix processing of large bulk strings (>= 2GB).
  * Added RM_UnlinkKey in modules API.
  * Fix Redis Cluster crashes when certain commands with a variable number
    of arguments are called in an improper way.
  * Fix memory leak in lazyfree engine.
  * Fix many potentially successful partial synchronizations that end
    doing a full SYNC, because of a bug destroying the replication
    backlog on the slave. So after a failover the slave was often not able
    to PSYNC with masters, and a full SYNC was triggered. The bug only
    happened after 1 hour of uptime so escaped the unit tests.
  * Improve anti-affinity in master/slave allocation for Redis Cluster
    when the cluster is created.
  * Improve output buffer handling for slaves, by not limiting the amount
    of writes a slave could receive.

- Update to 4.0.6
  * Release notes: https://raw.githubusercontent.com/antirez/redis/4.0.6/00-RELEASENOTES
  * PSYNC2: More errors in the fixes for PSYNC2 (CRITICAL).
  * Quicklist: change the len of quicklist to unsigned long.
  * Quicklist: fix the return value of quicklistCount.
  * Refactoring: improve luaCreateFunction() API.
  * Remove useless variable check from luaCreateFunction().
  * Fix issue #4505, Lua RDB AUX field loading of existing scripts.
  * Regression test for #4505 (Lua AUX field loading).
  * DEBUG change-repl-id implemented.
  * Buffer overflows occurring reading redis.conf CVE-2017-15047 (bsc#1061967)

- Update changelog with CVE reference

- Drop SLE 11 support.
- Refresh spec-file.
- Update to 4.0.2
  * Release notes: https://raw.githubusercontent.com/antirez/redis/4.0.2/00-RELEASENOTES
  * Different replication fixes to PSYNC2, the new 4.0 replication engine.
  * Modules thread safe contexts were introduced. They are an experimental
    API right now, but the API is considered to be stable and usable when needed.
  * SLOWLOG now logs the offending client name and address. Note that this is a
    backward compatibility breakage in case old code assumes that the slowlog
    entry is composed of exactly three entries.
  * The modules native data types RDB format changed.
  * The AOF check utility is now able to deal with RDB preambles.
  * GEORADIUS_RO and GEORADIUSBYMEMBER_RO variants, not supporting the STORE option,
    were added in order to allow read-only scaling of such queries.
  * HSET is now variadic, and HMSET is considered deprecated
    (but will be supported for years to come). Please use HSET in new code.
  * GEORADIUS huge radius (>= ~6000 km) corner cases fixed,
    certain elements near the edges were not returned.
  * DEBUG DIGEST modules API added.
  * HyperLogLog commands no longer crash on certain input (non HLL) strings.
  * Fixed SLAVEOF inside MULTI/EXEC blocks.
  * Many other minor bug fixes and improvements.

- cleanup service file
- add redis.sysctl file
- update README.SUSE
  * add info for socket usage per service
  * add info for limits per service (LimitNOFILE=10240)

- Update to version 3.2.9
  * A few rarely harmful bugs were fixed.
- Changes accumulated from 3.2.8
  Two important bug fixes, the first of one is critical:
  * Apparently Jemalloc 4.4.0 may contain a deadlock under
    particular conditions. See
    https://github.com/antirez/redis/issues/3799.
    We reverted back to the previously used Jemalloc versions and
    plan to upgrade Jemalloc again after having more info about the
    cause of the bug.
  * MIGRATE could crash the server after a socket error. See for
    reference: https://github.com/antirez/redis/issues/3796.

- Update to version 3.2.7
  * This release fixes important security and correctness issues
    (boo#1064980 CVE-2016-10517)

- update to redis 3.2.6
  * fixes for GEORADIUS, BITFIELD and Redis Cluster minor fixes.
- update 3.2.5
  * This release only fixes a compilation issue due to the
    missing -ldl at linking time.

- update to redis 3.2.4, including fixes for security issues:
  * CVE-2016-8339: CONFIG SET client-output-buffer-limit Code
    Execution Vulnerability [boo#1002351]
- bug fixes:
  * TCP binding bug fixed when only certain addresses were available
    for a given port
  * improved crash report
  * Fix for Redis Cluster redis-trib displaying of info after
    creating a new cluster.

- redis 3.2.3:
  * fix replication delay issue
  * drop CVE-2013-7458.patch, upstream

- Test for user/group existence before creating them.
  Request shadow to be present for the scriptlet.

- Fix CVE-2013-7458: unsafe permissions of command line history
  boo#991250, adding CVE-2013-7458.patch

- redis 3.2.2
- Highlight bug fixes:
  * Fix Redis server and Sentinel crashes
  * Fix GEORADIUS errors in reported entries
- New features:
  * slaves support the slave-announce-ip and slave-announce-port
    options.
  * RDB check utlity is now part of Redis and uses the same RDB code
  * redis-check-dump utility is now able to show certain information
    about the RDB file including creating version and date.

- Update to 3.2.1
  * [FIX] Cleaned up spec file.
  * [FIX] Critical bug in Sentinel was hopefully fixed.
  * [FIX] BITFIELD bugs fixed.
  * [FIX] GEO commands fixes on syntax errors and edge cases.
  * [NEW] RESOTRE now accepts dumps generated by older Redis versions.
  * [NEW] Jemalloc now is configured to save you memory, for a problem a
    change in the jemalloc configuration did not really survived when the
    3.2.0 release was finalized.
  * [NEW] TTL and TYPE command no longer alter the last access time of a key, for
    LRU evictions purposes. A new TOUCH command was introduced *just* to
    update the access time of a key.
  * [FIX] A bug was fixed in redis-cli, that connected to the instance running on the
    port 6379 if there was one, regardless of what was specified.
  * [NEW] TCP keep alive is now enabled by default. This should fix most ghost
    connections problems without resulting in any practical change in otherwise
    sane deployments.
  * [FIX] A Sentinel crash that could happen during failovers was fixed.
  * [NEW] avg_ttl reporting in INFO improved.
  * [NEW] Sentinel: improve handling of known Sentinel instances.
  * [NEW] Redis Cluster address update (via gossip section) processing improved
    to avoid initiating inwanted handshakes.
  * [FIX] Critical bug fixed: There was a problem in the way a cluster instance
    loaded the AOF that could cause data written via scripts to be lost during
    reshardings.
  * [NEW] There is a new very powerful BITFIELD command. Check the documentation
    here: http://redis.io/commands/BITFIELD
  * [NEW] CONFIG GET is allowed during the loading of the dataset.
  * [NEW] The DEBUG command have new features and can show an help with DEBUG HELP.
  * [NEW] redis-cli show hits about the commands arguments to the right.
  * [NEW] GEORADIUS got a STORE / STOREDIST option to store the result into a target
    key (as as orted set) instead of reporting it to the user.
  * [NEW] Redis Cluster replicas migration now works in a slightly different way. In
    the past a slave could migrate only to a master that used to have slaves
    in the past (and if there was still trace of this information). Now instead
    if a new slave gets at least a slot, and at least one other master in the
    cluster has a slave, then the new master is considered a valid target for
    replica migration. So if it will be orphaned and there is a spare slave
    it will get one.
  * [NEW] CLUSTER SLOTS output now includes the node ID (in a backward compatible
    manner).

- Fix installation example in README.SUSE

- Update to 3.0.7:
  * [FIX] Many fixes to MIGRATE multiple keys implementation.
  * [FIX] A Redis Cluster node crash was fixed because of wrong handling of
    node->slaveof pointers.
  * [FIX] Fix redis-trib rebalance when nodes need to be left empty because
    the specified weight is zero.
  * [FIX] MIGRATE: Never send -ASK redirections for MIGRATE when there are
  * [FIX] Lua debugger crash when printing too deeply nested objects.
  * [FIX] Redis-cli implementation of Lua debugging now allows to use the
    SCRIPT DEBUG command directly, switching to debugging mode as needed.
  * [FIX] Redis-trib is now able to fix more errors. A new CLUSTER subcommand
    called BUMPEPOCH was introduced in order to support new modes
    for the "fix" subcommand.
  * [NEW] Redis proctected mode: this feature improves Redis security and makes
    harder to run Redis in a configuration that is unsecure because no
    firewalling was used in order to protect Redis from external accesses.
  * [NEW] Cluster/Sentinel tests now use OSX leak to perform leak detection
    at the end of every unit.
  * [NEW] Detect and show server crashes during Cluster/Sentinel tests.
  * [NEW] More reliable Cluster/Sentinel test becuase of timing errors and
  - LOADING errors.
  * [FIX] lua_struct.c/getnum security issue fixed.
  * [FIX] Redis Cluster replica migration fixed.
  * [FIX] Fix a race condition in processCommand() because of interactions
    with freeMemoryIfNeeded().
  * [NEW] Backported from the upcoming Redis 3.2:
    MIGRATE now supports an extended multiple-keys pipelined mode, which
    is an order of magnitude faster. Redis Cluster now uses this mode
    in order to perform reshardings and rebalancings.
  * [NEW] Backported from the upcoming Redis 3.2:
    Redis Cluster has now support for rebalancing via the redis-trib
    rebalance command. Demo here:
  * [NEW] Redis Cluster redis-trib.rb new "info" subcommand.
  * [NEW] Redis Cluster tests improved.
  * [NEW] Log offending memory access address on SIGSEGV/SIGBUS