Description of problem: I'm not sure if it's related to `procps-ng` itself or a bug in `versionlock` plugin which gets triggered on `procps-ng`, but `procps-ng` still shows up in `dnf update` even after it's locked using `dnf versionlock add procps-ng`. Version-Release number of selected component (if applicable): dnf.noarch 4.7.0-1.fc34 @updates dnf-data.noarch 4.7.0-1.fc34 @updates dnf-plugins-core.noarch 4.0.21-1.fc34 @updates libdnf.x86_64 0.62.0-1.fc34 @updates python3-dnf.noarch 4.7.0-1.fc34 @updates python3-dnf-plugin-versionlock.noarch 4.0.21-1.fc34 @updates python3-dnf-plugins-core.noarch 4.0.21-1.fc34 @updates python3-libdnf.x86_64 0.62.0-1.fc34 @updates yum.noarch 4.7.0-1.fc34 @updates How reproducible: Steps to Reproduce: 1. dnf install dnf-plugins-core -y 2. dnf versionlock add procps-ng 3. dnf check-update Actual results: procps-ng is shown as an update. Expected results: procps-ng not getting shown as an update. Additional info: https://github.com/ansible-collections/community.general/issues/2539#issuecomment-842340203
Oh, the problem is caused by the minorbump part of release part of procps-ng package version. If you look into file /etc/dnf/plugins/versionlock.list you will probably see something like: # cat /etc/dnf/plugins/versionlock.list procps-ng-0:3.3.17-1.fc34.* In this file versionlock stores patterns of NEVRAs for allowed / excluded packages. The asterisk in the end of the line was meant for architecture part of the NEVRA but in procps-ng case it unfortunately matches also the newer `procps-ng-0:3.3.17-1.fc34.1` version. To workaround the issue (until it gets fixed) please either replace the asterisk with your architecture (e.g. procps-ng-0:3.3.17-1.fc34.x86_64) or remove it completely (e.g. procps-ng-0:3.3.17-1.fc34).
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.