From: Ryan Coe <bluemrp9@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libite: bump version to 2.0.2
Date: Wed, 23 Jan 2019 07:09:10 -0800 [thread overview]
Message-ID: <20190123150911.3321-1-bluemrp9@gmail.com> (raw)
Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
---
package/libite/libite.hash | 2 +-
package/libite/libite.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libite/libite.hash b/package/libite/libite.hash
index 7ef9dca57a..aac01fd36d 100644
--- a/package/libite/libite.hash
+++ b/package/libite/libite.hash
@@ -1,5 +1,5 @@
# Locally calculated
-sha256 39a4c12af30a38a813fac7c8d7512efb3692f910eba9c697a50ce0203e039dad libite-v2.0.1.tar.gz
+sha256 bd5d08066f3e53cc8967beb6f0620286aad7a24d49fb730caa1c6d09a26bb705 libite-v2.0.2.tar.gz
sha256 0e97ab27b60e20a7ddb8e9638189ad159124e51d2c12e12735b05423df224da5 LICENSE
sha256 9e0fb98d251dddf5ba81a355f6b4d89835ec53bc5d7f5fcd2c866b54ec5ccec8 src/chomp.c
sha256 a7d29c148e057fae11a87febc3a51970a26433c35a08fc710be689394442d32d src/pidfile.c
diff --git a/package/libite/libite.mk b/package/libite/libite.mk
index a128953c7a..bcda5f3f0c 100644
--- a/package/libite/libite.mk
+++ b/package/libite/libite.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LIBITE_VERSION = v2.0.1
+LIBITE_VERSION = v2.0.2
LIBITE_SITE = $(call github,troglobit,libite,$(LIBITE_VERSION))
LIBITE_LICENSE = MIT, X11, ISC, BSD-2-Clause
LIBITE_LICENSE_FILES = LICENSE src/chomp.c src/pidfile.c
--
2.20.1
next reply other threads:[~2019-01-23 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 15:09 Ryan Coe [this message]
2019-01-23 15:09 ` [Buildroot] [PATCH 2/2] package/inadyn: bump version to 2.5 Ryan Coe
2019-01-23 21:53 ` Peter Korsgaard
2019-01-23 21:53 ` [Buildroot] [PATCH 1/2] package/libite: bump version to 2.0.2 Peter Korsgaard
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=20190123150911.3321-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox