Hide Forgot
Description of problem: The man page describes --yum-cmd and --dnf-cmd, but these configuration options are not clear. For example, do these configuration options change mock's invocation of /usr/bin/yum to something else entirely (like /usr/bin/yum-deprecated?) Or do they simply append additional arguments onto /usr/bin/yum ? Does "--dnf-cmd" imply "--dnf"? Or do I have to specify it explicitly? It would be really nice to provide examples of when and how a user would use these configuration options. Version-Release number of selected component (if applicable): mock-1.2.7-1.fc22.noarch
Fixed in * 90ebb39 clarify "--yum-cmd" / "--dnf-cmd" options [RHBZ#1211621 https://git.fedorahosted.org/cgit/mock.git/commit/?id=90ebb39c8e6ac28c701dd0257616a966dc6d2048
Might I offer a couple suggestions? "Actually it will use binary which is specified" - "Actually" is unnecessary and sounds awkward - "it will use binary" should be "it will use the binary" It's still not clear to me how this relates to the "--yum" or "--dnf" options. For example, does the "--yum-cmd" command override my choice of "--yum" or "--dnf" ? I need to specify "--yum" if I've already specified "--yum-cmd"?
Thanks to the corrections. Applied. I added some examples and some clarification notes. Check it here: https://git.fedorahosted.org/cgit/mock.git/commit/?id=f182e628394b1d4f86317ec91477b0a77de6ce9a Also please mind difference between command (--yum-cmd) and option (--yum). Hmm. One more clarification: https://git.fedorahosted.org/cgit/mock.git/commit/?id=eed8ac633e0d4e69cdf003481ddb34ea3db8d1c2 I hope it is clear now.
mock-1.2.8-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc22
mock-1.2.8-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc21
mock-1.2.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mock-1.2.8-1.fc20
mock-1.2.8-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/mock-1.2.8-1.el7
mock-1.2.8-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.2.8-1.el6
Package mock-1.2.8-1.el7: * should fix your issue, * was pushed to the Fedora EPEL 7 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing mock-1.2.8-1.el7' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2015-6057/mock-1.2.8-1.el7 then log in and leave karma (feedback).
mock-1.2.8-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.8-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.8-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.10-1.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/mock-1.2.10-1.el7
mock-1.2.10-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/mock-1.2.10-1.el6
mock-1.2.10-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.10-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.