linux/meta-openembedded.git/meta-oe/recipes-extended/redis, branch mickledore

redis: upgrade 7.0.12 -> 7.0.13

2023-10-15T23:09:42+00:00

Refer [1], include an urgency SECURITY fix and some bug fixes [1] https://github.com/redis/redis/releases/tag/7.0.13 Signed-off-by: Changqing Li Signed-off-by: Armin Kuster

redis: upgrade 7.0.11 -> 7.0.12

2023-08-10T14:19:26+00:00

Refer: https://github.com/redis/redis/releases/tag/7.0.12 Signed-off-by: Changqing Li Signed-off-by: Armin Kuster

redis: upgrade 6.2.12 -> 6.2.13

2023-08-10T14:19:23+00:00

Refer: https://github.com/redis/redis/releases/tag/6.2.13 Signed-off-by: Changqing Li Signed-off-by: Armin Kuster

redis: use the files path correctly

2023-06-15T12:10:11+00:00

Recipes are not expected to set FILESPATH directly, they are expected to use FILESEXTRAPATH. I can see the seting of FILESPATH in this recipe only wants to find redis-7 specific patches and files. This could be easily achieved by using redis-7.0.11/ directory to hold all those files. Using FILESPATH in this way removes the possibility of overriding some files (e.g., the redis service file) from other layers via FILESEXTRAPATH:prepend, which is kind of a common practice and is actually working for basically all other recipes. This is because we have: meta/classes-global/base.bbclass:FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}", "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}" And FILESEXTRAPATH is handled in base_set_filespath. Signed-off-by: Chen Qi Signed-off-by: Armin Kuster

redis: upgrade 6.2.11 -> 6.2.12

2023-05-16T11:32:31+00:00

Signed-off-by: Changqing Li Signed-off-by: Armin Kuster

redis: upgrade 7.0.10 -> 7.0.11

2023-05-07T16:19:28+00:00

Signed-off-by: Wang Mingyu Signed-off-by: Khem Raj (cherry picked from commit 34153d91b47765eedb3f0010ec7bc367a00c82d6) Signed-off-by: Armin Kuster

redis: upgrade 7.0.9 -> 7.0.10

2023-03-22T16:12:40+00:00

Upgrade urgency: SECURITY, contains fixes to security issues. Security Fixes: * (CVE-2023-28425) Specially crafted MSETNX command can lead to assertion and denial-of-service Bug Fixes ========= * Large blocks of replica client output buffer may lead to psync loops and unnecessary memory usage (#11666) * Fix CLIENT REPLY OFF|SKIP to not silence push notifications (#11875) * Trim excessive memory usage in stream nodes when exceeding `stream-node-max-bytes` (#11885) * Fix module RM_Call commands failing with OOM when maxmemory is changed to zero (#11319) Signed-off-by: Changqing Li Signed-off-by: Khem Raj

redis: fix service redis-server restart not working under sysvinit

2023-03-18T16:36:49+00:00

Under sysvinit when trying to restart redis-server using service redis-server restart two calls are made to start-stop-daemon, first with the --stop argument and then with --start argument consecutively. Because the process doesn't immediately terminate when start-stop-daemon --stop is called, the next call to start-stop-daemon --start finds the process still running and does not attempt to start another one. This leads to only a stop of the redis-server process when a restart is requested. This behavior affects all redis versions using sysvinit only. This can be fixed by using the --retry argument with start-stop-daemon --stop in order for the call to block until the process terminates so that start-stop-daemon --start will attempt to start a new process. Unfortunately the --retry argument works only in the implementation of start-stop-daemon provided by dpkg package and is ignored in the implementation provided by busybox package. A repeated check if the process is still running and another try with another signal after a timeout will effectively simulate a stop with --retry=TERM/5/KILL/5 schedule. Signed-off-by: Stefan Ghinea Signed-off-by: Khem Raj

redis: Upgrade 7.x to 7.0.9

2023-03-06T05:49:25+00:00

Signed-off-by: Khem Raj

redis: Upgrade 6.x recipe to 6.2.11

2023-03-06T05:49:25+00:00

Signed-off-by: Khem Raj