Closed evan-goode closed 1 year ago
I altered the requires so users do not broken deps. And built the new version in rawhide.
This tool mainly calls dnf distro-sync
. I checked that dnf5 distro-sync
seems to work too.
The main work will have to be done when F40 is branched because we will be upgrading from F39 to F40 using DNF5 for the first time.
(I'm filing issues with all the packages that currently depend on
dnf
.)DNF 5 is a new package manager that will replace DNF 4 in Fedora 39+: Starting in Fedora 39, the
dnf
command will be provided by thednf5
package rather than thednf
package, anddnf5
will obsoletednf
. Since fedora-upgrade currently depends on DNF 4, it should choose one of the following strategies to avoid breaking the Fedora upgrade:dnf5
package in Fedora 39+ instead ofdnf
. Builds of DNF 5 are available in this COPR repository: https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/dnf5-unstable, and documentation is available here: https://dnf5.readthedocs.io/en/latest/.python3-dnf
instead ofdnf
, and call thednf-3
binary instead ofdnf
. The old DNF 4 command will still be available in the distribution, but only asdnf-3
(the binary is calleddnf-3
rather thandnf4
for historical reasons; it is the "Python 3 version" of DNF). The first option is preferred to this one; it is not recommended to modify installed software using both DNF 4 and DNF 5 on the same system.At some point, this project should adopt DNF 5, but the immediate issue is removing the dependency on
dnf
. We are planning to replace DNF with DNF5 in Fedora Rawhide very soon, by 2023-06-01, and the fedora-upgrade package will break as long as it still depends on thednf
package.For more information about the switch to DNF 5, see https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5.