Bug 1023595
| Summary: | yum-config-manager --setopt doesn't work with dotted repoids | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John W. Lamb <jolamb> | |
| Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> | |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 19 | CC: | admiller, ffesti, firas.alkafri, james.antill, lmeyer, packaging-team-maint, tim.lauridsen, zpavlas | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | yum-3.4.3-120.fc20 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1024111 (view as bug list) | Environment: | ||
| Last Closed: | 2013-12-10 06:12:12 UTC | Type: | Bug | |
| 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: | 1024111 | |||
|
Description
John W. Lamb
2013-10-25 21:23:02 UTC
There is some indication that you should be able to work around this with wildcards, e.g. http://lists.baseurl.org/pipermail/yum-commits/2012-February/004559.html At least with yum-utils-1.1.30-14.el6.noarch though, this doesn't work. Wildcard setopts are silently ignored. E.g.: yum-config-manager --setopt '*.exclude=bar' rhel-6-server-rpms --save # that does nothing yum-config-manager --setopt 'rhel-6-server-rpms.exclude=bar' rhel-6-server-rpms --save # that works BTW, would it be too much trouble to get some kind of error indication when setopt is ignored? As it is, the only way you can tell you've made a typo or it didn't work is by checking the output value to see if it matches what you put in, which isn't great for scripted usage. Fixed upstream. It'll get back into F19 if/when we rebase yum. commit a39f13193419ce9494f21963b32ed7d4453e8e49 Author: James Antill <james> Date: Fri Oct 25 16:38:13 2013 -0400 yum-3.4.3-119.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/yum-3.4.3-119.fc19 yum-3.4.3-119.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/yum-3.4.3-119.fc20 Package yum-3.4.3-119.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing yum-3.4.3-119.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-22706/yum-3.4.3-119.fc20 then log in and leave karma (feedback). yum-3.4.3-120.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/yum-3.4.3-120.fc19 yum-3.4.3-120.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/yum-3.4.3-120.fc20 yum-3.4.3-120.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. yum-3.4.3-120.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |