Created attachment 635689 [details] Patch to fix the bug that I reported Description of problem: mrepo will not accept an argument to the option --repo The --help option does not document --version or --type Version-Release number of selected component (if applicable): 0.8.7 How reproducible: Every time Steps to Reproduce: 1. mrepo -vv --force -g --repo=os centos6 x86_64 2. mrepo --help 3. Actual results: 1. It prints: mrepo: option --repo must not have an argument, try mrepo -h for a list of all the options 2. It does not show --version or --type Expected results: Additional info: I attach a patch to fix this. All my own work - I release copyright to Dag Wieers, Fedora Project, whoever.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.