Skip to content

Dnfdragora shows an update which should not be there #257

@L-U-T-i

Description

@L-U-T-i

Dnfdragora 2.1.6 (on freshly updated RHEL 9.6, with kmod-v4l2loopback-0.12.7-8.el9_6.elrepo.x86_64 package installed) announces an update (actually an older version of a package kmod-v4l2loopback-0.12.7^20230503g2c9b670-3.el9.x86_64), which can even not be installed, as it depends on some older kernel(s):
Image

Image

I've noticed the same happens with an older version of yumex (yumex-dnf 4.5.0):
Image

At the same time, dnf doesn't consider this version/release of the package as an update of the currently installed one:
Image

and new yumex-ng (which as much as I know still depends on dnfdaemon) also doesn't have this issue:
Image

I see elrepo created quite a mess with this package (git commit was in some releases a part of the package name, in the others a part of the version, and now not included at all) and probably version 0.12.7^20230503g2c9b670 is considered as higher than 0.12.7 by dnfdragora and yumex-dnf (and, not as such by dnf and yumex-ng!).

But, I think dnfdragora should be aligned with dnf about that, like the new yumex-ng is. Not to mention it is really annoying, as select all & update follows with an error now (package can not be updated due to a missing old kernel version / release). So, I have to look for this package after select all to uncheck it all the time...

Here is dnfdragora log file, if needed:
dnfdragora.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions