> Any suggestions about any of these conflicts? > > sudo dnf system-upgrade download --refresh --releasever=32 > sudo dnf system-upgrade download --refresh --releasever=32 > Before you continue ensure that your system is fully upgraded by running "dnf > --refresh upgrade". Do you want to continue [y/N]: y > y > Copr repo for kde owned by zawertun > 4.9 MB/s | 2.2 MB 00:00 [... snip ...] > Yarn Repository > 1.3 MB/s | 363 kB 00:00 > Modular dependency problem: > > Problem: conflicting requests > - nothing provides module(platform:f31) needed by module > gimp:2.10:3120191106095052:f636be4b-0.x86_64 > Error: > Problem 1: package boost-mpich-python2-1.69.0-10.fc31.x86_64 requires boost-mpich(x86-64) > = 1.69.0-10.fc31, but none of the providers can be installed > - boost-mpich-1.69.0-10.fc31.x86_64 does not belong to a distupgrade repository > - problem with installed package boost-mpich-python2-1.69.0-10.fc31.x86_64 [... snip ...] > - python2-dateutil-1:2.8.0-3.fc31.noarch does not belong to a distupgrade repository > - problem with installed package python2-matplotlib-tk-2.2.5-1.fc31.x86_64 > (try to add '--skip-broken' to skip uninstallable packages) Earlier this month (April 09), I had similar (not identical) problems when I tried to upgrade from f30 to f31. The thread for that is here: "https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/thread/JSBAFNVISAMQYHDYRYSPBAUOGGLVH2JZ/";. Maybe that will help. * I am not a sys.admin., * I was upgrading to f31 and you're upgrading to f32, and * there are other significant differences in out systems. Other members of this list are much more knowledgeable and experienced with these things. So please get their confirmation, comments, etc. before trying anything that I did that is likely to have significant risk. The key step in what I did seems to have been what Stan suggested: ----- It looks like you are having module problems. I don't know if this will help, but while testing upgrade from F31 to F32 to look for issues, we were advised to run dnf module reset '*' to make modules behave before running the upgrade. You could try that. ----- Good luck. Bill. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
