From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH v2] libjpeg: Version bump. 2.1.2 -> 2.1.3
Date: Wed, 9 Mar 2022 22:00:08 +0100 [thread overview]
Message-ID: <20220309210008.2862112-1-christian.melki@t2data.com> (raw)
Minor bugfixes.
Update license file hash, calendar year changes.
https://github.com/libjpeg-turbo/libjpeg-turbo/blob/main/ChangeLog.md
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/libjpeg.make | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/rules/libjpeg.make b/rules/libjpeg.make
index 2807d9bc1..06307e635 100644
--- a/rules/libjpeg.make
+++ b/rules/libjpeg.make
@@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBJPEG) += libjpeg
#
# Paths and names
#
-LIBJPEG_VERSION := 2.1.2
-LIBJPEG_MD5 := e181bd78884dd5392a869209bfa41d4a
+LIBJPEG_VERSION := 2.1.3
+LIBJPEG_MD5 := 85244dedeaf06f636a9e7ddea6d236d8
LIBJPEG_SUFFIX := tar.gz
LIBJPEG := libjpeg-turbo-$(LIBJPEG_VERSION)
LIBJPEG_TARBALL := $(LIBJPEG).$(LIBJPEG_SUFFIX)
@@ -26,7 +26,7 @@ LIBJPEG_SOURCE := $(SRCDIR)/$(LIBJPEG_TARBALL)
LIBJPEG_DIR := $(BUILDDIR)/$(LIBJPEG)
LIBJPEG_LICENSE := IJG, BSD-3-Clause, Zlib
LIBJPEG_LICENSE_FILES := \
- file://LICENSE.md;md5=970f17d51650fe54e4f839c6e6121f79 \
+ file://LICENSE.md;md5=a75feaa2de6d8942f50d412241fca1f1 \
file://README.ijg;startline=112;endline=174;md5=9fcb5339d9de46b31309aeef52d7deb1 \
file://simd/nasm/jsimdext.inc;startline=13;endline=28;md5=839b9ed7df5168976efc071bee29a76e
--
2.30.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2022-03-09 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 21:00 Christian Melki [this message]
2022-03-11 9:33 ` Michael Olbrich
2022-03-14 10:14 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20220309210008.2862112-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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