Bug 515776 - repoquery cannot handle more than 8 args
repoquery cannot handle more than 8 args
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: yum-utils (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-05 13:25 EDT by Stepan Kasal
Modified: 2014-01-21 18:10 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-08-05 13:37:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stepan Kasal 2009-08-05 13:25:37 EDT
Description of problem:
"repoquery gawk grep" returns two lines, as expected.
But if I list 9 or more arguments, repoquery lists all packages in the repositories.
Actually, even "repoquery $(seq 9)" lists all the pakcages in the world.

Similarly with "repoquery -ql", as soon as 9 or more package names follows, the output contains all the files contained in all the available rpms.

Version-Release number of selected component (if applicable):
yum-utils-1.1.22-3.fc12

How reproducible:
always
Comment 1 seth vidal 2009-08-05 13:34:40 EDT
I can't seem to replicate this - what ver of yum?

I see:

$ repoquery yum yum-utils awk grep bash zsh tcsh rpm rpm-python python xterm pidgin xchat
tcsh-0:6.15-8.fc11.i586
zsh-0:4.3.9-4.fc11.i586
xterm-0:242-3.fc11.i586
xchat-1:2.8.6-7.fc11.i586
pidgin-0:2.5.8-2.fc11.i586
grep-0:2.5.3-4.fc11.i586
rpm-0:4.7.0-2.fc11.i586
yum-utils-0:1.1.22-1.fc11.noarch
bash-0:4.0-7.fc11.i586
yum-0:3.2.23-3.fc11.noarch
rpm-python-0:4.7.0-2.fc11.i586
python-0:2.6-9.fc11.i586
Comment 2 seth vidal 2009-08-05 13:37:53 EDT
correction - upstream yum has fixed this and it'll be in a ver of yum in rawhide very soon.

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