From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <adam.duskett@amarulasolutions.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v9 4/5] dnf: Upgrade to 5.4.4.0
Date: Tue, 08 Sep 2026 06:42:46 +0200 [thread overview]
Message-ID: <DL9NRM24QNZE.33T8JAD1GBY1W@bootlin.com> (raw)
In-Reply-To: <20260907135607.4132821-4-adam.duskett@amarulasolutions.com>
On Mon Sep 7, 2026 at 3:56 PM CEST, 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:
>
> - Added a negative lookahead filter for the following warning if
> RPM_SIGN_PACKAGES != '1': "Warning: skipped OpenPGP checks"
> This warning is hard-coded and piped to stderr if gpg checks
> are disabled. However, most users do not sign their RPM packages
> and use dnf to simply construct the rootfs.
>
> - 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.
>
> - Move --skip-broken to after the install argument as the global
> --skip-broken argument is removed.
>
> - /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.
>
> - Change `if e_output.startswith("Error in POSTIN scriptlet in rpm package"):`
> to `if "%post(" in e_output and "scriptlet failed" in e_output.
>
> 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 by default.
>
> 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,
This has been failing on my side:
ERROR: dnf-native-5.4.4.0-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/x86_64-linux/dnf-native/5.4.4.0/temp/run.do_compile.2140500' failed with exit code 1
...
| /srv/pokybuild/yocto-worker/genericx86-64/build/build/tmp/work/x86_64-linux/dnf-native/5.4.4.0/sources/dnf-5.4.4.0/libdnf5-cli/session.cpp:257:36: error: ‘parse’ is not a member of ‘std::chrono’
| 257 | ss >> std::chrono::parse("%F", tp);
| |
...
https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4618
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-09-08 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 13:56 [PATCH v9 1/5] json-c: add patch to fix compiling with a C++ compiler Adam Duskett
2026-09-07 13:56 ` [PATCH v9 2/5] libtoml11: new recipe Adam Duskett
2026-09-07 16:10 ` [OE-core] " Khem Raj
2026-09-07 13:56 ` [PATCH v9 3/5] libsolv: explicitly enable comps for rpm packageconfig Adam Duskett
2026-09-07 13:56 ` [PATCH v9 4/5] dnf: Upgrade to 5.4.4.0 Adam Duskett
2026-09-08 4:42 ` Mathieu Dubois-Briand [this message]
2026-09-07 13:56 ` [PATCH v9 5/5] libdnf: remove recipe Adam Duskett
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=DL9NRM24QNZE.33T8JAD1GBY1W@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox