SUMMARY You can use a dnf plugin to version lock packages, so they won't get updated. Discover seems to ignore that, still showing updates for and wanting me to update those packages. STEPS TO REPRODUCE 1. Install 'dnf-command(versionlock)'. 2. Use dnf versionlock <package> to versionlock a specific package that has an update available. 3. Discover will still show updates for it and will want to update it. OBSERVED RESULT Discover wanted me to install an update for that package. EXPECTED RESULT It shouldn't have shown an update available, as it was versionlocked. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 with KDE KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION none
Does the same thing happen if you use `pkcon` in a terminal window? I suspect the problem is that the PackageKit library itself (which Discover and PKcon both use) doesn't support this via its DNF plugin.
I've just tried this and yes, it does. So it's probably an issue with PackageKit then. Thanks for the answer.
You're welcome. Feel free to report it at https://github.com/PackageKit/PackageKit/issues.
I'm still experiencing this bug (with dnf5) locked something using: ``` sudo dnf versionlock add vivaldi-stable ``` it doesn't show up when doing `sudo dnf up`, yet when i did update all through discover, it got updated. Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.0 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Kernel Version: 6.14.11-300.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300HQ CPU @ 2.50GHz Memory: 24 GiB of RAM (23.3 GiB usable) Graphics Processor 1: NVIDIA GeForce GTX 1050 Ti Graphics Processor 2: Intel® HD Graphics 630 Manufacturer: ASUSTeK COMPUTER INC. Product Name: FX502VE System Version: 1.0
I have bumped the issues in packagekit as well. if this is something you can't do anything about, feel free to re-close. revelant issue: https://github.com/PackageKit/PackageKit/issues/677 they said to file against libdnf, and in dnf5 repo they dismissed it with "the dnf plugin will be rewritten in dnf5 so it will be fixed". alas, dnf5 is out and it's not fixed. anything else i can do to progress this issue being resolved? Thank you.
It's still an upstream bug in the DNF PackageKit plugin.
Since this issue still is present in Discover 6.4.5, I've followed the breadcrumbs to this https://github.com/rpm-software-management/dnf5/issues/332 which seems to be a dead end. There are no direct pointers to other activities being done on the topic. Quoting conclusions here: > This is a bug between PackageKit and DNF4's libdnf because PackageKit uses DNF4's libdnf. and > it's not going to be implemented in dnf4 since [will be implemented in dnf5]
It seems to me after a bit more searching that PackageKit uses DNF4 instead of DNF5. Since I don't know much about PackageKit, I'm just putting here some leads for whomever may stumble uppon this after me: https://github.com/PackageKit/PackageKit/issues/822 - asks for PackageKit to use DNF5 due to history issues https://github.com/PackageKit/PackageKit/issues/679 - PackageKit reports no updates when DNF5 reports updates https://github.com/PackageKit/PackageKit/issues/803 - Asks for use of libdnf5 - no answers from maintainers https://github.com/PackageKit/PackageKit/pull/903 - it seems there are a few commits adding libdnf5 support, but I don't see how far that goes