From: "Marko, Peter" <Peter.Marko@siemens.com>
To: Yoann Congal <yoann.congal@smile.fr>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core][scarthgap][PATCH] gnupg: upgrade 2.4.8 -> 2.4.9
Date: Wed, 18 Feb 2026 21:28:25 +0000 [thread overview]
Message-ID: <AS1PR10MB5697F71F42D54E6DF1DBDA63FD6AA@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DG63GSU9MVS3.304EAXA47JAF9@smile.fr>
> -----Original Message-----
> From: Yoann Congal <yoann.congal@smile.fr>
> Sent: Wednesday, February 4, 2026 11:10
> To: Marko, Peter (FT D EU SK BFS1) <Peter.Marko@siemens.com>;
> openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][scarthgap][PATCH] gnupg: upgrade 2.4.8 -> 2.4.9
>
> On Sat Jan 10, 2026 at 11:44 PM CET, Peter Marko via lists.openembedded.org
> wrote:
> > From: Peter Marko <peter.marko@siemens.com>
> >
> > Handles CVE-2025-68973.
> >
> > Refresh patches.
> >
> > Signed-off-by: Peter Marko <peter.marko@siemens.com>
> > ---
> > meta/recipes-support/gnupg/gnupg/relocate.patch | 14 +++++++-------
> > .../gnupg/{gnupg_2.4.8.bb => gnupg_2.4.9.bb} | 2 +-
> > 2 files changed, 8 insertions(+), 8 deletions(-)
> > rename meta/recipes-support/gnupg/{gnupg_2.4.8.bb => gnupg_2.4.9.bb}
> (97%)
>
> Hello,
>
> I've tested that on autobuilder but got an error in oe-selftest-debian:
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/35/builds/3138
> ERROR: autoconf-native-2.72e-r0 do_recipe_qa: GPG exited with code 2: gpg:
> signing failed: Corrupted protection
> gpg: signing failed: Corrupted protection
> ERROR: patch-native-2.7.6-r0 do_recipe_qa: GPG exited with code 2: gpg:
> signing failed: Corrupted protection
> gpg: signing failed: Corrupted protection
>
> I've started a build with this gnupg upgrade reverted to confirm that
> this is indeed the cause:
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/35/builds/3142
>
> Can you look at this?
> Thanks!
Unfortunately, I'm not able to reproduce this failure.
On my Debian 11 I have:
SANITY_TESTED_DISTROS = ""
PACKAGE_CLASSES = "package_rpm"
RPM_GPG_SIGN_CHUNK = "1"
IMAGE_CLASSES += 'testimage'
And run:
oe-selftest -r signing -j 16
And get:
oe-selftest - INFO - RESULTS - signing.LockedSignatures.test_locked_signatures: PASSED (122.35s)
oe-selftest - INFO - RESULTS - signing.Signing.test_signing_packages: PASSED (155.34s)
oe-selftest - INFO - RESULTS - signing.Signing.test_signing_sstate_archive: PASSED (121.11s)
oe-selftest - INFO - oe-selftest - OK - All required tests passed (successes=3, skipped=0, failures=0, errors=0)
So I guess I just backport the CVE fix instead of this upgrade.
Peter
>
> Regards,
>
> --
> Yoann Congal
> Smile ECS
next prev parent reply other threads:[~2026-02-18 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 22:44 [OE-core][scarthgap][PATCH] gnupg: upgrade 2.4.8 -> 2.4.9 Peter Marko
2026-02-04 10:10 ` Yoann Congal
2026-02-18 21:28 ` Marko, Peter [this message]
2026-02-19 13:54 ` Yoann Congal
2026-02-22 20:53 ` Marko, Peter
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 7:14 [OE-core][scarthgap][patch] " Vijay Anusuri
2026-01-12 7:17 ` Marko, Peter
2026-01-12 7:29 ` Vijay Anusuri
2026-01-12 18:21 ` Yoann Congal
[not found] <1889800F45802F27.2902090@lists.openembedded.org>
2026-02-04 7:20 ` [OE-core][scarthgap][PATCH] " Marko, Peter
2026-02-04 8:11 ` Yoann Congal
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=AS1PR10MB5697F71F42D54E6DF1DBDA63FD6AA@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM \
--to=peter.marko@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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