Re: [OE-core] [PATCH] ruby: upgrade from 3.4.7 to 4.0.1

[Changqing Li <changqing.li@windriver.com>]

On 2/26/26 21:45, Mathieu Dubois-Briand wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> 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?

Hi, Mathieu

I  cannot reproduce this,  what I compiled locally all don't have "last 
modified".  And I check the logic how the erb.1.gz is generated,

and find a workaround for this.  I will send a V2 here.

Thanks

Changqing

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