Bug 1480613 - yum.conf manpage color options are incorrect
Summary: yum.conf manpage color options are incorrect
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-11 13:40 UTC by Jake Bathman
Modified: 2018-07-18 21:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-18 21:31:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jake Bathman 2017-08-11 13:40:10 UTC
Description of problem:
In the manpage for yum.conf(5) under the "color" option, it says "Possible values are: auto, never, always." However, the actual affirmative value is "on", and I'm not sure what the other possible values are, in the yum.conf file.

How reproducible:
Always

Steps to Reproduce:
1. Follow the manpage and use "color=always" in yum.conf
2. See if colors work in a yum command
3. Change the yum.conf line to "color=on" and try again

Comment 1 Jan Kurik 2017-08-15 09:36:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 2 Daniel Mach 2018-07-18 21:31:28 UTC
yum and related packages are no longer actively developed.
They are being replaced with dnf, dnf-utils, etc.

I'm closing this bug because it's most likely never going to be fixed.
If you still consider your bug report important, reopen it, please.

Comment 3 Daniel Mach 2018-07-18 21:34:14 UTC
yum and related packages are no longer actively developed.
They are being replaced with dnf, dnf-utils, etc.

I'm closing this bug because it's most likely never going to be fixed.
If you still consider your bug report important, reopen it, please.


Note You need to log in before you can comment on or make changes to this bug.