I tried to upgrade to Fedora 30 by using this command: dnf system-upgrade download --releasever=30 This resulted in: Error: Problem 1: package python2-hawkey-0.31.0-2.fc29.x86_64 requires libdnf(x86-64) = 0.31.0-2.fc29, but none of the providers can be installed - libdnf-0.31.0-2.fc29.x86_64 does not belong to a distupgrade repository - problem with installed package python2-hawkey-0.31.0-2.fc29.x86_64 Problem 2: package python3-hawkey-0.28.1-1.fc30.x86_64 requires libdnf(x86-64) = 0.28.1-1.fc30, but none of the providers can be installed - cannot install both libdnf-0.28.1-1.fc30.x86_64 and libdnf-0.31.0-2.fc29.x86_64 - problem with installed package python3-hawkey-0.31.0-2.fc29.x86_64 - package python2-libdnf-0.31.0-2.fc29.x86_64 requires libdnf(x86-64) = 0.31.0-2.fc29, but none of the providers can be installed - python3-hawkey-0.31.0-2.fc29.x86_64 does not belong to a distupgrade repository - problem with installed package python2-libdnf-0.31.0-2.fc29.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages) I did: # dnf remove python2-hawkey The next try resulted in: Error: Problem: package python2-libdnf-0.31.0-2.fc29.x86_64 requires libdnf(x86-64) = 0.31.0-2.fc29, but none of the providers can be installed - libdnf-0.31.0-2.fc29.x86_64 does not belong to a distupgrade repository - problem with installed package python2-libdnf-0.31.0-2.fc29.x86_64 (try to add '--skip-broken' to skip uninstallable packages) I did: # dnf remove python2-libdnf After this I could proceed with the download of the Fedora 30 packages. Shouldn't python2-hawkey and python2-libdnf be automatically removed?
> Shouldn't python2-hawkey and python2-libdnf be automatically removed? They should. dnf people: please update the obsoletes in fedora-obsolete-packages when you bump dnf in Fedora 29.
Time ago I opened a bug on fedora-obsoletes-packages - https://bugzilla.redhat.com/show_bug.cgi?id=1632564. Hope that the issue will be solved ASAP. *** This bug has been marked as a duplicate of bug 1632564 ***