databases/redis{,-devel,5}: Update to 6.0.15, 6.2.5, 5.0.13

Release Notes: https://groups.google.com/g/redis-db/c/yU-jQ9BhL24/m/e6iZA2GLBgAJ
Security: CVE-2021-32761

PR:		257326
Approved by:	osa (maintainer)
MFH:		2021Q3
Security:	c561ce49-eabc-11eb-9c3f-0800270512f4

databases/redis-devel: security update from 6.2.3 to 6.2.4

Changelog:	https://github.com/redis/redis/compare/6.2.3...6.2.4
PR:		256340
Security:	CVE-2021-32625
Security:	8eb69cd0-c2ec-11eb-b6e7-8c164567ca3c

databases/redis-devel: update to 6.2.3.
PR:	255582

databases/redis-devel: update to the fresh bugfix release 6.2.2.

Changelog:	https://github.com/redis/redis/blob/6.2.2/00-RELEASENOTES
PR:		255247

Update CONFLICTS after databases/redis4 removal.

all: Remove all other $FreeBSD keywords.

Remove # $FreeBSD$ from Makefiles.

Fix build on FreeBSD11.

Update from 6.2.0 to 6.2.1.
Remove added to the upstream patch.

<ChangeLog>

================================================================================
Redis 6.2.1 Released Mon Mar  1 17:51:36 IST 2021
================================================================================

Upgrade urgency: LOW.

Here is a comprehensive list of changes in this release compared to 6.2.0,
each one includes the PR number that added it, so you can get more details
at https://github.com/redis/redis/pull/<number>

Fix build.

cc -std=c11 -pedantic -DREDIS_STATIC='' -Wall -W -Wno-missing-field-initializers
  -O2 -pipe  -fstack-protector-strong -fno-strict-aliasing   -I../deps/hiredis
-I../deps/linenoise -I../deps/lua/src -MMD -o lzf_c.o -c lzf_c.c
zmalloc.c:59:5: error: function-like macro 'sizeof' is not defined
#if PREFIX_SIZE > 0
    ^
zmalloc.c:55:22: note: expanded from macro 'PREFIX_SIZE'
#define PREFIX_SIZE (sizeof(size_t))
                     ^
1 error generated.
gmake[3]: *** [Makefile:339: zmalloc.o] Error 1

Do not bump PORTREVISION because these have no successful
builds.

Reported by:	many

Security update if you use 32bit build of redis (see bellow), MODERATE
if you used earlier versions of Redis 6.2, LOW otherwise.

Integer overflow on 32-bit systems (CVE-2021-21309):
Redis 4.0 or newer uses a configurable limit for the maximum supported bulk
input size. By default, it is 512MB which is a safe value for all platforms.
If the limit is significantly increased, receiving a large request from a client
may trigger several integer overflow scenarios, which would result with buffer
overflow and heap corruption.

ChangeLog:	https://github.com/redis/redis/releases/tag/6.2.0

Update to 6.2rc3.

ChangeLog:	https://github.com/redis/redis/blob/6.2-rc3/00-RELEASENOTES

Update to the recent development version 6.2.0rc2.

Update databases/redis to the recent stable version 6.0.10.
Update CONFLICTS for:
o) databases/redis4
o) databases/redis5
o) databases/redis
o) databases/redis-devel

Connect databases/redis5 to the build.

Bump PORTREVISIONs for dependant ports.

Update from 6.0.8 to 6.0.10.

<ChangeLog>

================================================================================
Redis 6.0.10     Released Tue Jan 12 16:20:20 IST 2021
================================================================================

Upgrade urgency MODERATE: several bugs with moderate impact are fixed,
Here is a comprehensive list of changes in this release compared to 6.0.9.

Command behavior changes:
* SWAPDB invalidates WATCHed keys (#8239)
* SORT command behaves differently when used on a writable replica (#8283)
* EXISTS should not alter LRU (#8016)

Update from 6.0.6 to 6.0.8.
The distribution point has changed on GH from antirez to redis.

<ChangeLog>

================================================================================
Redis 6.0.8     Released Wed Sep 09 23:34:17 IDT 2020
================================================================================

Upgrade urgency HIGH: Anyone who's using Redis 6.0.7 with Sentinel or
CONFIG REWRITE command is affected and should upgrade ASAP, see #7760.

Bug fixes:

* CONFIG REWRITE after setting oom-score-adj-values either via CONFIG SET or

Update from 6.0.5 to 6.0.6.

<ChangeLog>

Upgrade urgency MODERATE: several bugs with moderate impact are fixed here.

The most important issues are listed here:

* Fix crash when enabling CLIENT TRACKING with prefix
* EXEC always fails with EXECABORT and multi-state is cleared
* RESTORE ABSTTL won't store expired keys into the db
* redis-cli better handling of non-pritable key names
* TLS: Ignore client cert when tls-auth-clients off
* Tracking: fix invalidation message on flush
* Notify systemd on Sentinel startup

- Add LICENSE_FILE
- Update WWW

Approved by:	portmgr blanket

Update from 6.0.4 to 6.0.5.

<ChangeLog>

Upgrade urgency MODERATE: several bugs with moderate impact are fixed here.

The most important issues are listed here:

* Fix handling of speical chars in ACL LOAD.
* Make Redis Cluster more robust about operation errors that may lead
  to two clusters to mix together.
* Revert the sendfile() implementation of RDB transfer. It causes some delay.
* Fix TLS certificate loading for chained certificates.
* Fix AOF rewirting of KEEPTTL SET option.
* Fix MULTI/EXEC behavior during -BUSY script errors.

</ChangeLog>

Update from 6.0.3 to 6.0.4.

<ChangeLog>

Upgrade urgency CRITICAL: this release fixes a severe replication bug.
Please visit https://github.com/antirez/redis/blob/6.0/00-RELEASENOTES
for details.

</ChangeLog>

Update from 6.0.2 to 6.0.3.

<ChangeLog>

Upgrade urgency CRITICAL: a crash introduced in 6.0.2 is now fixed.

</ChangeLog>

Update the lua/luajit/luajit-openresty extra patches.

Bump PORTREVISION.

Update from 6.0.1 to 6.0.2.

<ChangeLog>

Upgrade urgency MODERATE: many not critical bugfixes in different areas.
                          Critical fix to client side caching when
                          keys are evicted from the tracking table but
                          no notifications are sent.

The following are the most serious fix:

* XPENDING should not update consumer's seen-time
* optimize memory usage of deferred replies - fixed
* Fix CRC64 initialization outside the Redis server itself.
* stringmatchlen() should not expect null terminated strings.

Update to 6.0.1.

<ChangeLog>

Upgrade urgency HIGH: This release fixes a crash when builiding against
                      Libc malloc.

Here we revert 8110ba888, an optimization that causes a crash due to a
bug in the code. It does not happen with the default allocator because of
differences between Jemalloc and libc malloc, so this escaped all our
testing but was reported by a user. We'll add back the original optimization
that was reverted here later, after checking what happens: it is not a
critical optimization.

</ChangeLog>

Update to the recent commit (aka 6.0 GA).

Update to the recent commit.

Update to the recent commit.

USES=lua gained flavors.

Ports using USES=lua:module or lua:flavors will be flavored.  A range of
supported lua versions can be set using XX-YY (or XX-, or -YY, or simply ZZ)
for ports not supporting all lua versions.

USES=lua sets LUA_FLAVOR that needs to be used on all dependencies of
flavored lua ports, in a similar way as PHP or Python flavors.

PR:		245038
Submitted by:	andrew tao11 riddles org uk
Reviewed by:	mat, kevans, russ haley gmail com
Approved by:	mat (portmgr)
Differential Revision:	https://reviews.freebsd.org/D16494

Update to the recent commit.

Update to the Apr 3, 2020.
Re-generate lua/luajit specific patches.

Update to the recent commit.

Update to the recent commit.

Update to the recent commit.

Update to the recent commit.

Update to the recent commit.

Update to the recent commit.
Reset OPTIMIZATION to respect our CFLAGS.

Update to the recent commit.

Update to the recent commit.
Reduce complexity with the lua-related targets.

Add TLS support.

Convert to use modern OPTIONS way to be less discouraged with
the number of knobs. (*)

Bump PORTREVISION.

Thanks to:	adamw (*)

Update to a recent snapshot.

Update to the recent commit.

Update to the recent commit.

Update to the recent commit.

Also, introduce another dependency records for two
different versions of luajit in the ports tree, cause
otherwise the port has a library dependency issue
because those libraries have the same numbers.

Update to the recent version.

Add two missing patches with r519299.

Update to the recent 7e24e21 commit on Dec 5, 2019.
Port to the openresty flavor of luajit.

databases/redis-devel: fix build on GCC architectures

Require C11 compiler:
cc1: error: unrecognized command line option "-std=c11"

Also remove base GCC workaround.

Update to the recent commit.

Update to the recent commit.
Make portlint(1) more happier by regenerating the patch and move
USES knob up.
Add another patch to respect [C|CXX]FLAGS.

Fix the build by updating the patch.

Update to the recent development version from the unstable branch.

Update from 5.0.6 to 5.0.7.

<ChangeLog>

Upgrade urgency HIGH: many issues fixed, some may have an impact.

Hi all, Redis 5.0.7 fixes a number of bugs, none is very critical, however
there are a few that may have an impact. It's a good idea to upgrade.
There are fixes in the area of replication from modules commands and
callbacks, AOF fsync (non critical issue), memory leaks (very rare and small),
streams beahvior (non critical), and a potential crash in commands
processing multiple keys at the same time that is there for years, and happens
very rarely, but is not impossible to trigger.

</ChangeLog>

Repocopy the databases/redis to the databases/redis4 to update
the databases/redis port to the latest stable version, 5.0.6.

PR:		241526
Reviewed by:	portmgr (adamw)
Approved by:	portmgr (adamw)
Differential Revision:	https://reviews.freebsd.org/D22336

Update from 5.0.5 to 5.0.6.
Regenerate the patches to make portlint(1) happier.

<ChangeLog>

Upgrade urgency CRITICAL: Only in case of exposed instances to untrusted users.

This Redis release, 5.0.6, is a bugfix and enhancement release. The most
important bugfix is a corruption related to the HyperLogLog. A malformed
HyperLogLog string could cause an invalid access to the memory. At a first
glance the vulnerability appears to be not exploitable but just a DoS. The
way to trigger the issue is complex, we'll not provide any information about
how to do that for the users safety.

Other significant changes in this release:

* New modules APIs merged from Redis unstable to Redis 5.
* Some memory optimization related to objects creation.
* Fixes to flushSlaveOutputBuffer() that make sure that SHUTDOWN will
  transfer pending buffers to replicas.

</ChangeLog>

Convert to UCL & cleanup pkg-message (categories d)

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

Prepare for powerpc-on-clang by deleting hard-coded tests for architecture
as a stand-in for "are we running on gcc".

In some cases we only need to specifically test for "are we on the ancient
base gcc", e.g, the usage of 'pragma'.

While here, in some cases turn off SSE functions more specifically based
on ARCH, and turn off -mtune=generic everywhere.  These are part of a
larger work in progress; these commits are for ports that would have
been touched by the the powerpc-on-clang test regardless.

Approved by:	portmgr (tier-2 blanket)

Upgrade from 5.0.4 to 5.0.5.

<ChangeLog>

Upgrade urgency CRITICAL: This release fixes an important AOF fysnc bug
                          and other less critical issues.

Redis 5.0.5 fixes an important issue with AOF and adds multiple very useful
modules APIs. Moreover smaller bugs in other parts of Redis are fixed in
this release.

The AOF bug
-----------

The AOF bug happens when the fsync policy is set to "everysec", which is the

Upgrade from 5.0.3 to 5.0.4.

<ChangeLog>

Upgrade urgency HIGH: This release fixes several Redis stability issues.

Dear Redis users, this release includes a number of fixes for bugs that may
result in Redis crashing in special conditions (not normal usage, but specific
artificial conditions), fixes to certain Redis behaviors especially around
Redis streams, and finally a set of new APIs for Redis Modules.

Specifically:

* Hyperloglog different coding errors leading to potential crashes were fixed.
* A replication bug leading to a potential crash in case of plain misuse of

Upgrade from 5.0.2 to 5.0.3.

<ChangeLog>

Upgrade urgency HIGH: Redis 5 is consolidating, upgrading is a good idea.
                      However there is nothing very critical here, but certain
                      issues resolved could lead to very rare crashes.

Welcome to Redis 5.0.3, several interesting bug fixes here:

* Redis no longer panics when you send data to a replica-mode connection that
  is in MONITOR or SYNC mode.

* Fixes to certain sorted set edge cases. You are unlikely to ever notice those
  issues, but now it is more correct.

Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

Upgrade from 5.0.1 to 5.0.2.

<ChangeLog>

Upgrade urgency: CRITICAL if you use streams and consumer groups.
                 HIGH if you use redis-cli with Redis Cluster.
                 LOW otherwise.

Welcome to Redis 5.0.2.  This release fixes two issues with Streams consumer
groups, where items could be returned duplicated by XREADGROUP when accessing
the history, and another bug where XREADGROUP can report some history even
if the comsumer pending list is empty.  Both problems were addressed and unit
tests to avoid regressions implemented.  Moreover this release fixes some
issue with redis-cli when in cluster mode.  Finally some FreeBSD and DragonFly
build problems are now resolved.

</ChangeLog>

Upgrade from 5.0.0 to 5.0.1.

<ChangeLog>

Upgrade urgency: URGENT if you use Redis Streams. MODERATE otherwise.

Hi all, this is the first patch level release of Redis 5. It contains
both fixes and improvements. Here there is a list of the major ones, however
read the commit messages at the end of the changelog if you want to know
more about the smaller things. Let's start with the new features:

* Sentinel now supports authentication! Check the Sentinel official doc
  for more info.

* Redis-cli cluster "fix" is now able to fix a big number of clusters put

Do not override the environment for make(1) when JEMALLOC knob
is defined.

Bump PORTREVISION.

Fix build on GCC-based architectures.

PR:	231780

Upgrade from 5.0-rc5 to 5.0.0.

<ChangeLog>

Upgrade urgency CRITICAL: Several fixes to streams AOF and replication.

Hi all and welcome to the first stable release of Redis 5! \o/

To start a quick recap of what's new in Redis 5:

1. The new Stream data type. https://redis.io/topics/streams-intro
2. New Redis modules APIs: Timers, Cluster and Dictionary APIs.
3. RDB now store LFU and LRU information.
4. The cluster manager was ported from Ruby (redis-trib.rb) to C code
   inside redis-cli. Check `redis-cli --cluster help` for more info.

Pet portlint.  Found while chasing tier-2 problems.

Approved by:	portmgr (tier-2 blanket)

Upgrade from 5.0-rc4 to 5.0-rc5.

<ChangeLog>

Upgrade urgency HIGH: Several imporant bugs fixed.

This is the release candidate number five, and has a lot of bug fixes inside,
together with a few big changes to the Redis behavior from the point of view
of replication of scripts and handling of the maxmemory directive in slaves.
Make sure to read the whole list!

* BREAKING BEHAVIOR: Slaves now ignore maxmemory by default.
* BREAKING BEHAVIOR: Now scripts are always replicated for their effects, and
                     never sending the script itself to slaves/AOF.
* Improvement: Big pipelining performances improved significantly.
* Fix: Rewrite BRPOPLPUSH as RPOPLPUSH to propagate.
* Fix: False positives in tests.
* Fix: Certain command flags were modified because not correct.
* Fix: Fix blocking XREAD for streams that are empty.
* Improvement: Allow scripts to timeout on slaves as well.
* Fix: Different corner cases due to CLIENT PAUSE are now fixed.
* Improvement: Optimize parsing large bulk greater than 32k.
* Fix: Propagate read-only scripts as SCRIPT LOAD, not as EVAL.

</ChangeLog>

Upgrade from 5.0-rc3 to 5.0-rc4.

<ChangeLog>

Upgrade urgency

HIGH: Many non critical but important issues fixed.
CRITICAL for Stream users: Many important bugs fixed.

Fixes:

* A number of fixes related to Streams: stability and correctnes.
* Fix dbRandomKey() potential infinite loop.
* Improve eviction LFU/LRU when keys are created by INCR commands family.
* Active defragmentation is now working on Redis 5.

Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.

This includes ports
 - featuring USE_GCC=yes or USE_GCC=any,
 - featuring USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and those
 - with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
   c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.

PR:		222542

Upgrade from 5.0-rc1 to 5.0-rc3.
Add experimental support for jemalloc.	(*)

Requested by:	farrokhi (*)

Use USE_GITHUB.

Sponsored by:	Absolight

Upgrade to recent unstable version 5.0-rc1.

Switch to new test framework.

ChangeLog:	https://raw.githubusercontent.com/antirez/redis/5.0/00-RELEASENOTES

For ports in `databases' category: remove redundant PKGMESSAGE assignment,
which is set appropriately by the b.p.m when `pkg-message' appears on the
SUB_FILES list.

Add a workaround for solarisfixes.h header file.
Bump PORTREVISIONs.

Upgrade to recent stable version - 4.0.9.
Update CONFLICTS record.

Upgrade from 4.0.8 to 4.0.9.

Redis version 4.0.9 adds a few interesting new features and fixes a very
critical bug regarding the Append Only File.

ChangeLog:	https://github.com/antirez/redis/blob/4.0/00-RELEASENOTES

Bump PORTREVISIONs of all users of math/mpc that we just updated to
version 1.1.0 (via revision 464079).

Upgrade from 4.0.7 to 4.0.8.

<ChangeLog>

Upgrade urgency CRITICAL ONLY for Redis Cluster users. Otherwise no reason
to upgrade at all.

Redis 4.0.8 fixes a single critical bug in the radix tree data structure
used for Redis Cluster keys slot tracking. The problem was actually fixed
10 months ago into unstable, but it was fixed in a commit related to Streams
so it was never backported (for error) into the 4.0 branch.

The problem will crash Redis Cluster instances during deletions, but it is
very hard to trigger: only when the node removed is in the edge of a memory
mapped area there are the conditions to create an issue, because otherwise
the code just accesses an out of range word in read-only way in an allocated
structure: this is almost always harmless.

</ChangeLog>

Upgrade from 4.0.6 to 4.0.7.

<ChangeLog>

* Many 32 bit overflows were addressed in order to allow to use Redis with
  a very significant amount of data, memory size permitting. (zhaozhao.zz,
  Oran Agra)

* MEMORY USAGE fixed for the list type. (gnuhpc)

* Allow read-only scripts in Redis Cluster. (Salvatore Sanfilippo)

* Fix AOF pipes setup in edge case. (heqin)

* AUTH option for MIGRATE. (AlexStocks, Salvatore Sanfilippo, Fabio Nicotra)

There is no USES=gcc

Pointy hat to:	osa

A customer reported privately it's possible to build the package with
gcc on i386 platform, so it looks like it's a bug with clang 4 on i386.

Do not bump PORTREVISION cause package for i386 never been built.

Reference:	https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216745

Upgrade from 4.0.2 to 4.0.6.

ChangeLog:	https://raw.githubusercontent.com/antirez/redis/4.0/00-RELEASENOTES

Upgrade to 4.0.2.

ChangeLog:	https://raw.githubusercontent.com/antirez/redis/4.0/00-RELEASENOTES

Partially revert r450351 and unbreak

Reported by:	pkg-fallout
With hat:	portmgr

Cleanup after removal of libexecinfo from ports.

PR:		220271
Submitted by:	mat (review), Yasuhiro KIMURA (PR)
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D11488

Remove USES=execinfo.

PR:		220271
Submitted by:	mat (review), Yasuhiro KIMURA (PR)
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D11488

redis-devel fails to build on 11.0 i386 and head i386 too

Reported by:	pkg-fallout

Mark BROKEN on 10/i386.

networking.o: In function `createClient':
networking.c:(.text+0x189): undefined reference to `__atomic_fetch_add_8'
cc: error: linker command failed with exit code 1 (use -v to see invocation)

Sponsored by:	Absolight

Attempt to fix the issue for 10.x, 11.x and head on i386.

networking.o: In function `createClient':
networking.c:(.text+0x189): undefined reference to `__atomic_fetch_add_8'
cc: error: linker command failed with exit code 1 (use -v to see invocation)

Do not bump PORTREVISION since this change affects i386 only what's broken till
now.

Fails to build on 10 i386:

networking.o: In function `createClient':
networking.c:(.text+0x189): undefined reference to `__atomic_fetch_add_8'
cc: error: linker command failed with exit code 1 (use -v to see invocation)

Sponsored by:	Absolight

Upgrade to the latest stable release - 4.0.1.

ChangeLog:	https://raw.githubusercontent.com/antirez/redis/4.0/00-RELEASENOTES

Convert every usage of https://github.com/.../archive/xxx to USE_GITHUB.

While there, fix small style issues.

Sponsored by:	Absolight

Upgrade from 4.0-rc2 to 4.0-rc3.

Upgrade from 4.0-rc1 to 4.0-rc2.

<ChangeLog>

Upgrade urgency LOW: This release mainly fixes a rare GEO API bug and a crash
                     related to the modules subsystem.

Redis 4.0.0-RC2 (version number 3.9.102) just fixes two bugs:

1. GEORADIUS could fail reporting items with very big radius lengths because
   of a bug in the bounding box computation function. This was fixed and tests
   with large radius sizes were added.

2. There was a crash in the modules subsystem that was not merged into RC1 for
   an error, while it was already fixed into the "unstable" branch.

</ChangeLog>

Upgrade from 3.2.5 to 4.0-rc1.

ChangeLog:	https://raw.githubusercontent.com/antirez/redis/4.0/00-RELEASENOTES

Upgrade from 3.2.4 to 3.2.5.

<ChangeLog>

Upgrade urgency LOW: This release only fixes a compilation issue due to the
                     missing -ldl at linking time.

zach shipko in commit 4736407:
 BSDs don't have -ldl
 1 file changed, 15 insertions(+), 5 deletions(-)

antirez in commit 9ada818:
 Fix modules compilation when libc malloc is used.
 1 file changed, 2 insertions(+), 2 deletions(-)

</ChangeLog>

Upgrade from 3.2.3 to 3.2.4.

ChangeLog:	https://raw.githubusercontent.com/antirez/redis/3.2/00-RELEASENOTES

Remove needless code, no functional change.

Upgrade from 3.2.1 to 3.2.3.

ChageLog: https://raw.githubusercontent.com/antirez/redis/3.2/00-RELEASENOTES