Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] memcached: update to 1.5.19
Date: Thu, 31 Oct 2019 20:49:13 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16008@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 314 bytes --]

There is a new pull request by ndowens against master on the void-packages repository

https://github.com/ndowens/void-packages memcached
https://github.com/void-linux/void-packages/pull/16008

memcached: update to 1.5.19


A patch file from https://github.com/void-linux/void-packages/pull/16008.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-memcached-16008.patch --]
[-- Type: text/x-diff, Size: 1918 bytes --]

From c7b89d7c2c9074f031994ccfaf082893b3dd0e68 Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens04@gmail.com>
Date: Thu, 31 Oct 2019 14:03:10 -0500
Subject: [PATCH] memcached: update to 1.5.19

---
 srcpkgs/memcached/patches/termios.patch | 12 ------------
 srcpkgs/memcached/template              |  7 ++++---
 2 files changed, 4 insertions(+), 15 deletions(-)
 delete mode 100644 srcpkgs/memcached/patches/termios.patch

diff --git a/srcpkgs/memcached/patches/termios.patch b/srcpkgs/memcached/patches/termios.patch
deleted file mode 100644
index ed45d1975d0..00000000000
--- a/srcpkgs/memcached/patches/termios.patch
+++ /dev/null
@@ -1,12 +0,0 @@
-This fixes build (errors about an incomplete struct) as the
-code uses TCGETS.
---- linux_priv.c	2019-02-10 17:37:43.939089097 +0100
-+++ linux_priv.c	2019-02-10 17:37:31.180435066 +0100
-@@ -3,6 +3,7 @@
- #include <errno.h>
- #include <stdlib.h>
- #include <sys/ioctl.h>
-+#include <termios.h>
- #include "memcached.h"
- 
- // If anything crosses the policy, kill the process.
diff --git a/srcpkgs/memcached/template b/srcpkgs/memcached/template
index 8dfd0095a83..959c8456c1b 100644
--- a/srcpkgs/memcached/template
+++ b/srcpkgs/memcached/template
@@ -1,7 +1,7 @@
 # Template file for 'memcached'
 pkgname=memcached
-version=1.5.16
-revision=2
+version=1.5.19
+revision=1
 build_style=gnu-configure
 configure_args="--enable-seccomp"
 makedepends="libevent-devel libseccomp-devel"
@@ -11,7 +11,8 @@ 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=45a22c890dc1edb27db567fb4c9c25b91bfd578477c08c5fb10dca93cc62cc5a
+checksum=3ddcdaa2d14d215f3111a7448b79c889c57618a26e97ad989581f1880a5a4be0
+nocross="Test can not be run when cross-compiling"
 
 post_install() {
 	vlicense COPYING LICENSE

             reply	other threads:[~2019-10-31 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 19:49 voidlinux-github [this message]
2019-10-31 21:22 ` voidlinux-github
2019-11-01  1:03 ` voidlinux-github
2019-11-01  1:26 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-01  1:26 ` voidlinux-github
2019-11-01 17:51 ` [PR PATCH] [Closed]: " voidlinux-github
  -- strict thread matches above, loose matches on Subject: below --
2019-10-04  9:27 [PR PATCH] " voidlinux-github

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-16008@inbox.vuxu.org \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).