I've noticed one test is failing due to new dnf5 syntax. I've created an upstream issue for that.

I've updated the dnf5 package to 5.2.1.0 which fixes already mentioned incompatible Python API bindings changes and also issues with system-upgrade command.

The reverse dependency builds were successful: https://copr.fedorainfracloud.org/coprs/jkolarik/dnf5-5.2.0.0/builds/. However, some errors might not be detected, such as issues with Python bindings that aren't caught during build-time tests but could occur at runtime.

I've also tested the 'default font installation' case in the Rawhide container, but I experience the same error with both dnf 4.19.2 and dnf5 5.2.0.0: fc-match is not installed. So FMPOV, it doesn't seem related.

I've realized I am not sure about Bodhi auto pushing the updates to Rawhide even if I deselected auto push in configuration. Therefore giving negative karma preventively.

According to the discussion in https://github.com/rpm-software-management/createrepo_c/issues/398, I'll create a successor of this bodhi to keep the drpm support in Fedora for now.

I've updated the changelog in the downstream spec and also the description of this bodhi.

Hi, this is connected with the https://bugzilla.redhat.com/show_bug.cgi?id=2213212. I've noticed right now that this should've been already included for the createrepo_c-1.0.0 release looking at the upstream changes, but was probably forgotten to do so in the downstream spec. I've linked the bodhi with that bug.

Hi there, as the https://bugzilla.redhat.com/show_bug.cgi?id=2245773 was not marked as a severe issue, we are planning to do the next build in the standard manner, in a few weeks.

I was looking into the new commits pushed since the previous dnf version and I don't see anything changed related to the repoquery output. I believe we are talking about this trigger from the fedora-update-feedback package: https://github.com/ironthree/fedora-update-feedback/blob/main/src/sysinfo.rs#L203.

And testing it locally on my installed packages set, I compared the dnf 4.16.2 output with dnf 4.18.0, apparently without any changes.

Please, if it is reproducible, file a bug against dnf in Bugzilla with specific input data. Thanks!

Based on the feedback above, dnf was rebuilt without the change "Do not print details of verifying (RhBug:1908253)" which was breaking the Anaconda usage. Should be fine now.

Based on the feedback above, dnf was rebuilt without the change "Do not print details of verifying (RhBug:1908253)" which was breaking the Anaconda usage. Should be fine now.

Based on the feedback above, dnf was rebuilt without the change "Do not print details of verifying (RhBug:1908253)" which was breaking the Anaconda usage. Should be fine now.

@adamwill Please do you know what is the problem with the remaining "running" test? When I open the details, it states "Result: passed" ...

This update has been unpushed.

But I guess the cause of not upgrading the package in this case could be the change of the default best option value to True which was not used before in Fedora.

Commit: https://github.com/rpm-software-management/dnf5/commit/42fd5777ec91d82f376af2bfb158e9b447385d3d. Discussion: https://github.com/rpm-software-management/dnf5/discussions/564.

Hello, sorry for maybe a dumb question, but I was looking into results of the previous bodhi update of dnf5-5.0.14 and there for the same testing module a different package was used ("pandoc-common"): https://openqa.fedoraproject.org/tests/1984487#step/base_update_cli/14. There the test has passed. Is it because of a change in test scenarios?

@orion I reproduced it having the dnf 4.15.1 and dnf5 5.0.11 in Rawhide. dnf upgrade then could be performed, while dnf5 is throwing the mentioned error. It seems to be connected with changes in handling of the protected packages in dnf and dnf5. Not sure we can do anything about it, but it should be working using the default dnf version at the time ...