All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Zoltán Böszörményi" <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>
Subject: Re: [OE-core][PATCH v8 1/5] rpm-sequoia-crypto-policy: New recipe
Date: Thu, 06 Feb 2025 11:16:47 +0100	[thread overview]
Message-ID: <D7LA9XGPGG5H.287DBDA93AM2K@bootlin.com> (raw)
In-Reply-To: <20250206055222.3319167-1-zboszor@gmail.com>

On Thu Feb 6, 2025 at 6:52 AM CET, Zoltán Böszörményi wrote:
> This ships a crypto policy file for rpm-sequoia.
>
> Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
> ---

Hi Zoltán,

Thanks for the patch update.

I believe there is a regression introduced by this version of your
series, several builds are failing with:

ERROR: rpm-sequoia-crypto-policy-native-20250124-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/temp/run.do_compile.537997' failed with exit code 2
Log data follows:
| DEBUG: Executing shell function do_compile
| asciidoc -v -d manpage -b docbook crypto-policies.7.txt
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/recipe-sysroot-native/usr/lib/python3.13/site-packages/asciidoc/resources/asciidoc.conf
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/sources-unpack/git/crypto-policies.7.txt
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/recipe-sysroot-native/usr/lib/python3.13/site-packages/asciidoc/resources/docbook45.conf
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/recipe-sysroot-native/usr/lib/python3.13/site-packages/asciidoc/resources/filters/source/source-highlight-filter.conf
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/recipe-sysroot-native/usr/lib/python3.13/site-packages/asciidoc/resources/filters/code/code-filter.conf
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/recipe-sysroot-native/usr/lib/python3.13/site-packages/asciidoc/resources/filters/latex/latex-filter.conf
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/recipe-sysroot-native/usr/lib/python3.13/site-packages/asciidoc/resources/filters/graphviz/graphviz-filter.conf
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/recipe-sysroot-native/usr/lib/python3.13/site-packages/asciidoc/resources/filters/music/music-filter.conf
| asciidoc: reading: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/recipe-sysroot-native/usr/lib/python3.13/site-packages/asciidoc/resources/lang-en.conf
| asciidoc: writing: /srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/rpm-sequoia-crypto-policy-native/20250124/sources-unpack/git/crypto-policies.7.xml
| xsltproc --nonet -o crypto-policies.7 /usr/share/asciidoc/docbook-xsl/manpage.xsl crypto-policies.7.xml
| warning: failed to load external entity "/usr/share/asciidoc/docbook-xsl/manpage.xsl"
| cannot parse /usr/share/asciidoc/docbook-xsl/manpage.xsl
| make: *** [Makefile:137: crypto-policies.7] Error 4
| WARNING: exit code 2 from a shell command.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/870/steps/14/logs/stdio

Might this be a missing dependency ?


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



  parent reply	other threads:[~2025-02-06 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06  5:52 [OE-core][PATCH v8 1/5] rpm-sequoia-crypto-policy: New recipe Zoltán Böszörményi
2025-02-06  5:52 ` [OE-core][PATCH v8 2/5] rpm-sequoia: New recipe for version 1.7.0 Zoltán Böszörményi
2025-02-06  5:52 ` [OE-core][PATCH v8 3/5] rpm: Set SEQUOIA_CRYPTO_POLICY in wrapped tools Zoltán Böszörményi
2025-02-06  5:52 ` [OE-core][PATCH v8 4/5] dnf: " Zoltán Böszörményi
2025-02-06  5:52 ` [OE-core][PATCH v8 5/5] oeqa/selftest/cases/signing.py: Re-enable self-test Zoltán Böszörményi
2025-02-06 10:16 ` Mathieu Dubois-Briand [this message]
2025-02-06 10:42   ` [OE-core][PATCH v8 1/5] rpm-sequoia-crypto-policy: New recipe Böszörményi Zoltán
2025-02-06 10:51     ` Alexander Kanavin
     [not found]     ` <182198F3C56EC291.752@lists.openembedded.org>
2025-02-06 10:53       ` Alexander Kanavin
2025-02-06 11:49         ` Böszörményi Zoltán
2025-02-06 12:08           ` Alexander Kanavin
2025-02-06 10:46 ` Alexander Kanavin

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=D7LA9XGPGG5H.287DBDA93AM2K@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=alex.kanavin@gmail.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.