Hi, I'm having trouble with dnf and the 5.19 kernel.
I have tried to exclude the 5.19 kernel on this system (FC37) because 1) Virtual box doesn't seem to support it yet, 2) the system gets stuck during boot and the boot will NOT succeed (It seems to be running a list of UUIDs). The problem: somehow I managed to upgrade to the 5.19 kernel and am now stuck. dnf seems to want to remove EVERYTHING that it thinks is dependent on this kernel.I have used this command "dnf --noautoremove erase kernel-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64 kernel-core-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64 kernel-devel-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64 kernel-headers-5.19.0-0.rc5.git0.1.fc37.x86_64 kernel-modules-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64 kernel-modules-extra-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64' which is where the 501 dependencies comes from. I am a loss as to just what to do to get 5.19 out of my system. Is this happenstance a bug? Do all these packages REALLY depend on the kernel version? "Normally" I would do something like "rpm --nodeps -e kernel*5.19*". Could the solution be that simple? Any thoughts/hints/tips/suggestions would be greatly appreciated. Best regards, George... _______________________________________________ test mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
