Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: PackageKit failed to abide to exclude parameter within the repo file (i.e. updates) where it should skip that package similar to dnf command: dnf --exclude=kernel upgrade Version-Release number of selected component (if applicable): 1.1.5 How reproducible: Always Steps to Reproduce: 1. Add exclude=kernel in updates repo file to sync to other repo 2. 3. Actual results: PackageKit ignores exclude parameter set by repo file Expected results: PackageKit should abide to the rule set by repo file with exclude parameter Additional info: $ cat /etc/yum.repos.d/fedora-updates.repo | grep exclude exclude=kernel* $ cat /etc/yum.repos.d/_copr_mystro256-amd-staging-kernel.repo [mystro256-amd-staging-kernel] name=Copr repo for amd-staging-kernel owned by mystro256 baseurl=https://copr-be.cloud.fedoraproject.org/results/mystro256/amd-staging-kernel/fedora-$releasever-$basearch/ type=rpm-md skip_if_unavailable=True gpgcheck=1 gpgkey=https://copr-be.cloud.fedoraproject.org/results/mystro256/amd-staging-kernel/pubkey.gpg repo_gpgcheck=0 enabled=1 enabled_metadata=1 $ pkcon get-updates | grep kernel Available kernel-4.10.8-200.fc25.x86_64 (updates) Available kernel-core-4.10.8-200.fc25.x86_64 (updates) Available kernel-headers-4.10.8-200.fc25.x86_64 (updates) Available kernel-modules-4.10.8-200.fc25.x86_64 (updates)
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
Bumped to rawhide for the time being until https://fedoraproject.org/wiki/Changes/Unified_database_for_DNF addresses the issue.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
I cannot reproduce at least on f27, my test-case ( from bug #1572950 ) using updates-testing (that I have enabled). 1. sudo dnf update ... kernel x86_64 4.16.5-200.fc27 updates-testing 83 k (cancel) 2. pkcon get-updates ... Available kernel-4.16.5-200.fc27.x86_64 (updates-testing) The Linux kernel 3. edit /etc/yum.repos.d/fedora-updates-testing.repo to add exclude=kernel* 4. pkcon refresh force 5. sudo dnf update ... nothing... 6. pkcon get-updates ... nothing ... I suspect an important step missed for folks experiencing this may have been 4 ('pkcon refresh force'), to refresh PK cache/metadata... otherwise it may take waiting until your metadata cache expires (I'm not sure what the default is, but it could be awhile... maybe even 24 hrs).
*** Bug 1572950 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.