Description of problem: Gnome Software ignores my settings in yum/dnf configs, most importantly the 'exclude' setting. I am using it because of a tainted kernel. Version-Release number of selected component (if applicable): gnome-software-3.14.0-1.fc21.x86_64 How reproducible: Always Steps to Reproduce: 1. Add exclude=kernel* to {yum,dnf}.conf 2. (Optional) Reboot 3. Check for updates Actual results: Gnome Software still wants to update kernel, kernel-core, kernel-modules, and kernel-modules-extra Expected results: Gnome Software excludes these packages from the update. Additional info:
PackageKit doesn't use dnf or yum. We'd have to talk to the designers about how to handle this kind of thing in the UI.
Can I configure PackageKit to ignore certain packages then?
Richard: FWIW I'd agree with the reporter that it's pretty unfortunate we don't universally respect settings like this that aren't really package manager specific. I realize it might be a PITA to build, but I think it'd really be worth considering if there's some sort of way we can try and make all the supported package management stacks in F22 respect settings like this that are specified in yum configuration. Maybe we need some sort of store for package management configuration that isn't tied to a particular package manager, and a way to migrate settings into it from 'legacy' package manager configuration stores...
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
The general issue here is still outstanding, I think: we now have rather a bunch of package management tools and no common configuration for them.
Just hit the same issue, I'll excluded bacula from being updated. Until it will be fixed, I'll remove gnome-software as it could break the system.
Another example Keepassx was released in F23 as keepassx-0.4.3-13.fc23.x86_64 but then later upgraded to keepassx-2.0.0-1.fc23. The latter uses a different database format which is incompatible. I have tried version locking it but gnome software ignores the version lock and updates it. This database is shared among multiple users with multiple distros so I cannot just convert to the newer database format.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Having the same issue here. Will it be addressed for F24? I want to exclude=nodejs in my case, as i'm using nodesource for a newer version
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.
It seems pretty unlikely that this just magically got fixed with a version bump, so I'm re-opening it.
Confirm this bug exists in Fedora 26. Versionlock is ignored when updating system
This is not a bug on the gnome-software side, it's PackageKit, which should be updated/fixed, but it's in a maintenance mode, if I'm not mistaken. As Adam said, this needs a common place to set the settings and that being used by the package manages (yum/dnf/PackageKit/snap/dpkg/apt/Flatpak/...). The gnome-software is only a front end to those.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.