DNF upgrade from 31 to 32 fails

[mackissack (Alfredo C Harvey)]

Attempting to upgrade Fedora 31 to 32

[root@hy ahm]# dnf upgrade -y --refresh

run seamlessly
but

[root@hy ahm]# dnf system-upgrade download --releasever=32

caused the following error
occurred
Error:
Problema: package python2-beautifulsoup4-4.9.0-1.fc31.noarch requires python2-lxml, but none of the providers can be installed
- python2-lxml-4.4.0-1.fc31.x86_64 does not belong to a distupgrade repository
- problem with installed package python2-beautifulsoup4-4.9.0-1.fc31.noarch

Any suggestion?

[ersen]

use dnf system-upgrade download --releasever=32 --allowerasing. This will erase python2 packages which is unavailable in Fedora 32 and prevents you from upgrading. Read which other packages will also be erased before proceeding and cancel and ask here if you see any package other than these two.

[simmon (Great People OS)]

@mackissack

I agree @ersen comments. I think it would be better to install it separately after upgrading through that setting. by simmon (F32 Server KDE)

[mackissack (Alfredo C Harvey)]

You are a master, @ersen.

@ersen

system-upgrade download --releasever=32 --allowerasing

run smoothly and resulted in

and ended in

Thank you very much.
Where do I send the beers?

[salimma (Michel Lind (né Salim))]

@mackissack

Where do I send the beers?

Join us virtually at the Fedora Social Hour!

[qulogic (Elliott Sales de Andrade)]

I reported a bug because this sort of thing should be handled for you.

[iolaum (Nikolaos Perrakis)]

I had the same issue. Posted about my experience in the bug report created.

[computersavvy (Jeff V)]

It gives you the message so you can choose how to handle the offending files.
I would never consider that a bug because hiding what is happening is only one of the reasons I chose to leave Windows a long time ago.

[iolaum (Nikolaos Perrakis)]

It is a bug because the process is intended to complete successfully but instead doesn’t. There 's nothing that is hidden here. The confirmation screen lists all package changes/upgrades/removals. The problem is that one package was not being handled correctly and placed it’s appropriate place on the confirmation screen like all others were.