Description of problem:
When the repo FOO in
dnf repoquery --repo FOO
is not enabled, an empty result is returned. It is necessary to enable the repo manually:
dnf repoquery --enablerepo FOO --repo FOO
Even though this behaviour is technically correct, I believe it would be logical and user friendly to automatically enable repos selected by --repo.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Disable a repository (FOO)
2. $ dnf repoquery --repo FOO
Listing of all packages in the repo FOO
...or we should at least print a warning.
FTR, I remember that we intentionally did not introduce this behaviour when implementing "dnf repo-pkgs". So, if we are going to implement this, it would be nice to make it consistent among all DNF commands.
Right, t should enable the specified repo. The same for "repo-pkgs".
With this change we can transfer this switch to DNF.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
The bug reported here is fixed in upstream (dnf-2.0), but problem mentioned in Comment 2 is solved by PR: https://github.com/rpm-software-management/dnf/pull/615