From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH for-next] package/htop: bump to 2.1.0
Date: Mon, 12 Feb 2018 20:25:13 +0100 [thread overview]
Message-ID: <20180212192513.4332-1-romain.naour@gmail.com> (raw)
No upstream hash provided with this release [1].
Add licence file hash.
[1] http://www.freelists.org/post/htop/ANN-htop-210
Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
package/htop/htop.hash | 6 +++---
package/htop/htop.mk | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/htop/htop.hash b/package/htop/htop.hash
index cfea23f99b..5419d767a3 100644
--- a/package/htop/htop.hash
+++ b/package/htop/htop.hash
@@ -1,3 +1,3 @@
-# Hashes from: http://www.freelists.org/post/htop/ANN-htop-202
-md5 7d354d904bad591a931ad57e99fea84a htop-2.0.2.tar.gz
-sha1 201f793f13dce2448e36047079875b9bd5bba75a htop-2.0.2.tar.gz
+# Locally calculated
+sha256 3260be990d26e25b6b49fc9d96dbc935ad46e61083c0b7f6df413e513bf80748 htop-2.1.0.tar.gz
+sha256 70466e76443cb5b68144d9fcedca9584e7bfdb6c50859daa5a0290ea27c58aad COPYING
diff --git a/package/htop/htop.mk b/package/htop/htop.mk
index d06e4a56d0..71889557ca 100644
--- a/package/htop/htop.mk
+++ b/package/htop/htop.mk
@@ -4,7 +4,7 @@
#
################################################################################
-HTOP_VERSION = 2.0.2
+HTOP_VERSION = 2.1.0
HTOP_SITE = http://hisham.hm/htop/releases/$(HTOP_VERSION)
HTOP_DEPENDENCIES = ncurses
# Prevent htop build system from searching the host paths
--
2.14.3
next reply other threads:[~2018-02-12 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 19:25 Romain Naour [this message]
2018-02-14 20:44 ` [Buildroot] [PATCH for-next] package/htop: bump to 2.1.0 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=20180212192513.4332-1-romain.naour@gmail.com \
--to=romain.naour@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox