Description of problem:
Reading the man page too briefly can lead you to believe that this is a valid command:
yum --disablerepo=<repo> check-update
as happened here:
Version-Release number of selected component (if applicable):
~]# rpm -q yum
Steps to Reproduce:
1. man yum
yum [options] [command] [package ...]
yum [options] COMMAND [package ...]
The text for the man page can be improved in other places. Happy to send patches.
(In reply to Stephen Wadeley from comment #0)
> Description of problem:
> Reading the man page too briefly can lead you to believe that this is a
> valid command:
> yum --disablerepo=<repo> check-update
Actually, this *is* a valid command. What's not valid is something like:
That's what the reporter of the other BZ did with the expectation that it would disable the repo permanently, which is incorrect.
OTOH, it's true that the man page section for --disablerepo only says the following:
"Disables specific repositories by id or glob."
This can, indeed, mislead new users into thinking that it can be used alone, without a command, to permanently disable the given repo.
> Steps to Reproduce:
> 1. man yum
> Actual results:
> yum [options] [command] [package ...]
> Expected results:
> yum [options] COMMAND [package ...]
OK, this is a valid change that should make things clearer so we'll consider it.
> Additional info:
> The text for the man page can be improved in other places. Happy to send
Here's the upstream repo:
Patches are, of course, welcome, however please keep in mind that we cannot accept big changes (not even to the man page) at this point. In any case, feel free to post them and we'll take a look. Thanks!
Sorry for very long delay
(In reply to Stephen Wadeley from comment #4)
> Sorry for very long delay
> Thnak you
I don't think we should make the second change ("Temporarily enable ..."). To stay consistent, we would then have to add "temporarily" to every single CLI option as well. If there's no customer ticket related to this specifically, I would just leave it as it is. There's power in simplicity and consistency.
Regarding the first change, that's completely valid and we can use that.
OK to comment 5,
let me know if I need to make another push to remove that commit.
I just did. Thanks!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.