Bug 279881 - yum shell ignores repo disable
Summary: yum shell ignores repo disable
Alias: None
Product: Fedora
Classification: Fedora
Component: yum   
(Show other bugs)
Version: 7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-09-06 00:31 UTC by Ian Mortimer
Modified: 2014-01-21 22:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-09-06 02:57:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ian Mortimer 2007-09-06 00:31:10 UTC
Description of problem:
repos disabled in yum shell (with repo disable) are ignored when listing
available packages and when downloading and installing packages.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. create a yum shell which disables some repos
2. add a list available or update command after the repo disable
3. run the shell
Actual results:
yum lists or downloads and installs packages from disabled repos

Expected results:
yum should only list or download packages from repos enabled by the
configuration and not disabled in the shell.

Additional info:

For an extreme example this command line gets the expected result:

# yum --disablerepo='*' list available
Loading "downloadonly" plugin
No Repositories Available to Set Up

However the equivalent yum shell lists all available packages from all enabled

repo disable *
list available

On the other hand repo list shows all repos as disabled:

repo disable *
repo list

With yum-3.0.6-1.fc6 (on Fedora 6) running the first shell gets the expected result:

Setting up Yum Shell
Setting up repositories
No Repositories Available to Set Up

Comment 1 Seth Vidal 2007-09-06 02:57:03 UTC
Thank you for the easy replicator. I was able to track it down and fix the
problem in yum upstream. The fix will be available in yum 3.2.5

this patch contains the fix:


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