public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <changqing.li@windriver.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] ruby: upgrade from 3.4.7 to 4.0.1
Date: Thu, 26 Feb 2026 14:45:05 +0100	[thread overview]
Message-ID: <DGOXT5NS9NUS.TSZ25ARI9R03@bootlin.com> (raw)
In-Reply-To: <20260224015117.3338374-1-changqing.li@windriver.com>

On Tue Feb 24, 2026 at 2:51 AM CET, Changqing Li via lists.openembedded.org wrote:
> License-Update: Add license BSL-1.0 and Apache-2.0
>
> COPYING - Add Cross-links between Japanese and English pages
> LEGAL - Update LEGAL for JSON vendored sources
>
> Refer:
> [1] https://github.com/ruby/ruby/commit/e652af18816ffe0b85109b8de0827349bf03f16d
> [2] https://github.com/ruby/ruby/commit/d5fbff50c7ff880ae71b8a8ae9aad976c69bea73
>
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---

Hi Changqing,

Thanks for the upgrade.

It looks like we have some reproducibility issue after the upgrade:

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/ruby-doc_4.0.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/ruby-doc_4.0.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/ruby-doc-4.0.1-r0.x86_64_v3.rpm

https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3457

The diffoscope output can be found here:

https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260226-ok6427ba/packages/diff-html/

Based on that, it seems the file output is not stable, as it sometimes
add "last·modified: xxx" to the file type.

Can you have a look at the possibilities to make the build reproducible
again?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-02-26 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24  1:51 [PATCH] ruby: upgrade from 3.4.7 to 4.0.1 Changqing Li
2026-02-26 13:45 ` Mathieu Dubois-Briand [this message]
2026-02-27 10:01   ` [OE-core] " Changqing Li
2026-02-27 10:07   ` [PATCH V2] " Changqing Li
2026-02-27 13:39     ` [OE-core] " Mathieu Dubois-Briand
2026-02-28  2:37       ` Changqing Li
2026-03-02 15:07 ` [OE-core] [PATCH] " Richard Purdie
2026-03-03  5:16   ` Changqing Li

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=DGOXT5NS9NUS.TSZ25ARI9R03@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=changqing.li@windriver.com \
    --cc=openembedded-core@lists.openembedded.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