Bug 505952 - yumex not disabling repos
yumex not disabling repos
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: yumex (Show other bugs)
11
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Tim Lauridsen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-14 18:37 EDT by David Hart
Modified: 2009-08-06 06:49 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-08-06 06:49:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Hart 2009-06-14 18:37:16 EDT
Description of problem:
On a Fedora 11 installation, I installed yumex (version 2.0.5) to manage my updates:
[CODE]sudo yum install yumex[/CODE]

Among the repos that I downloaded was livna.org, which I normally want disabled as the default. From within yumex, in the Repository Selection View, I removed the check associated with livna.

The next time I launched yumex and checked, livna was still checked. I had to manually edit /etc/yum.repos.d/livna.repo and change:
[CODE]enabled=1[/CODE]

to:
[CODE]enabled=0[/CODE]

to disable livna.


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


How reproducible: see above


Steps to Reproduce:
1.
2.
3.
  
Actual results: repository is not disabled (either in the yumex GUI or in the /etc/yum.repos.d/livna.repo file


Expected results: repository should be disabled (enabled=0 in /etc/yum.repos.d/livna.repo)


Additional info: There is a workaround (see above).
Comment 1 Tim Lauridsen 2009-08-06 06:49:32 EDT
repo selection in the yumex repo view, is a temporary selection for the current yumex session, it will not change the start of the .repo files.

You can use "System -> Administration -> Software Sources" to do a permanent change of a repo enable/disable state

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