On 11/11/21 15:13, Tom R (Milwaukee WI) wrote:
My VPS provider prgmr.com duplicated my failed upgrade from fedora32 to
fedora33. In their testing, they were able to upgrade that host to fedora34
(i.e. go from fedora32 to fedora34). I'm happy to upgrade to fedora34.
My understanding of the previous history is that it that the upgrade was
successful, but for some reason it was having trouble booting. You
booted the F32 kernel, which worked, but you are still running F33.
Here's what my vps provider suggested I do:
# boot into fedora32, as root:
This is not a correct statement as I just mentioned.
$ dnf upgrade --refresh -y; sudo dnf system-upgrade download --releasever=34 -y; sudo dnf system-upgrade reboot
My concern: I have made no changes, but take a look: http://sprunge.us/wkziyU
I'm concerned that dnf would only update fedora33 packages (again I did not
run it). Should I be doing some cleanup first: http://sprunge.us/Cyhmq4
You are doing a normal upgrade, but the system is already mostly
up-to-date, so there's nothing much to do.
Is it safe to run
$ dnf history rollback 148
There's no way that will work.
Just do the system-upgrade to F34. Hopefully that will fix whatever is
currently going wrong.
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
