On Fri Dec 12, 2025 at 11:33 AM CET, Adam Duskett via lists.openembedded.org
wrote:
> Completely rewritten in C++, there are several changes needed
> to facilitate moving from DNF4 to DNF5. Below are some significant
> items to note:
>
> - The "-v/--verbose" cli option is removed. As such, remove the argument
> everywhere it was called.[1]
>
> - the rpmverbosity cli option is replaced with --setopt=rpmverbosity
>
> - Change gpgcheck to pkg_gpgcheck as this is what the documentation
> recommends.[2]
>
> - --nogpgcheck is now --no-gpgchecks
>
> - --setopt=protect_running_kernel=False has to be set or else every dnf
> transaction complains that /boot/vmlinuz-${kernel_version} does not
> exist in /var/log/dnf5.log. There is an open issue on github[3] to enable
> the currently not-yet implemented `autocheck_running_kernel option`, but
> it has been open for quite some time and the protect_running_kernel
> option supresses the message.
>
> - /var/cache/dnf is replaced with /var/cache/libdnf5
>
> - Add `features += 'PACKAGECONFIG:append:pn-rpm = " sequoia"\n'`
> `features += 'PACKAGECONFIG:append:pn-librepo = " sequoia"\n'`
> to test_testimage_dnf as librepo currently does not work
> with gpgme.
>
> While DNF5 has many config options, unfortunately, the majority
> of them depends on sdbus-c++, which is not included in OE-core.
> However, the package is included in meta-openembedded, so it's
> best to include the PACKAGECONFIG options in the recipe and
> leave them off.
>
> 1: https://github.com/rpm-software-management/dnf5/issues/464
> 2: https://dnf5.readthedocs.io/en/latest/dnf5.conf.5.html
> 3: https://github.com/rpm-software-management/dnf5/issues/1255
>
> Signed-off-by: Adam Duskett <[email protected]>
> ---
Hi Adam,
Thanks for your patch.
It looks like there is also a change with the --skip-broken argument:
ERROR: core-image-sato-1.0-r0 do_populate_sdk: Could not invoke dnf. Command
'...' returned 2:
Unknown argument "--skip-broken" for command "dnf5". Add "--help" for more
information about the arguments.
The argument is available for commands: module enable, environment install,
group install, replay, reinstall, downgrade, debuginfo-install, distro-sync,
install, do. (It has to be placed after the command.)
https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/2856
https://autobuilder.yoctoproject.org/valkyrie/#/builders/8/builds/2869
https://autobuilder.yoctoproject.org/valkyrie/#/builders/30/builds/2824
https://autobuilder.yoctoproject.org/valkyrie/#/builders/36/builds/2848
...
As expected, this is seen on almost all child builds of this a-full:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/2851
Can you have a look at the error?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#227609):
https://lists.openembedded.org/g/openembedded-core/message/227609
Mute This Topic: https://lists.openembedded.org/mt/116744110/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
