From: Christopher McCrory <chrismcc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 09/27] package/libv4l: bump to version 1.16.6
Date: Sun, 8 Sep 2019 09:11:18 -0700 [thread overview]
Message-ID: <20190908161118.26263-1-chrismcc@gmail.com> (raw)
Signed-off-by: Christopher McCrory <chrismcc@gmail.com>
---
package/libv4l/libv4l.hash | 5 +++--
package/libv4l/libv4l.mk | 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/package/libv4l/libv4l.hash b/package/libv4l/libv4l.hash
index 99d5021939..78351c97e5 100644
--- a/package/libv4l/libv4l.hash
+++ b/package/libv4l/libv4l.hash
@@ -1,6 +1,7 @@
# Locally calculated after checking signature
-# https://linuxtv.org/downloads/v4l-utils/v4l-utils-1.16.5.tar.bz2.asc
-sha256 ed80242510385017a1dc566e17a285a77222bb301f5bc19386badfcc2c19df1b v4l-utils-1.16.5.tar.bz2
+# https://linuxtv.org/downloads/v4l-utils/v4l-utils-1.16.6.tar.bz2.asc
+# with key 05D0169C26E41593418129DF199A64FADFB500FF
+sha256 f9dac1878e3d5636eab7f56bb209fdfc66b94ee8a2aae54dcb4282fe63a678ae v4l-utils-1.16.6.tar.bz2
# Locally calculated
sha256 391e4da1c54a422a78d83be7bf84b2dfb8bacdd8ad256fa4374e128655584a8a COPYING
sha256 5a7f623a50e384aaf6d2ced068339ddf93d0a50d3a0ecbe86f125b07804ecc78 COPYING.libv4l
diff --git a/package/libv4l/libv4l.mk b/package/libv4l/libv4l.mk
index 22895a9e2c..b31d1a4c41 100644
--- a/package/libv4l/libv4l.mk
+++ b/package/libv4l/libv4l.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LIBV4L_VERSION = 1.16.5
+LIBV4L_VERSION = 1.16.6
LIBV4L_SOURCE = v4l-utils-$(LIBV4L_VERSION).tar.bz2
LIBV4L_SITE = https://linuxtv.org/downloads/v4l-utils
LIBV4L_INSTALL_STAGING = YES
--
2.20.1
next reply other threads:[~2019-09-08 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 16:11 Christopher McCrory [this message]
2019-09-08 23:01 ` [Buildroot] [PATCH 09/27] package/libv4l: bump to version 1.16.6 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=20190908161118.26263-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.