Bug 322221 - Error getting repository data for disabled nonexistent YUM repository
Summary: Error getting repository data for disabled nonexistent YUM repository
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-07 15:42 UTC by Lubomir Kundrak
Modified: 2014-01-21 22:59 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-07 21:10:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lubomir Kundrak 2007-10-07 15:42:38 UTC
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.

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