From: Christopher McCrory <chrismcc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 03/27] package/gperf: bump to version 3.1
Date: Sun, 8 Sep 2019 09:10:03 -0700 [thread overview]
Message-ID: <20190908161003.25759-1-chrismcc@gmail.com> (raw)
Signed-off-by: Christopher McCrory <chrismcc@gmail.com>
---
package/gperf/gperf.hash | 4 +++-
package/gperf/gperf.mk | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/package/gperf/gperf.hash b/package/gperf/gperf.hash
index 21c76605b5..3d8aafbdca 100644
--- a/package/gperf/gperf.hash
+++ b/package/gperf/gperf.hash
@@ -1,5 +1,7 @@
# Locally calculated after checking pgp signature
-sha256 767112a204407e62dbc3106647cf839ed544f3cf5d0f0523aaa2508623aad63e gperf-3.0.4.tar.gz
+# https://ftp.gnu.org/pub/gnu/gperf/gperf-3.1.tar.gz.sig
+# with key 93C08C88471097CD
+sha256 588546b945bba4b70b6a3a616e80b4ab466e3f33024a352fc2198112cdbb3ae2 gperf-3.1.tar.gz
# Locally calculated
sha256 8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903 COPYING
diff --git a/package/gperf/gperf.mk b/package/gperf/gperf.mk
index 2a6192a48b..4b928a0ebd 100644
--- a/package/gperf/gperf.mk
+++ b/package/gperf/gperf.mk
@@ -4,7 +4,7 @@
#
################################################################################
-GPERF_VERSION = 3.0.4
+GPERF_VERSION = 3.1
GPERF_SITE = $(BR2_GNU_MIRROR)/gperf
GPERF_LICENSE = GPL-3.0+
GPERF_LICENSE_FILES = COPYING
--
2.20.1
next reply other threads:[~2019-09-08 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 16:10 Christopher McCrory [this message]
2019-09-08 17:00 ` [Buildroot] [PATCH 03/27] package/gperf: bump to version 3.1 Thomas Petazzoni
2019-09-08 21:09 ` Ricardo Martincoski
2019-09-08 22:41 ` Thomas Petazzoni
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=20190908161003.25759-1-chrismcc@gmail.com \
--to=chrismcc@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.