Red Hat Bugzilla – Bug 322221
Error getting repository data for disabled nonexistent YUM repository
Last modified: 2014-01-21 17:59:56 EST
Description of problem: When I disable a repository with --disablerepo= that does not exist at all, yum dies with an error. Version-Release number of selected component (if applicable): yum-3.2.6-1.fc8 Actual results: [root@gopher hydrogen-0.9.3]# yum -d10 -v --disablerepo=jpackage --noplugins install binutils Error getting repository data for jpackage, repository not found [root@gopher hydrogen-0.9.3]# Expected results: It would make more sense to just ignore the --disablerepo.
Depends... if it's something that doesn't really exist, sure. But if it's something that exists and you just tyop'd the repoid, continuing on could end up giving exactly the results you were trying to avoid. The current behavior is very explicit and can't end up in things being installed/updated that you don't want; and the safer option being the default is generally the right thing to do with yum.