Red Hat Bugzilla – Bug 1023595
yum-config-manager --setopt doesn't work with dotted repoids
Last modified: 2014-06-13 09:07:10 EDT
Description of problem:
Running yum-config-manager --setopt=repo.id.with.dots.enabled=0 repo.id.with.dots --save doesn't update the repo config file as expected.
Version-Release number of selected component (if applicable):
yum-utils-1.1.30-14 (Red Hat 6.4)
Add a repository with dots in the repoid, then try to adjust some attribute using yum-config-manager --setopt
Steps to Reproduce:
1. Add a repo in /etc/yum.repos.d with a dot in the repoid (in RHEL, this was discovered with the OpenShift repos, e.g. rhel-server-ose-1.2-infra-6-rpms)
2. Try to adjust some option using yum-config-manager: yum-config-manager --setopt=rhel-server-ose-1.2-infra-6-rpms.enabled=0 rhel-server-ose-1.2-infra-6-rpms --save
3. Check the repo file to verify that the change did not get committed
The "enabled" option will remain unchanged
The "enabled" option will be written to file as "enabled=0"
As mentioned above, this impacts Fedora and RHEL.
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.
Author: James Antill <email@example.com>
Date: Fri Oct 25 16:38:13 2013 -0400
yum-3.4.3-119.fc19 has been submitted as an update for Fedora 19.
yum-3.4.3-119.fc20 has been submitted as an update for Fedora 20.
* 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:
then log in and leave karma (feedback).
yum-3.4.3-120.fc19 has been submitted as an update for Fedora 19.
yum-3.4.3-120.fc20 has been submitted as an update for Fedora 20.
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.