Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

repoquery: add filtering based on From repository. #381

Open
Ricky-Tigg opened this issue Mar 16, 2023 · 1 comment
Open

repoquery: add filtering based on From repository. #381

Ricky-Tigg opened this issue Mar 16, 2023 · 1 comment
Labels
Priority: LOW RFE Request For Enhancement (as opposed to a bug) Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take

Comments

@Ricky-Tigg
Copy link

v. 4.14.0 | Hello. Values reported by

  • dnf --installed repository-packages updates-testing list
  • dnf rq --installed --repo=updates-testing

while sent through pipe wc -l, are respectively non-null and null, despite they have similar goals. Since the former command executed as intended, the value of the latter command is expected not to differ from the value resulting from the former command.

@kontura
Copy link
Contributor

kontura commented Mar 20, 2023

Yes, the repoquery options --installed and --repo=.. are not compatible or rather they always result in an empty set because installed packages are in a special @System repo.

Probably the best solution would be to allow filtering packages by their from_repo attribute, that is the repo from which they come from.

We could implement a way to do that in dnf5 (possibly add a new repoquery option --from-repo=...) therefore I am transferring the issue to dnf5.

@kontura kontura transferred this issue from rpm-software-management/dnf Mar 20, 2023
@github-project-automation github-project-automation bot moved this to Backlog in DNF team Apr 14, 2023
@kontura kontura changed the title dnf rq | Installed packages from specified repository not reported repoquery: add filtering based on From repository. Jul 11, 2023
@j-mracek j-mracek added the Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take label Sep 15, 2023
@kontura kontura added the RFE Request For Enhancement (as opposed to a bug) label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: LOW RFE Request For Enhancement (as opposed to a bug) Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take
Projects
Status: Backlog
Development

No branches or pull requests

3 participants