Description of problem: after having some issues with an upgrade I have a bunch of dupes The process documented http://dnf.readthedocs.io/en/latest/command_ref.html#repoquery-command-label fails claiming that the dnf query is invalid it seems it is the -1 if i change it to a 1 I get the latest builds not the older ones [root@bbb02 ~]# dnf repoquery --duplicates --latest-limit -1 -q usage: dnf repoquery [-c [config file]] [-q] [-v] [--version] [--installroot [path]] [--nodocs] [--noplugins] [--disableplugin [plugin]] [--releasever RELEASEVER] [--setopt SETOPTS] [--skip-broken] [-h] [--allowerasing] [-b] [-C] [-R [minutes]] [-d [debug level]] [--debugsolver] [--showduplicates] [-e ERRORLEVEL] [--obsoletes] [--rpmverbosity [debug level name]] [-y] [--assumeno] [--enablerepo [repo]] [--disablerepo [repo] | --repo [repo]] [-x [package]] [--disableexcludes [repo]] [--repofrompath [repo,path]] [--nogpgcheck] [--color COLOR] [--refresh] [-4] [-6] [--downloadonly] [--bugfix] [--enhancement] [--newpackage] [--security] [--advisory ADVISORY] [--bzs BUGZILLA] [--cves CVES] [--sec-severity {Critical,Important,Moderate,Low}] [-a] [--show-duplicates] [--arch ARCH] [-f FILE [FILE ...]] [--whatconflicts REQ] [--whatobsoletes REQ] [--whatprovides REQ] [--whatrequires REQ] [--whatrecommends REQ] [--whatenhances REQ] [--whatsuggests REQ] [--whatsupplements REQ] [--alldeps | --exactdeps] [--recursive] [--deplist] [--querytags] [--resolve] [--tree] [--srpm] [--latest-limit LATEST_LIMIT] [-i | -l | -s | --qf QUERYFORMAT | --nevra | --nvr | --envra] [--duplicates | --installonly | --unsatisfied] [--location] [--conflicts | --enhances | --provides | --recommends | --requires | --requires-pre | --suggests | --supplements] [--available] [--installed | --extras | --upgrades | --unneeded] [--recent] [key [key ...]] Version-Release number of selected component (if applicable): dnf-plugins-core-1.1.0-1.fc26.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The problem here is with argparser. Value -1 is recognized as a option not a value. There are some workaround: 1. --latest-limit=-1 2. --latest-limit " -1"
I create a pull request that only describe work around, but not solve a problem. Unfortunately we cannot do more.
Pull-request: https://github.com/rpm-software-management/dnf/pull/801
*** Bug 1428015 has been marked as a duplicate of this bug. ***
dnf-2.4.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-e0fa49ff81
dnf-2.4.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e0fa49ff81
dnf-2.4.1-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1467293 has been marked as a duplicate of this bug. ***
Seems that I had dnf-2.4.1-1.fc26 installed when the upgrade failed mentioned in bug #1467293, yet I still got the same error when trying to use -1 as an argument.
Definitely does not work for me, please retest and reopen this bug. $ rpm -q dnf dnf-plugins-core dnf-2.5.1-1.fc26.noarch dnf-plugins-core-2.1.1-1.fc26.noarch $ sudo dnf repoquery --duplicates --latest-limit -1 > /dev/null Command line error: argument --latest-limit: expected one argument
Sorry, didn't see it is not possible to fix this in current release. In a sense that is described in comment #2 it is fixed for me as well. --latest-limit <number> Limit the resulting set to <number> of latest packages for every package name and architecture. If <number> is negative skip <number> of latest packages. If negative number is used use syn‐ tax --latest-limit=<number>.