Red Hat Bugzilla – Bug 1480176
dnf repoquery --whatrequires <capability> doesn't work as expected
Last modified: 2017-12-12 05:17:04 EST
Description of problem:
In the manual page of dnf.plugin.repoquery there is not written what the <capability> is, but I deduce it's the same as what can be written in the Provides:. But if such constructs are used, repoquery behaves strange.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. dnf repoquery --alldeps --whatrequires 'tcl = 1:8.6.6-1' | grep dfish
2. dnf repoquery --alldeps --whatrequires 'tcl = 1:8.6*' | grep dfish
3. dnf repoquery --alldeps --whatrequires 'tcl=1:8.6.6*'
4. dnf repoquery --alldeps --whatrequires 'tcl = 1:8.6.6-1' | wc -l
5. dnf repoquery --alldeps --whatrequires tcl | wc -l
3. at least tk or nothing
4. much lower number than 33
So at the moment I have no idea how it works and how to get list of packages which requires exactly tcl 1:8.6.6 (e.g. for mass rebuild when updating to tcl-8.6.7).
Reassigning to libsolv, these strings are most likely parsed there.
I tested it with following result:
dnf repoquery --alldeps --whatrequires 'tcl = 1:8.6.6-1' | grep dfish
# output with dfish is correct, because it requires "tcl" and it means also 'tcl = 1:8.6.6-1'
Again no problem here. Output is expected
Ok here solver needs spaces around = (). But here we have to consider that allowed are =, <=, <, >, >= . And I am not sure if < or > can be part of version of package.
I checked output from dnf repoquery --alldeps --whatrequires 'tcl = 1:8.6.6-1' and each package requires tcl in form that fulfill the provide.
I guess expected output
I created patch that should solve example 3. (dnf repoquery --alldeps --whatrequires 'tcl=1:8.6.6*').
Hope that it helps.
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'
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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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
Thank you for reporting this bug and we are sorry it could not be fixed.