Description of problem: [notting@nostromo: ~]$ repoquery --repofrompath=... Not using downloaded repomd.xml because it is older than what we have: Current : Tue Oct 16 22:38:14 2012 Downloaded: Tue Oct 16 09:28:52 2012 Argh, let's delete everything. [notting@nostromo: ~]$ rm -rf /var/tmp/yum-notting-7dZ0oL/ [notting@nostromo: ~]$ repoquery --repofrompath=... Not using downloaded repomd.xml because it is older than what we have: Current : Tue Oct 16 22:38:14 2012 Downloaded: Tue Oct 16 09:28:52 2012 Argh, right, it's copying the system repo. [notting@nostromo: ~]$ su [root@nostromo notting]# yum clean all Loaded plugins: auto-update-debuginfo, langpacks, refresh-packagekit Cleaning repos: fedora updates updates-testing Cleaning up Everything [root@nostromo notting]# exit [notting@nostromo: ~]$ repoquery --repofrompath=... Not using downloaded repomd.xml because it is older than what we have: Current : Tue Oct 16 22:38:14 2012 Downloaded: Tue Oct 16 09:28:52 2012 Argh, wtf, is there still a cached copy for me? [notting@nostromo: ~]$ yum clean all Loaded plugins: auto-update-debuginfo, langpacks, refresh-packagekit Cleaning repos: fedora updates updates-testing Cleaning up Everything [notting@nostromo: ~]$ repoquery --repofrompath=... Current : Tue Oct 16 22:38:14 2012 Downloaded: Tue Oct 16 09:28:52 2012 ARGH. [notting@nostromo: ~]$ su - [root@nostromo ~]# rm -rf /var/cache/yum/ [root@nostromo ~]# rm -rf /var/tmp/yum-notting-7XXAIY/ [root@nostromo ~]# logout [notting@nostromo: ~]$ repoquery --repofrompath=... ... proper results ... The issue, I suspect, is that cached repodata from --repofrompath will live eternally through 'yum clean all', because that only cleans enabled repos. Is that correct? Is it possible to have 'yum clean all' clean... *everything*? Version-Release number of selected component (if applicable): yum-3.4.3-45.fc18.noarch How reproducible: 100%
> cached repodata from --repofrompath will live eternally through 'yum clean all', because that only cleans enabled repos. Is that correct? Yes, "clean all" does not clean disabled repos. See BUG 744792 for similar problem (debuginfo repo disabled by default, but enabled in prereposetup hook). http://lists.baseurl.org/pipermail/yum-devel/2011-October/008724.html
yum explicitly only touches what is enabled, you can do: yum --enablerepo=\* clean all ...but even that will miss. repos. you don't have configuration for. There is also repomanage, and just plain rm -rf /var/cache/yum/*
Then I'd like to RFE that repoquery's --repofrompath not use the global caching configuration.
Here's another yum quirk. I commonly use the "--releasever" option to examine packages from other releases than the one I have installed. Cleaning those repos should be possible with this syntax: $ sudo yum clean all --enablerepo='*' --releasever='*' Instead, yum creates a directory called '*': $ ls /var/cache/yum/x86_64/ */ 16/ 17/ 18/ 19/ 19-beta/ 20/ f18/ f19/ rawhide/ repo-1/ $ ls /var/cache/yum/x86_64/'*' fedora/ updates/ updates-testing/ fedora-debuginfo/ updates-debuginfo/ updates-testing-debuginfo/ fedora-source/ updates-source/ updates-testing-source/ $ rpm -q yum yum-3.4.3-106.fc19.noarch
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.