Prepare for DNF 5, don't depend on `dnf` about mock HOT 6 CLOSED

The compat with dnf-4 (not dnf-3?) will have to be implemented, still not there.

What are your plans WRT build systems? Do you plan to build (in Koji, Copr) Fedora 39 since
day one (202306-01)? Have you discussed this with Fedora infra team?

from mock.

It is actually dnf-3.

from mock.

I see, dnf-3 comes from the dnf-2 vs dnf-3 time (python2 vs python3).

from mock.

See also the discussion here: https://pagure.io/releng/issue/11441

The conclusion seems to be we'll build Rawhide with DNF4 for some transition period.
For this, we need to ship an updated fedora-rawhide configuration (mock-core-configs)
with

config_opts["dnf_command"] = "/usr/bin/dnf-3"
config_opts["dnf_install_command"] = "install python3-dnf dnf-plugins-core"

Without this, Copr (and local Mock) will fail to build once the Rawhide chroot is changed.

Since python3-dnf provides dnf-3 since ever (even on EL8), we might even consider
doing this for all Fedora versions.

from mock.

And actually -> we should even consider changing system_dnf_command option,
because Mock on Rawhide would use /bin/dnf for installing the bootstrap chroot.

from mock.

I see, dnf-3 comes from the dnf-2 vs dnf-3 time (python2 vs python3).

Yes! I should have mentioned that; it's confusing for sure.

from mock.