[PATCH] zstd: update 1.5.4 -> 1.5.5

[PATCH] zstd: update 1.5.4 -> 1.5.5

[Michael Callahan]

[-- 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

Re: [poky] [PATCH] zstd: update 1.5.4 -> 1.5.5

[Luca Ceresoli]

Hello Michael,

On Sat, 22 Apr 2023 19:15:52 -0600
"Michael Callahan" <coder.callahan@gmail.com> wrote:

> Update zstd to 1.5.5 for a rare corruption fix.

Thank you for your patch! However there are a couple issues with it:
you should send it to the openembedded-core mailing list and you should
not send patch as attachments but rather inline (using git send-email
is probably your best option).

More info on sending patches here:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

Specifically about your patch, another apparently identical one has
already been sent, and it has been rejected as it generated failures
during autobuilder testing:

https://lists.openembedded.org/g/openembedded-core/topic/98172286#179877

You may want to reply to that e-mail if you have more info on that
build issue.

Best regards,
Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com