Description of problem: I just used a wrong repoquery without noticing: repoquery --repoid=fedora-updates --repoid=fedora --releasever 13 youtube-dl The problem is, the that there is no repo with the id fedora-updates, it is just updates. Nevertheless repoquery did not tell me this. Version-Release number of selected component (if applicable): yum-utils-1.1.26-1.fc12 How reproducible: always Steps to Reproduce: 1. repoquery --repoid=INVALID-$RANDOM yum-utils Actual results: returns nothing Expected results: should tell that there is no such repo. Additional info:
I added this upstream, however there is a long tradition of: . repoquery doesn't output anything to stderr in non-quiet mode. . repoquery is in quiet mode by default. ...but: repoquery --verbose --repoid=alkfjaljf -a ...will now tell you what you did wrong.
(In reply to comment #1) > I added this upstream, however there is a long tradition of: > > . repoquery doesn't output anything to stderr in non-quiet mode. Here are two mistakes I already made when I used repoquery (obviously with other parameters) regarding repo selection, where repoquery wrote something to stderr (the first one might be unintended): $ repoquery --repofrompath=/dev/null foo Traceback (most recent call last): File "/usr/bin/repoquery", line 867, in <module> main(sys.argv) File "/usr/bin/repoquery", line 784, in main repoid,repopath = tuple(repo.split(',')) ValueError: need more than 1 value to unpack $ repoquery --repofrompath=blah,/dev/null foo Cannot retrieve repository metadata (repomd.xml) for repository: blah. Please verify its path and try again
Hmm, apparently errors do come out in quiet mode (I've fixed the description of quiet). So I change the repoquery error message to come out too. The former was a bug, and has been fixed.
yum-utils-1.1.27-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/yum-utils-1.1.27-1.fc13
yum-utils-1.1.27-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.