Red Hat Bugzilla – Bug 480058
repoquery can't list RPMs listed in /etc/yum.conf exclude= list
Last modified: 2014-01-21 18:07:46 EST
Description of problem:
So I hit a show-stopper issue with a specific RPM, and can't upgrade until something happens upstream (in this case, it was bug #433649 against gdm, open for several months now). So I list 'exclude=RPM' in /etc/yum.conf so that it doesn't keep showing up in 'yum list updates', and I can't accidentally do a 'yum update' and forget '--exclude=RPM'.
Unfortunately, it *also* means that to see if the fix has *landed* yet, I need to go edit /etc/yum.conf, remove the RPM from the exclude= list, save it, run 'repoquery --changelog <RPM>', look it over, re-edit yum.conf, re-add the RPM to the exclude= list, and re-save.
It would be helpful if repoquery didn't filter based on the exclude= list.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
We're unlikely to implement that since repoquery is yum-based and it makes sense to follow yum settings when you do that.
However, you can do:
repoquery -c /path/to/yum.conf
and just have that yum.conf not have the exclude= in it.
You can use --disableexcludes for "yum list updates" ... we could also implement that in repoquery, maybe.
Notably - if you're happy with all the other defaults in yum you can just do:
repoquery -c /dev/null .....
If repoquery supported --disableexcludes, that would solve the issue perfectly.