I’ve been using Fedora for quite some time but just switched over to Silverblue on version 35. When I installed Silverblue it created a boot entry for Fedora 34 as well as for the current version of 35.
When I upgraded to 36, I assumed the 34 entry would be removed and replaced by one for 35. That didn’t happen.
I have version 35 pinned along with the regular entries for 36, but that entry for version 34 is still there. When I look at rpm-ostree status, it does not show as pinned. How do I remove that entry so that I’m left with only version 35 and 36 now?
In hopes of not confusing @fooze666, but this is not true for Silverblue/Kinoite. By default there are only 2 deployments - the currently booted one and the previous (rollback) deployment. Additional deployments can be pinned manually. There are no kernel choices in GRUB, just deployment.
This is not a valid rpm-ostree command.
rpm-ostree remove is not a valid command, the command would be rpm-ostree uninstall .... This actually would not work in Silverblue, since the kernel is part of the base install. You’d have to do rpm-ostree override remove .... But don’t do that with the kernel. There are no kernel choices at boot as mentioned earlier; if you remove the kernel, the deployment will be unbootable.