Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "wangmy" <wangmy@fujitsu.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] zstd: upgrade 1.5.4 -> 1.5.5
Date: Wed, 12 Apr 2023 09:35:56 +0200	[thread overview]
Message-ID: <20230412093556.56b79b0e@booty> (raw)
In-Reply-To: <1681119440-25219-5-git-send-email-wangmy@fujitsu.com>

Hello,

On Mon, 10 Apr 2023 17:37:20 +0800
"wangmy" <wangmy@fujitsu.com> wrote:

> From: Wang Mingyu <wangmy@fujitsu.com>
> 
> Changelog:
> ==========
> fix: fix rare corruption bug affecting the high compression mode
> perf: improve mid-level compression speed
> lib: deprecated bufferless block-level API
> cli: mmap large dictionaries to save memory
> cli: improve speed of --patch-from mode
> cli: improve i/o speed (+10%) when processing lots of small files
> cli: zstd no longer crashes when requested to write into write-protected directory
> cli: fix decompression into block device using -o, reported
> build: fix zstd CLI compiled with lzma support but not zlib support
> build: fix cmake does no longer require 3.18 as minimum version
> build: fix MSVC+ClangCL linking issue
> build: fix zstd-dll, version of zstd CLI that links to the dynamic library
> build: fix MSVC warnings
> doc: updated zstd specification to clarify corner cases
> doc: document how to create fat binaries for macos
> misc: improve seekable format ingestion speed (+100%) for very small chunk sizes
> misc: tests/fullbench can benchmark multiple files
> 
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>

It appears that this patch is also causing failures in reproducible
builds:

https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2694/steps/13/logs/stdio

Diffoscope:
http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20230411-mdixcwb8/packages/diff-html/

reproducible build succeeded after removing this patch as well as the
squashfs-tools patch.

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


  reply	other threads:[~2023-04-12  7:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  9:37 [OE-core] [PATCH] python3-cryptography-vectors: upgrade 39.0.2 -> 40.0.1 wangmy
2023-04-10  9:37 ` [OE-core] [PATCH] python3-cython: upgrade 0.29.33 -> 0.29.34 wangmy
2023-04-10  9:37 ` [OE-core] [PATCH] python3-hypothesis: upgrade 6.68.2 -> 6.71.0 wangmy
2023-04-10  9:37 ` [OE-core] [PATCH] python3-importlib-metadata: upgrade 6.0.0 -> 6.2.0 wangmy
2023-04-10  9:37 ` [OE-core] [PATCH] zstd: upgrade 1.5.4 -> 1.5.5 wangmy
2023-04-12  7:35   ` Luca Ceresoli [this message]
2023-04-10 16:17 ` [OE-core] [PATCH] python3-cryptography-vectors: upgrade 39.0.2 -> 40.0.1 Tim Orling
2023-04-10 17:25 ` Alexandre Belloni

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=20230412093556.56b79b0e@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wangmy@fujitsu.com \
    /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