From: Ryan Coe <bluemrp9@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] libite: bump version to 1.9.2
Date: Fri, 3 Nov 2017 06:30:03 -0700 [thread overview]
Message-ID: <20171103133004.8083-2-bluemrp9@gmail.com> (raw)
In-Reply-To: <20171103133004.8083-1-bluemrp9@gmail.com>
Also add hashes for license files.
Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
---
package/libite/libite.hash | 5 ++++-
package/libite/libite.mk | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/package/libite/libite.hash b/package/libite/libite.hash
index 67ad009bf5..ec894c5e00 100644
--- a/package/libite/libite.hash
+++ b/package/libite/libite.hash
@@ -1,2 +1,5 @@
# Locally calculated
-sha256 b27e4af69e9e5b4d00924538d3a41b53752082cc439b9246edec5501aff2f22f libite-v1.8.2.tar.gz
+sha256 18c087123f02cc3cfb612bf53b12dc8a94d4d3ebf015ed5937b1f9203eef72f8 libite-v1.9.2.tar.gz
+sha256 0e97ab27b60e20a7ddb8e9638189ad159124e51d2c12e12735b05423df224da5 LICENSE
+sha256 9e0fb98d251dddf5ba81a355f6b4d89835ec53bc5d7f5fcd2c866b54ec5ccec8 chomp.c
+sha256 a7d29c148e057fae11a87febc3a51970a26433c35a08fc710be689394442d32d pidfile.c
diff --git a/package/libite/libite.mk b/package/libite/libite.mk
index 56b0d5c105..e88060d1dc 100644
--- a/package/libite/libite.mk
+++ b/package/libite/libite.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LIBITE_VERSION = v1.8.2
+LIBITE_VERSION = v1.9.2
LIBITE_SITE = $(call github,troglobit,libite,$(LIBITE_VERSION))
LIBITE_LICENSE = MIT, X11, ISC, BSD-2-Clause
LIBITE_LICENSE_FILES = LICENSE chomp.c pidfile.c
--
2.15.0
next prev parent reply other threads:[~2017-11-03 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 13:30 [Buildroot] [PATCH 1/3] mariadb: bump version to 10.1.28 Ryan Coe
2017-11-03 13:30 ` Ryan Coe [this message]
2017-11-03 13:30 ` [Buildroot] [PATCH 3/3] inadyn: bump version to 2.2.1 Ryan Coe
2017-11-03 20:20 ` [Buildroot] [PATCH 1/3] mariadb: bump version to 10.1.28 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=20171103133004.8083-2-bluemrp9@gmail.com \
--to=bluemrp9@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.