From: onli <onli@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] memcached: Update to 1.6.17
Date: Mon, 03 Oct 2022 02:19:42 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39644@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
There is a new pull request by onli against master on the void-packages repository
https://github.com/onli/void-packages memcached_1.6.17
https://github.com/void-linux/void-packages/pull/39644
memcached: Update to 1.6.17
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- armv6l-musl
A patch file from https://github.com/void-linux/void-packages/pull/39644.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-memcached_1.6.17-39644.patch --]
[-- Type: text/x-diff, Size: 1376 bytes --]
From 952a3d411d5f9a96a0bddc425282d8939e8c7a18 Mon Sep 17 00:00:00 2001
From: onli <onli@paskuda.biz>
Date: Mon, 3 Oct 2022 02:09:45 +0200
Subject: [PATCH] memcached: Update to 1.6.17
---
srcpkgs/memcached/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/memcached/template b/srcpkgs/memcached/template
index f9379465cf5e..c9c71926dac7 100644
--- a/srcpkgs/memcached/template
+++ b/srcpkgs/memcached/template
@@ -1,18 +1,18 @@
# Template file for 'memcached'
pkgname=memcached
-version=1.6.10
+version=1.6.17
revision=1
build_style=gnu-configure
configure_args="--enable-seccomp"
-hostmakedepends="autoconf automake"
+hostmakedepends="autoconf automake pkg-config"
makedepends="libevent-devel libseccomp-devel"
short_desc="Distributed memory object caching system"
maintainer="Orphaned <orphan@voidlinux.org>"
license="BSD-3-Clause"
homepage="http://www.memcached.org"
changelog="https://github.com/memcached/memcached/wiki/ReleaseNotes${version//./}"
-distfiles="http://memcached.org/files/${pkgname}-${version}.tar.gz"
-checksum=ef46ac33c55d3a0f1c5ae8eb654677d84669913997db5d0c422c5eaffd694a92
+distfiles="https://memcached.org/files/${pkgname}-${version}.tar.gz"
+checksum=2055e373613d8fc21529aff9f0adce3e23b9ce01ba0478d30e7941d9f2bd1224
# Rebuild configure script, due to patching configure.ac
pre_configure() {
next reply other threads:[~2022-10-03 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 0:19 onli [this message]
2022-10-03 12:51 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39644@inbox.vuxu.org \
--to=onli@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).