Red Hat Bugzilla – Bug 244785
yum ignores the --disablerepo option
Last modified: 2014-01-21 17:58:36 EST
Description of problem: yum ignores the --disablerepo option Version-Release number of selected component (if applicable): yum-3.2.0-1.fc7 How reproducible: always Steps to Reproduce: 1. yum --disablerepo=REPONAME Actual results: repository is not excluded Expected results: repository should be ignored Additional info: Example: # yum --disablerepo=skype upgrade Loading "priorities" plugin Loading "presto" plugin Loading "dellsysidplugin" plugin Loading "installonlyn" plugin Loading "downloadonly" plugin Loading "skip-broken" plugin Loading "fastestmirror" plugin Loading "fedorakmod" plugin Loading "protectbase" plugin Setting up Presto Cannot open/read repodata/repomd.xml file for repository: skype In this case the unreachable repository (skype) should be ignored since it was disabled from the command line setting enable=0 in the configuration file is also not working Running with -d 9 does not give more information: # yum -d 9 --disablerepo=skype upgrade Loading "priorities" plugin Loading "presto" plugin Loading "dellsysidplugin" plugin Loading "installonlyn" plugin Loading "downloadonly" plugin Loading "skip-broken" plugin Loading "fastestmirror" plugin Loading "fedorakmod" plugin Loading "protectbase" plugin Running "config" handler for "priorities" plugin Running "config" handler for "presto" plugin Running "config" handler for "installonlyn" plugin Running "config" handler for "downloadonly" plugin Running "config" handler for "skip-broken" plugin Running "config" handler for "protectbase" plugin Running "postconfig" handler for "dellsysidplugin" plugin Running "init" handler for "dellsysidplugin" plugin Running "init" handler for "fastestmirror" plugin Running "init" handler for "fedorakmod" plugin Loading Fedora Extras kernel module support. Running "postreposetup" handler for "presto" plugin Setting up Presto Cannot open/read repodata/repomd.xml file for repository: skype
I believe this is due to some fun with the presto plugin -- can you try disabling it and see if that improves things? If so, then this will be resolved in yum 3.2.1
I removed the presto plugin and everything works as expected. I should have noticed that the problem was accurring too early and that the probable cause was a plugin. Thanks
Well, to be fair, what presto is doing _should_ work. It's just a yum bug that's keeping that from being the case. But good to know; will be fixed when we push the yum 3.2.1 update later this week