On 2020-05-03 2:10 p.m., Ranjan Maitra wrote:
So, it appears based on your description that rxvt on F32 is behind rxvt on F31. I suspect that in this situation I would do one of two things.
1. Wait a few days and let the problem take care of itself as the F32 package gets updated.
2. dnf erase rxvt and upgrade. Then, after the system comes back with F32, dnf install rxvt. Of course, this assumes that you have some terminal window option.
HTH,
Many thanks and best wishes,
Ranjan
On Sun, 3 May 2020 12:24:22 -0400 Frank <beacon@xxxxxxxxxxxx> wrote:
I am blocked upgrading my 31 to 32. Updated 31, and did the "sudo dnf
system-upgrade download --releasever=32 --allowerasing". It dl 1.2 gigs of
packages, and at the very end told me rxvt was being blocked because of
a conflict with the newer version.
I then ran "sudo dnf system-upgrade reboot" and it said system is not
ready for upgrade.
I am stumped!
Any suggestions??
That's what I ended up doing. It appeared after close examination
that RXVT was the only
thing blocking the upgrade. DNF had not removed the old one even though
I ran DNF with
allow-erasing on the command line.
After I removed RXVT and re-ran DNF system-upgrade with an additional
--setopt=keepcache=1 on the command
line when it finished quite quickly....then dnf system-upgrade reboot
worked fine. A long time later I had my F32 desktop
back. Since then I've had a few crashes but nothing serious.
Thanks
_______________________________________________
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
