From: mkohlhaas <mkohlhaas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] redis: update to 6.2.6.
Date: Fri, 15 Apr 2022 08:48:04 +0200 [thread overview]
Message-ID: <20220415064804.B6kkM-OLupJ51vUsHr97qYsEe87M51yneGg-GSv9mlQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36702@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
There is an updated pull request by mkohlhaas against master on the void-packages repository
https://github.com/mkohlhaas/void-packages redis
https://github.com/void-linux/void-packages/pull/36702
redis: update to 6.2.6.
None
A patch file from https://github.com/void-linux/void-packages/pull/36702.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-redis-36702.patch --]
[-- Type: text/x-diff, Size: 1062 bytes --]
From 1629c7d70ce1f5637bd6b9d083bb46b8c734e001 Mon Sep 17 00:00:00 2001
From: "Hans-J. Schmid" <knock@myopendoor.de>
Date: Fri, 15 Apr 2022 08:41:11 +0200
Subject: [PATCH] redis: update to 6.2.6.
---
srcpkgs/redis/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/redis/template b/srcpkgs/redis/template
index 974305ff1f0f..57e825ccbae9 100644
--- a/srcpkgs/redis/template
+++ b/srcpkgs/redis/template
@@ -1,6 +1,6 @@
# Template file for 'redis'
pkgname=redis
-version=6.0.9
+version=6.2.6
revision=1
makedepends="jemalloc-devel libatomic-devel"
checkdepends="tcl-devel procps-ng"
@@ -10,7 +10,7 @@ license="BSD-3-Clause"
homepage="https://redis.io"
changelog="https://raw.githubusercontent.com/antirez/redis/5.0/00-RELEASENOTES"
distfiles="http://download.redis.io/releases/${pkgname}-${version}.tar.gz"
-checksum=dc2bdcf81c620e9f09cfd12e85d3bc631c897b2db7a55218fd8a65eaa37f86dd
+checksum=5b2b8b7a50111ef395bf1c1d5be11e6e167ac018125055daa8b5c2317ae131ab
system_accounts="redis"
redis_homedir="/var/lib/redis"
next prev parent reply other threads:[~2022-04-15 6:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 6:42 [PR PATCH] " mkohlhaas
2022-04-15 6:48 ` mkohlhaas [this message]
2022-04-15 6:52 ` [PR PATCH] [Updated] " mkohlhaas
2022-04-15 6:53 ` mkohlhaas
2022-04-15 6:56 ` mkohlhaas
2022-04-15 7:25 ` mkohlhaas
2022-04-15 7:27 ` mkohlhaas
2022-04-15 7:29 ` mkohlhaas
2022-04-15 7:32 ` mkohlhaas
2022-04-15 7:34 ` mkohlhaas
2022-04-15 7:37 ` mkohlhaas
2022-04-15 7:39 ` mkohlhaas
2022-04-15 7:41 ` mkohlhaas
2022-04-15 7:55 ` mkohlhaas
2022-04-15 7:56 ` mkohlhaas
2022-04-15 7:57 ` mkohlhaas
2022-04-15 8:00 ` mkohlhaas
2022-04-15 8:04 ` mkohlhaas
2022-04-15 8:10 ` mkohlhaas
2022-04-15 8:10 ` paper42
2022-04-15 8:13 ` [PR PATCH] [Updated] " mkohlhaas
2022-04-15 8:16 ` mkohlhaas
2022-04-15 8:17 ` mkohlhaas
2022-04-15 8:20 ` mkohlhaas
2022-04-15 8:28 ` paper42
2022-04-15 8:29 ` [PR PATCH] [Updated] " mkohlhaas
2022-04-15 8:39 ` mkohlhaas
2022-04-15 8:57 ` mkohlhaas
2022-04-15 9:04 ` mkohlhaas
2022-04-15 9:05 ` mkohlhaas
2022-04-15 9:06 ` mkohlhaas
2022-04-17 21:29 ` [PR PATCH] [Closed]: " mkohlhaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220415064804.B6kkM-OLupJ51vUsHr97qYsEe87M51yneGg-GSv9mlQ@z \
--to=mkohlhaas@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).