Description of problem: Trying to upgrade from Fedora 30 to Fedora 31, I'm getting this error: terminate called after throwing an instance of 'libdnf::ModulePackageContainer::EnableMultipleStreamsException' what(): Cannot enable multiple streams for module 'maven' Aborted (core dumped) Version-Release number of selected component (if applicable): dnf-4.2.18-1.fc30.noarch How reproducible: 100 % (happens on all my Fedora 30 machines) Steps to Reproduce: 1. dnf system-upgrade --releasever=31 --best --allowerasing download Actual results: Crash Expected results: Upgrade Additional info: 1. Retrace server doesn't work so I don't have the coredump or a backtrace. 2. It's impossible to file bugs for Fedora 30 now, so filed as F31.
This https://unix.stackexchange.com/questions/579184/upgrade-from-fedora-30-to-31-cannot-enable-multiple-streams-for-module-ant/582610#582610 seems to be the same thing. Let's try dnf module disable maven and then just run system upgrade the standard way: dnf system-upgrade download --releasever=31
there was a fix for this pending in updates-testing when F30 went EOL. It should still be there. It will never hit stable, though, because we don't do stable pushes for EOL releases. *** This bug has been marked as a duplicate of bug 1811234 ***
Just for the record: Disabling all modules that 'dnf module list --enabled' listed helped. Of course, I've never enabled those modules manually or intentionally. And I wonder how other users avoided this issue because it happened with GIMP as well, which is probably part of vast majority of Fedora installations.
@adam this is quite 'catch-22' problem as the upgrade failure blocks the upgrade to supported release.
Most people who hit this figured out on their own to disable the affected module(s). Also I think fewer people have GIMP installed than you assume :) Andrej: all the fix really did was reset all the modules. You can do that yourself easily enough. You can still install it from updates-testing, too, I think (haven't tested, but it ought to work).
I figured this out by myself, but was helping others in despair with the same problem. When you mentioned there is an fix but didn't make into updates I thought some fixes of upgrade process could go beyond EOL mark (especially when the work was already done) to improve overall Fedora status. Maybe marketing could spend some bucks to promote Fedora this way.