BSD Ports

databases/redis 8.10.1 NetBSD

Persistent key-value database with built-in net interface

System
NetBSD
Repository
pkgsrc
Maintainer
[email protected]
Last update
Commit
34ba8d4cd4
License
server-side-public-license OR gnu-agpl-v3
Categories
databases
Package size
1136.1 KiB, 3770.3 KiB installed

Description

Redis is an advanced key-value store. It is similar to memcached but the dataset is not volatile, and values can be strings, exactly like in memcached, but also lists, sets, and ordered sets. All these data types can be manipulated with atomic operations to push/pop elements, add/remove elements, perform server side union, intersection, and difference between sets, and so forth. Redis also supports different kinds of sorting.

In the other systems

SystemPortVersion
NetBSDdatabases/redis8.10.1
FreeBSDdatabases/redis8.10.2
DragonFlydatabases/redis7.4.3
MidnightBSDdatabases/redis8.10.2

Install

Binary package:

pkgin install redis

From pkgsrc:

cd /usr/pkgsrc/databases/redis && make install clean

Dependencies

Required by 1

Commit history 2

DateCommitCreditsLog message
34ba8d4cd4 jperkin redis: Replace interpreter for scripts/build.sh.
Despite a comment at the top of the script saying it is designed for POSIX sh, it uses the non-portable 'local' keyword.
f324e8c23b adam redis: updated to 8.10.1
Redis 8.10.1 Released Mon 17 Aug 2026 10:00:00 IST Update urgency: `SECURITY`: There are security fixes in the release. Security fixes - (CVE-2026-62356) Miscalculated buffer size in `CMSketch` RDB loading may lead to heap OOB write - Out-of-bounds access in TopK heap cleanup path (MOD-15410) - Use-after-free in the TLS pending-data list when a command closes another pending connection - A malicious RDB payload with an out-of-range `SLOT_INFO` slot id causes memory corruption during RDB loading, which may lead to Remote Code Execution - Vector Sets: missing node level validation when loading a vector set from RDB may lead to out-of-bounds access - Vector Sets: use-after-free when `VREM` mutates the HNSW graph while background `VSIM` threads are still running …