Hide Forgot
On one particular machine that has recently been updated to Fedora 26: $ dnf repoquery --unsatisfied Last metadata expiration check: 0:00:05 ago on Thu Jul 20 11:40:40 2017. The operation would result in removing the following protected packages: kernel-core This message doesn't seem to make sense for a query operation! Here are all the kernel packages that are installed on the machine: kernel-4.11.10-300.fc26.x86_64 kernel-4.11.8-200.fc25.x86_64 kernel-4.11.9-300.fc26.x86_64 kernel-core-4.11.10-300.fc26.x86_64 kernel-core-4.11.8-200.fc25.x86_64 kernel-core-4.11.9-300.fc26.x86_64 kernel-devel-4.11.10-300.fc26.x86_64 kernel-devel-4.11.8-200.fc25.x86_64 kernel-devel-4.11.9-300.fc26.x86_64 kernel-headers-4.11.10-300.fc26.x86_64 kernel-modules-4.11.10-300.fc26.x86_64 kernel-modules-4.11.8-200.fc25.x86_64 kernel-modules-4.11.9-300.fc26.x86_64 kernel-tools-libs-4.11.10-300.fc26.x86_64 The currently running kernel is 4.11.9-300.fc26.x86_64 Here are the dnf-related packages on the machine: dnf-2.5.1-1.fc26.noarch dnf-conf-2.5.1-1.fc26.noarch python3-dnf-plugin-system-upgrade-2.0.1-1.fc26.noarch python2-dnf-plugins-extras-common-2.0.1-1.fc26.noarch dnf-plugins-core-2.1.2-2.fc26.noarch python2-dnf-2.5.1-1.fc26.noarch python3-dnf-plugins-core-2.1.2-2.fc26.noarch python3-dnf-plugins-extras-common-2.0.1-1.fc26.noarch dnf-yum-2.5.1-1.fc26.noarch python3-dnf-2.5.1-1.fc26.noarch python2-dnf-plugin-system-upgrade-2.0.1-1.fc26.noarch libdnf-0.9.2-1.fc26.x86_64 python2-hawkey-0.9.2-1.fc26.x86_64 python3-hawkey-0.9.2-1.fc26.x86_64 libsolv-0.6.28-1.fc26.x86_64
*** Bug 1484420 has been marked as a duplicate of this bug. ***
I created a patch that should solve the problem (https://github.com/rpm-software-management/dnf/pull/914).
*** Bug 1492389 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This particular problem seems solved. Can we close the ticket?
We will close it after release. Ii it OK?
Fine by me. Thanks! :)
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
this is *not* solved ------------------- [root@firewall:~]$ dnf repoquery --unsatisfied Last metadata expiration check: 0:01:09 ago on Sat Sep 7 17:15:40 2019. Problem: The operation would result in removing the following protected packages: kernel-core -------------------- after rpm was too dumb too handle immutable files in a proper way resulting in cpio errors and neither the old version nor the new are in the rpm database i just wanted to find out what packages (besides glibc - which i just 'dnf install glibc'-ed) are missing from the database to simply install them dnf-4.2.8-1.fc30.noarch dnf-data-4.2.8-1.fc30.noarch libdnf-0.35.2-1.fc30.x86_64 python3-dnf-4.2.8-1.fc30.noarch python3-dnf-plugin-leaves-4.0.9-1.fc30.noarch python3-dnf-plugins-core-4.0.9-1.fc30.noarch python3-libdnf-0.35.2-1.fc30.x86_64