Bug 322221 - Error getting repository data for disabled nonexistent YUM repository
Error getting repository data for disabled nonexistent YUM repository
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jeremy Katz
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-07 11:42 EDT by Lubomir Kundrak
Modified: 2014-01-21 17:59 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-07 17:10:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lubomir Kundrak 2007-10-07 11:42:38 EDT
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):


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.
Comment 1 Jeremy Katz 2007-10-07 17:10:56 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.