Bug 279881

Summary: yum shell ignores repo disable
Product: [Fedora] Fedora Reporter: Ian Mortimer <i.mortimer>
Component: yumAssignee: Jeremy Katz <katzj>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 7CC: james.antill, pmatilai, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-06 02:57:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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):
yum-3.2.4-2.fc7


How reproducible:
always


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
repos:

repo disable *
list available
run

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

repo disable *
repo list
run

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:

http://devel.linux.duke.edu/gitweb/?p=yum.git;a=commitdiff;h=9c6c6f88e524e7fec0e4a78ee9e8274fd9640c07;hp=ff1c6d84c96e09fa463fec1fa1ecf860ddf1163b