On 2020-05-13 05:51, Ed Greshko wrote:
On 2020-05-13 04:59, Samuel Sieb wrote:
> dnf specifically will not remove the running kernel. Even if you are running the
oldest kernel, it will not be removed. It will remove the oldest kernel that you are not
running. So, this should be irrelevant to the packagekit issue.
Yes, "dnf" will not remove the running kernel. But, are we 100% certain that
"pkcon" follows the same
rule? I suppose I could try it on a VM to test. And even if it doesn't
"today", it didn't always use libdnf.
So, it could be a remnant.
Well.....
[root@f30g ~]# uname -r
5.6.8-100.fc30.x86_64
[root@f30g ~]# pkcon remove kernel
Resolving [=========================] More than one package
matches:
1. kernel-5.5.8-100.fc30.x86_64 [installed:updates]
2. kernel-5.5.10-100.fc30.x86_64 [installed:updates]
3. kernel-5.6.8-100.fc30.x86_64 [installed:updates]
Please choose the correct package: 3
[=========================]
Starting [=========================]
Testing changes [=========================]
Finished [ ] (0%)
The following packages have to be removed:
kernel-5.6.8-100.fc30.x86_64 The Linux kernel
Proceed with changes? [N/y] y
[=========================]
Testing changes [=========================]
Removing [=========================]
Requesting data [=========================]
Finished [=========================]
[root@f30g ~]# rpm -q kernel
kernel-5.5.8-100.fc30.x86_64
kernel-5.5.10-100.fc30.x86_64
However, it didn't actually delete anything since upon reboot it was still in the boot
menu and
[root@f30g ~]# uname -r
5.6.8-100.fc30.x86_64
But still...
[root@f30g ~]# rpm -q kernel
kernel-5.5.8-100.fc30.x86_64
kernel-5.5.10-100.fc30.x86_64
So, it is at least marked as removed in the rpm database. This probably will result in
images being left on
disk. Not a big deal but could cause some confusion to the user at some point.
Maybe that would be a similar result on an "upgrade-system"?
Oh, and for the record....
[root@f30g ~]# dnf erase kernel-5.6.8
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Removing:
kernel x86_64 5.6.8-100.fc30 @updates 0
Transaction Summary
================================================================================
Remove 1 Package
Freed space: 0
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Erasing : kernel-5.6.8-100.fc30.x86_64 1/1
Running scriptlet: kernel-5.6.8-100.fc30.x86_64 1/1
Verifying : kernel-5.6.8-100.fc30.x86_64 1/1
Removed:
kernel-5.6.8-100.fc30.x86_64
Complete!
[root@f30g ~]# uname -r
5.6.8-100.fc30.x86_64
[root@f30g ~]# rpm -q kernel
kernel-5.5.8-100.fc30.x86_64
kernel-5.5.10-100.fc30.x86_64
So, dnf does the same.
FWIW, this holds true for "erase" of any kernel. It just translates in to
"mark uninstalled".
Anyway, I think this has been flogged enough. :-)
--
The key to getting good answers is to ask good questions.