From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <peng.zhang1.cn@windriver.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][master][PATCH] groff: upgrade 1.23.0 -> 1.24.0
Date: Sun, 08 Mar 2026 16:55:27 +0100 [thread overview]
Message-ID: <DGXIUF7BJW61.19RP6EZ3O8H60@bootlin.com> (raw)
In-Reply-To: <20260306092939.1907718-1-peng.zhang1.cn@windriver.com>
On Fri Mar 6, 2026 at 10:29 AM CET, Peng (Paul) (CN) via lists.openembedded.org Zhang wrote:
> From: Zhang Peng <peng.zhang1.cn@windriver.com>
>
> Upgrade to latest revision of 1.24.0.
> - Drop patches included in this release.
> - Add patch to fix test-groff not found in cross-compilation.
> - COPYING, LICENSES: Refresh GPLv3 text.
>
> Release Note:[https://lists.gnu.org/r/groff/2026-02/msg00149.html]
>
> Signed-off-by: Zhang Peng <peng.zhang1.cn@windriver.com>
> ---
Hi,
Thanks for the upgrade.
It looks like the reproducibility is failing on groff:
File "/srv/pokybuild/yocto-worker/reproducible/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/reproducible.py", line 407, in test_reproducible_builds
self.fail('\n'.join(fails))
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/groff-doc_1.24.0-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/groff-doc_1.24.0-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/groff-doc-1.24.0-r0.x86_64_v3.rpm
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/3541
Diffoscope output can be found here:
https://valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20260308-55s2cjsh/packages/diff-html/
At first glance, it seems the issue is the doc pdf which is not stable.
Can you have a look at it?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-08 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 9:29 [OE-core][master][PATCH] groff: upgrade 1.23.0 -> 1.24.0 peng.zhang1.cn
2026-03-08 15:55 ` Mathieu Dubois-Briand [this message]
2026-03-09 14:25 ` Zhang Peng
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=DGXIUF7BJW61.19RP6EZ3O8H60@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peng.zhang1.cn@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