From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: zboszor@gmail.com, openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
Randy MacLeod <randy.macleod@windriver.com>,
Khem Raj <raj.khem@gmail.com>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Subject: Re: [OE-core][PATCH v9 1/5] rpm-sequoia-crypto-policy: New recipe
Date: Fri, 07 Feb 2025 10:25:41 +0000 [thread overview]
Message-ID: <3e8003570397e8eb864a55cad9a2f8668d114112.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250206114547.3441965-1-zboszor@gmail.com>
On Thu, 2025-02-06 at 12:45 +0100, Zoltan Boszormenyi via lists.openembedded.org wrote:
> This ships a crypto policy file for rpm-sequoia.
>
> Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
> ---
> meta/conf/distro/include/maintainers.inc | 1 +
> ...1-Make-xsltproc-settable-as-XSLTPROC.patch | 43 +++++++++++++++++++
> ...002-Don-t-use-hardcoded-python3-path.patch | 41 ++++++++++++++++++
> .../rpm-sequoia-crypto-policy_git.bb | 34 +++++++++++++++
> 4 files changed, 119 insertions(+)
> create mode 100644 meta/recipes-devtools/rpm-sequoia/rpm-sequoia-crypto-policy/0001-Make-xsltproc-settable-as-XSLTPROC.patch
> create mode 100644 meta/recipes-devtools/rpm-sequoia/rpm-sequoia-crypto-policy/0002-Don-t-use-hardcoded-python3-path.patch
> create mode 100644 meta/recipes-devtools/rpm-sequoia/rpm-sequoia-crypto-policy_git.bb
The new recipe doesn't seem to build on musl:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/969
https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/985/steps/11/logs/stdio
and the policy recipe is struggling in world builds such:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/958/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/956/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/956
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/887/steps/11/logs/stdio
and in reproducibility testing as a build failure:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/37/builds/993/steps/12/logs/stdio
Cheers,
Richard
next prev parent reply other threads:[~2025-02-07 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 11:45 [OE-core][PATCH v9 1/5] rpm-sequoia-crypto-policy: New recipe Zoltán Böszörményi
2025-02-06 11:45 ` [OE-core][PATCH v9 2/5] rpm-sequoia: New recipe for version 1.7.0 Zoltán Böszörményi
2025-02-06 11:45 ` [OE-core][PATCH v9 3/5] rpm: Set SEQUOIA_CRYPTO_POLICY in wrapped tools Zoltán Böszörményi
2025-02-06 11:45 ` [OE-core][PATCH v9 4/5] dnf: " Zoltán Böszörményi
2025-02-06 11:45 ` [OE-core][PATCH v9 5/5] oeqa/selftest/cases/signing.py: Re-enable self-test Zoltán Böszörményi
2025-02-07 10:25 ` Richard Purdie [this message]
2025-02-08 6:57 ` [OE-core][PATCH v9 1/5] rpm-sequoia-crypto-policy: New recipe Böszörményi Zoltán
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=3e8003570397e8eb864a55cad9a2f8668d114112.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=zboszor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.