Stan, Thank you for your response... it's DEFINITELY appreciated. A little misunderstanding here though. I could have been more explicit in the description of my problem. I have seen this situation before (and written bug reports on it). This situation looks like a packaging(?) problem. I once tried this kind of thing and dnf came back with > 800 (maybe 1400) packages to remove... including rpm and dnf et. al.... NOT GOOD. It's good that dnf asks if it's ok to proceed. Whew. Bullet dodged. So... I'm not trying to back out to fc31... all my kernels are f32. You DO bring out an interesting possibility though. If the newer f32 kernels depend on different "things" than the older f32 kernel I want to keep... there would be a big problem. Sigh. I haven't seen anything like that though. Yay! The "real" situation is that I have frozen this system's kernel at an older version because of problems with the newer kernels going crazy... reporting apparent stalling on cpus (excessive disablement maybe). I thought I had a broken cpu but went back to the oldest kernel and the messages went away. I haven't written a bug on this mainly because I haven't had much luck with reporting kernel bugs. This current effort was the beginning of an effort to get the most current kernel and see if the problem persists... and then report the bug... if that's what it is. Just talking with you has given me an idea though. I could change the # of kernels to retain, install the latest kernel, test for messages, write a bug if the problem still appears... AND I'd still have my latest kernel. I'll give that a try. So... THANKS for your help It was GOOD "talking" with you, George... On Thursday, October 24, 2019, 12:24:20 PM PDT, stan <xrnu@xxxxx> wrote: On Thu, 24 Oct 2019 18:12:22 +0000 (UTC) George R Goffe via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > I am attempting to remove old kernels from my system but "dnf erase > <kernel-package>" wants to remove much more than just that kernel > package. I wrote a bug at bugzilla.redhat.com but have gotten > nowhere. This is the bug URL: 1761024 – removing old kernels wants to > remove more than kernel packages This is really a question for the test list, since you are using rawhide. That alone makes diagnosing the problem difficult, since there can be incompatibilities because of new version and process introduction in rawhide. The rule for running rawhide is, 'if it breaks, you get to keep the pieces', though it is rare that developers don't fix things to avoid that drastic an outcome. And they do need people like you running it and reporting problems so they can be fixed before rawhide becomes a release candidate. That said, early in the rawhide cycle, like now, when F31 hasn't even been released, things can be a little chaotic. > > 1761024 – removing old kernels wants to remove more than kernel > packages > > > > I want to keep the oldest kernel and remove the "newer" kernels. At a guess, I think this is the source of your problem. You are trying to remove f32 kernels, and return to an f31 kernel. There is probably some link between packages compiled under the new regime (newer gcc?, newer glibc?) than in f31, so it has to remove all those packages in order to be compatible. You could try letting the removals complete, keeping track of the packages removed, and then installing them after f32 is purged, from the f31 repositories. Alternatively, you could force a return to f31 by manually installing the fedora-release\* and fedora-repo packages for f31 and running a dnf distrosync to remove / replace anything newer than f31. _______________________________________________ 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
