Bug 507883
| Summary: | can't disable color from cmd line | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | James Antill <james.antill> |
| Component: | yum | Assignee: | James Antill <james.antill> |
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.4 | CC: | ffesti, james.antill, jhutar, pmatilai, rlerch, tim.lauridsen |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Due to a logic error in the code, yum ignored the --color=never option on the command line and color=never option in yum.conf. Yum output was therefore always in color, regardless of user preferences. With the error corrected, users can now use yum in monochrome.
|
Story Points: | --- |
| Clone Of: | 506754 | Environment: | |
| Last Closed: | 2009-09-02 07:33:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
James Antill
2009-06-24 15:56:35 UTC
This is a simple fix (move a couple of lines around) and ready to go for snap1. Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Due to a logic error in the code, yum ignored the --color=never option on the command line and color=never option in yum.conf. Yum output was therefore always in color, regardless of user preferences. With the error corrected, users can now use yum in monochrome. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1419.html |