Bug 230851
Summary: | yum does not accept --disablerepo option | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mamoru TASAKA <mtasaka> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | bkearney, jarod, lmacken, sertacyildiz |
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-04-25 22:06:47 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: | |||
Bug Depends On: | |||
Bug Blocks: | 150226, 230870 |
Description
Mamoru TASAKA
2007-03-03 18:34:40 UTC
Hrmm... this is being caused because we do the repo setup now when we access YumBase.repos. Which we do for the first time on the --disablerepo. repo setup probably needs to be separated from getting the repos object. But how to do that while still not making it so that we don't have to explicitly set up repos might be a little ugly :-/ I just noticed that --excluderepo is the typo. I meant "--disablerepo", sorry... yum-3.1.4-1.fc7 does not seem to be okay. I've just tested this command and --enablerepo on cvs head and I can't get the problem to occur. Can anyone else replicate it on what's in cvs right now? What do you mean by "cvs version"? At least, 3.1.5-1 is still not okay. 3.1.6-1 is still not okay. Then I need you to define 'not okay' b/c I can't make it fail. 100% reproducible as below. * Well, Currently "extras-development-debuginfo" repository (in fedora-extras-development.repo in fedora-release-6.92-1) cannot be enabled because http://mirrors.fedoraproject.org/mirrorlist?repo=extras-devel-debug&arch=i386' returns "# no repository available for repo extras-devel-debug" * Then intentionally enable this repository with writing "enabled=1" on extras-development-debuginfo repo in fedora-extras-development.repo file * Try # yum --disablerepo=extras-development-debuginfo check-update Then: Cannot find a valid baseurl for repo: extras-development-debuginfo Still happens on 3.1.6-1. 3.1.0-2 does not have this problem. Aha, it's related to the mirror list. The same thing doesn't happen if you have a non-existent baseurl. James -- does the patch you sent to yum-devel over the weekend help with this case? *** Bug 237168 has been marked as a duplicate of this bug. *** (In reply to comment #9) > Aha, it's related to the mirror list. The same thing doesn't happen if you have > a non-existent baseurl. > > James -- does the patch you sent to yum-devel over the weekend help with this case? Nope :( I did some hunting, and the root cause is the change to use properties rather than calling doFooSetup(). specifically, in cli.py: elif opt == "--disablerepo" self.base.repos.disableRepo(repoexp) that referencing of self.base.repos will end up running doRepoSetup() before disableRepo is called. Okay, got something that looks like it's working and sent it to the upstream list for comments. Should hopefully get into 3.1.7 yum-3.1.7-1 erased this problem. Thank you!! |