Description of problem: When trying to do a dnf system upgrade from Fedora 32 -> 33, the following error blocks the upgrade: Error: Problem: package python-srpm-macros-3.9-10.fc33.noarch requires redhat-rpm-config, but none of the providers can be installed - problem with installed package python-srpm-macros-3-59.fc32.noarch - package redhat-rpm-config-172-1.fc33.noarch requires kernel-srpm-macros, but none of the providers can be installed - redhat-rpm-config-150-1.fc32.noarch does not belong to a distupgrade repository - python-srpm-macros-3-59.fc32.noarch does not belong to a distupgrade repository - package kernel-srpm-macros-1.0-3.fc33.noarch is filtered out by exclude filtering Version-Release number of selected component (if applicable): How reproducible: 10 of 20 Fedora 32 workstations encountered the same upgrade error; several hours of debugging did not highlight a reason why some systems had this error while others did not. All systems have been serially updated using dnf from F29 -> F30 -> F31 -> F32 over the years. Steps to Reproduce: 1. dnf upgrade --refresh (and reboot if necessary) 2. dnf install dnf-plugin-system-upgrade (not needed on these system from previous upgrades) 3. dnf system-upgrade download --refresh --releasever=33 Actual results: Upgrade failed with error message above. Expected results: System upgrade to F33 using dnf system-upgrade reboot. Additional info: One one test system, I forced the upgrade with an --allowerasing flag, which allows the system to upgrade, but then hit multiple problems trying to install packages that were removed because of the same kernel-srpm-macros and redhat-rpm-config problems (not being able to install them).
Looking at the following line "package kernel-srpm-macros-1.0-3.fc33.noarch is filtered out by exclude filtering" I am guessing that you have something like exclude=kernel* in one, or many of your repo files in /etc/yum.repos.d/ and/or in /etc/dnf/dnf.conf Is this the case?
You are 100% correct. dnf.conf had that option set (not sure how/who did that at some point in the system's history). Thanks for the insight... that has brought closure to a lot of frustration and now will let the dnf-based system upgrade to proceed on other systems that were affected.
Good to hear. Are we ok closing this bug then?
Absolutely; close away!