From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <sundeep.kokkonda@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: <Randy.MacLeod@windriver.com>
Subject: Re: [OE-core] [PATCH] rust: Upgrade 1.96.0 -> 1.96.1
Date: Sat, 18 Jul 2026 06:58:17 +0200 [thread overview]
Message-ID: <DK1FJ604RQLX.1IRYGTCQNJZOK@bootlin.com> (raw)
In-Reply-To: <20260705152012.3160479-1-sundeep.kokkonda@windriver.com>
On Sun Jul 5, 2026 at 5:20 PM CEST, Sundeep KOKKONDA via lists.openembedded.org wrote:
> From: Sundeep KOKKONDA <sundeep.kokkonda@windriver.com>
>
> https://blog.rust-lang.org/2026/06/30/Rust-1.96.1/
>
> Rust 1.96.1 fixes:
> - Missing retries / timeouts in Cargo's HTTP client
> - Miscompilation in a MIR optimization
> - Cargo CVEs:: CVE-2025-15661, CVE-2026-55199, CVE-2026-55200
>
> Test results:
> No changes
>
> Assisted-by: Kiro
> Signed-off-by: Sundeep KOKKONDA <sundeep.kokkonda@windriver.com>
> ---
Hi Sundeep,
This was a bit expected, we still have the reproducibility issue:
AssertionError: The following deb packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/rust-dbg_1.97.1-r0_amd64.deb
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/deb/./x86-64-v3/rust_1.97.1-r0_amd64.deb
The following ipk packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/ipk/./x86-64-v3/rust-dbg_1.97.1-r0_x86-64-v3.ipk
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/ipk/./x86-64-v3/rust_1.97.1-r0_x86-64-v3.ipk
The following rpm packages are different and not in exclusion list:
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/rpm/./x86_64_v3/rust-1.97.1-r0.x86_64_v3.rpm
/srv/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB-extended/tmp/deploy/rpm/./x86_64_v3/rust-dbg-1.97.1-r0.x86_64_v3.rpm
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/4417
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260717-4vji97l6/packages/diff-html/
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-07-18 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 15:20 [PATCH] rust: Upgrade 1.96.0 -> 1.96.1 sundeep.kokkonda
2026-07-18 4:58 ` Mathieu Dubois-Briand [this message]
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=DK1FJ604RQLX.1IRYGTCQNJZOK@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=Randy.MacLeod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sundeep.kokkonda@windriver.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