From: Michael Callahan <coder.callahan@gmail.com>
To: poky@lists.yoctoproject.org
Subject: [PATCH] zstd: update 1.5.4 -> 1.5.5
Date: Sat, 22 Apr 2023 19:15:52 -0600 [thread overview]
Message-ID: <CADm5WxNHOOJw6N+8bwnsZa50j7A2dPC+dawzR+1QsDHx-yutXA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 48 bytes --]
Update zstd to 1.5.5 for a rare corruption fix.
[-- Attachment #2: 0001-zstd-upgrade-1.5.4-1.5.5.patch --]
[-- Type: text/x-patch, Size: 1319 bytes --]
From c79bfa3f340c0ee7c36433cfc8f8fdbb32cc6ee5 Mon Sep 17 00:00:00 2001
From: Michael Callahan <coder.callahan@gmail.com>
Date: Sat, 22 Apr 2023 17:23:35 -0600
Subject: [PATCH] zstd: upgrade 1.5.4 -> 1.5.5
Fix a rare to trigger corruption bug and some minor improvements.
Changelog:
https://github.com/facebook/zstd/releases/tag/v1.5.5
Signed-off-by: Michael Callahan <coder.callahan@gmail.com>
---
meta/recipes-extended/zstd/{zstd_1.5.4.bb => zstd_1.5.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/zstd/{zstd_1.5.4.bb => zstd_1.5.5.bb} (96%)
diff --git a/meta/recipes-extended/zstd/zstd_1.5.4.bb b/meta/recipes-extended/zstd/zstd_1.5.5.bb
similarity index 96%
rename from meta/recipes-extended/zstd/zstd_1.5.4.bb
rename to meta/recipes-extended/zstd/zstd_1.5.5.bb
index c2e96225e4..487465b6c7 100644
--- a/meta/recipes-extended/zstd/zstd_1.5.4.bb
+++ b/meta/recipes-extended/zstd/zstd_1.5.5.bb
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=0822a32f7acdbe013606746641746ee8 \
SRC_URI = "git://github.com/facebook/zstd.git;branch=release;protocol=https"
-SRCREV = "945f27758c0fd67b636103a38dbf050266c6b90a"
+SRCREV = "63779c798237346c2b245c546c40b72a5a5913fe"
UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)"
CVE_PRODUCT = "zstandard"
--
2.34.1
next reply other threads:[~2023-04-23 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 1:15 Michael Callahan [this message]
2023-04-24 10:38 ` [poky] [PATCH] zstd: update 1.5.4 -> 1.5.5 Luca Ceresoli
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=CADm5WxNHOOJw6N+8bwnsZa50j7A2dPC+dawzR+1QsDHx-yutXA@mail.gmail.com \
--to=coder.callahan@gmail.com \
--cc=poky@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).