Bug 1327438 - make --available default in dnf repoquery
Summary: make --available default in dnf repoquery
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Mracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-15 07:28 UTC by Tomas Mlcoch
Modified: 2016-10-04 18:08 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-10-04 18:08:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomas Mlcoch 2016-04-15 07:28:18 UTC
I have a repository "/path/to/repo/" with 3 packages, but when I run:

$ REPOID="160415-6" && dnf repoquery --repofrompath="$REPOID,file:///path/to/repo/" --disablerepo='*' --enablerepo="$REPOID" '*'

I get gazillion of packages.

Yum based repoquery works as expected:

$ REPOID="160415-6" && repoquery --repofrompath="$REPOID,file:///home/tmlcoch/git/createrepo_c/rpms_1/" --disablerepo='*' --enablerepo="$REPOID" '*'


My configuration:

$ cat /etc/fedora-release 
Fedora release 23 (Twenty Three)

$ rpm -q dnf hawkey libsolv librepo python-hawkey python-librepo
dnf-1.1.8-1.fc23.noarch
hawkey-0.6.2-3.fc23.x86_64
libsolv-0.6.19-2.fc23.x86_64
librepo-1.7.16-2.fc23.x86_64
python-hawkey-0.6.2-3.fc23.x86_64
python-librepo-1.7.16-2.fc23.x86_64

Comment 1 Honza Silhan 2016-04-18 12:02:05 UTC
We should consider how to make included available and installed by some options.

Comment 2 Jaroslav Mracek 2016-05-06 08:45:45 UTC
Repoquery from yum-utils shows only available package with higher version. ``yum info`` installed and only available package with higher version (install only packages works differently). 
We want that?:
1. ``dnf repoquery`` should show all available packages
2. ``dnf repoquery --installed`` only installed
3. ``dnf repoquery --installed --available`` all packages (this is at present time unsupported combination)

Or it should behave exactly like repoquery (same options, behavior)?

Here are some examples of yum - dnf compatibility:

repoquery --show-duplicates '*' = dnf repoquery --available

repoquery '*' = dnf repoquery --latest-limit=1 --available

The question is, if it is worth to change dnf repoquery behavior if same thing can be done by compatible layer for users, that like yum behavior, or by ``dnf repoquery`` options?

Comment 3 Jaroslav Mracek 2016-05-09 14:29:40 UTC
A made a pull-request that will allow --available as a default option:
https://github.com/rpm-software-management/dnf-plugins-core/pull/163


Note You need to log in before you can comment on or make changes to this bug.