From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <adam.duskett@amarulasolutions.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 6/6] dnf: Upgrade to 5.3.0.0
Date: Fri, 12 Dec 2025 18:49:49 +0100 [thread overview]
Message-ID: <DEWFF52P7FUG.1OYVLWLGCCZMD@bootlin.com> (raw)
In-Reply-To: <20251212103312.2077322-6-adam.duskett@amarulasolutions.com>
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 <adam.duskett@amarulasolutions.com>
> ---
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
prev parent reply other threads:[~2025-12-12 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 10:33 [PATCH v2 1/6] signing-keys.bb: Fix DISTRO_CODENAME truncation Adam Duskett
2025-12-12 10:33 ` [PATCH v2 2/6] libtoml: new recipe Adam Duskett
2025-12-12 10:33 ` [PATCH v2 3/6] libtoml11: cleanup package to adhere to the recipe style guide Adam Duskett
2025-12-12 10:33 ` [PATCH v2 4/6] libsolv: explicitly enable comps for rpm packageconfig Adam Duskett
2025-12-12 10:33 ` [PATCH v2 5/6] librepo: add PACKAGECONFIG[sequoia] Adam Duskett
2025-12-12 10:33 ` [PATCH v2 6/6] dnf: Upgrade to 5.3.0.0 Adam Duskett
2025-12-12 17:49 ` Mathieu Dubois-Briand [this message]
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=DEWFF52P7FUG.1OYVLWLGCCZMD@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=adam.duskett@amarulasolutions.com \
--cc=openembedded-core@lists.openembedded.org \
/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.