Bug 1467293

Summary: dnf repoquery --duplicated --latest-limit -1 // argument --latest-limit: expected one argument
Product: [Fedora] Fedora Reporter: srakitnican <samuel.rakitnican>
Component: dnfAssignee: rpm-software-management
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 26CC: dmach, jmracek, packaging-team-maint, rpm-software-management, vmukhame
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-04 11:38:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description srakitnican 2017-07-03 10:25:12 UTC
Description of problem: "-1" in "--latest-limit -1" seems to be invalid argument with dnf 2.0, something that used to work with dnf 1.x for removing duplicate packages.


Version-Release number of selected component (if applicable):
$ rpm -q dnf
dnf-2.4.1-1.fc26.noarch
dnf-2.5.1-1.fc26.noarch


How reproducible: Always


Steps to Reproduce:
1. $ sudo dnf repoquery --duplicated --latest-limit -1

Actual results: Command line error: argument --latest-limit: expected one argument


Expected results:


Additional info: This system failed to upgrade most likely because libdb issue RHBZ#1465292 .

Comment 1 srakitnican 2017-07-03 10:29:14 UTC

*** This bug has been marked as a duplicate of bug 1446641 ***

Comment 2 srakitnican 2017-07-03 10:30:59 UTC
Thank you. Workarounds mentioned in other bug reports works.

Comment 3 Jaroslav Mracek 2017-08-04 11:38:32 UTC
I am sorry but the problem here was solved by providing a workaround including examples in documentation. The other solution cannot be provided with Python argparser.

*** This bug has been marked as a duplicate of bug 1446641 ***