On Mon, 19 Jan 2026 at 07:09, <[email protected]> wrote:
>   - 0001-macros.in-Set-_rpmformat-to-4.patch
>     Fixed:
>     error: External dependency generator is incompatible with v6 packages

This one is creating technical debt. I can imagine support for v4
packages will be dropped at some not-too-distant point. We've had this
deprecation warning for a long time, but it looks like the matter is
becoming more pressing now. Can you look into it?

>   - 0001-macros.in-Set-_pkgverify_level-to-digest-as-RCPM-4.2.patch
>     Fixed:
>     GPG check FAILED
>
> * Add scdoc-native to DEPENDS to fix do_configure error for both native and
>   target:
>   Could not find SCDOC using the following names: scdoc

Is this a hard dependency? Is there a cmake switch to turn it off?

>   Note, both target and native need scdoc-native.
>
> * Add bash to RDEPENDS:${PN} to fix:
>   ERROR: rpm-1_6.0.1-r0 do_package_qa: QA Issue: 
> /usr/lib/rpm/rpm-setup-autosign
>   contained in package rpm requires /bin/bash, but no providers found in
>   RDEPENDS:rpm? [file-rdeps]

All things that depend on bash are specifically placed into
${PN}-build, so that the main package will not pull in gplv3 licensed
items. I can imagine this will fail in no-gpl3 tests too.

> -EXTRA_OECMAKE:append:class-native = " -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var"
> +EXTRA_OECMAKE:append:class-native = " -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DLIBELF_FOUND=False"

Addition of LIBELF_FOUND=False is not explained. Also I think it can
be easily provided?

Otherwise, looks good, thanks for working on it!

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#229615): 
https://lists.openembedded.org/g/openembedded-core/message/229615
Mute This Topic: https://lists.openembedded.org/mt/117340910/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to