Description of problem:
DEBUG util.py:600: Error:
DEBUG util.py:600: Problem: package python3-dnf-4.2.21-2.fc33.noarch requires python3-hawkey >= 0.46.2, but none of the providers can be installed
DEBUG util.py:600: - package python3-hawkey-0.48.0-1.fc33.x86_64 conflicts with python3-dnf < 4.2.23 provided by python3-dnf-4.2.21-2.fc33.noarch
DEBUG util.py:600: - package dnf-4.2.21-2.fc33.noarch requires python3-dnf = 4.2.21-2.fc33, but none of the providers can be installed
DEBUG util.py:600: - package supermin-5.2.0-2.fc33.x86_64 requires dnf, but none of the providers can be installed
DEBUG util.py:600: - package libguestfs-1:1.42.0-7.fc33.x86_64 requires supermin >= 5.1.18, but none of the providers can be installed
DEBUG util.py:600: - package libguestfs-devel-1:1.42.0-7.fc33.x86_64 requires libguestfs.so.0()(64bit), but none of the providers can be installed
DEBUG util.py:600: - package libguestfs-devel-1:1.42.0-7.fc33.x86_64 requires libguestfs(x86-64) = 1:1.42.0-7.fc33, but none of the providers can be installed
DEBUG util.py:600: - conflicting requests
Full log here:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Build any package that BR's dnf.
Thanks, I will try it out as soon as the build is available in Koji.
I guess it's using the new version but still couldn't build:
What's really odd is that "libdnf" appears nowhere in the root.log.
The commit I've linked is not the fix, but the cause.
libdnf produces python3-hawkey
Should we untag the latest libdnf here? Or is there more interdependent packages that would be broken by that?
Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (firstname.lastname@example.org).
All subpackages of a package agaisnt which this bug was filled are now installable or removed from Fedora 33.
Thanks for taking care of it!
Sorry, this was my bad. We didn't build all the packages as soon as we could, so the transition period was longer.
In fact thank you Igor for building the new dnf-plugins-core.
Unfortunately the dependencies worked out that new libdnf conflicts with older dnf and new dnf conflicts with older dnf-plugins-core.
Can confirm it works now.