This is a testing side-tag for collecting feedback on a proposed update that will switch to dnf5 as the system's default package manager in Fedora 41.
On a system running Fedora 41 Rawhide, update the dnf stack packages to the versions from this side-tag:
dnf upgrade dnf --enablerepo=side-tag --repofrompath=side-tag,'https://kojipkgs.fedoraproject.org/repos/f41-build-side-88363/latest/x86_64/' --best --nogpgcheck
After executing the transaction, the system will be configured to point the dnf command to the new version from the dnf5 package.
The former version of the dnf command is still available as the dnf-3 binary or the dnf4 symlink.
To revert to the previous version of dnf, use the following command:
dnf install dnf-4.19.2
For more details about each package update, refer to the upstream release notes:
Related system-wide change proposal:
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2024-8a41ea93a2Please login to add feedback.
| 0 | 0 | Test Case base update cli |
| 0 | 0 | Test Case createrepo c dnf |
| 0 | 0 | Test Case default font installation |
| 0 | 0 | Test Case langpacks packages |
| 0 | 0 | Test Case package install remove |
This update's test gating status has been changed to 'waiting'.
jkolarik edited this update.
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.
since you managed to disable autotime, this should be stuck in testing until you change that. I spent a bunch of time on this code in bodhi recently and, IIUC, rawhide updates can only be pushed stable by autotime. usually they are expected to have autotime set to 0 days, which means they go stable as soon as they pass gating. with autotime disabled it should be impossible for this update to go stable.
This update's test gating status has been changed to 'failed'.
jkolarik edited this update.
jkolarik edited this update.
New dnf works properly. Symlinks correctly point to the intended dnf versions.
Default font installation test case shows a diff with
fontquery-diff rawhide(f41 image is unavailable). Tested on rawhide.For the kiwi failure in openQA, it appears the kiwi configs need some updating for this change: https://pagure.io/fedora-kiwi-descriptions/pull-request/46 . probably only the removal of the 'dnf-yum' entries and the change in config.xml is critical there, the others are just cleanups. That one should only be merged together with this.
I think osbuild also needs a change for the dnf-yum problem: https://github.com/osbuild/images/pull/637 . that one could be merged ahead of time.
Lorax appears to be working ok. But osbuild-composer uses named groups which appear to have stopped working. I've filed https://github.com/rpm-software-management/dnf5/issues/1451 with a reproducer.
The cockpit failures in openQA turned out to be due to issues in the openQA test flow. I've fixed that, and I also patched the openQA kiwi container build test to patch the kiwi config on-the-fly to be suitable for dnf5. With those changes the tests should all pass (they are re-running now, they passed on staging).
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Everything seems to be roughly fine from testing I've done, including PackageKit. However,
fontquery-diff rawhideshows a diff.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.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.
ansible-core and fedrq have been updated to support dnf 5.2.0
jkolarik edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
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-upgradecommand.This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Tested 5.2.1.0 with lorax and osbuild and it works! Thanks for fixing the python API bindings.
jkolarik edited this update.
This update has been submitted for stable by bodhi