Bug 1316663 - missing man pages for secolor.conf and setrans.conf files
Summary: missing man pages for secolor.conf and setrans.conf files
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mcstrans
Version: 7.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Petr Lautrbach
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-10 17:22 UTC by Milos Malik
Modified: 2017-03-23 15:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 15:01:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Milos Malik 2016-03-10 17:22:17 UTC 
Description of problem:
 * both secolor.conf and setrans.conf files are taken into account when mcstrans daemon starts, but these files are not documented in a form of man pages

Version-Release number of selected component (if applicable):
mcstrans-0.3.1-4.el6.x86_64

How reproducible:
always

Steps to Reproduce:
# man secolor.conf
No manual entry for secolor.conf
# man setrans.conf
No manual entry for setrans.conf
# 

Actual results:
 * both man pages are missing

Expected results:
 * both man pages are present
Comment 3 Peter Vrabec 2016-06-13 13:41:09 UTC 
When Red Hat shipped 6.8 on May 10, 2016 RHEL 6 entered Production Phase 2.
https://access.redhat.com/support/policy/updates/errata#Production_2_Phase
That means only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released".

This issue will be tracked for RHEL-7. RHEL-7 is in Production Phase 1.
Comment 4 Nikola Forró 2017-03-23 10:01:25 UTC 
Petr,

since both man pages are present in RHEL 7, shouldn't this be closed NOTABUG?
Comment 5 Petr Lautrbach 2017-03-23 14:36:42 UTC 
Milos, do you agree to close this bug?
Comment 6 Milos Malik 2017-03-23 14:55:09 UTC 
Because this bug report was switched from RHEL-6 to RHEL-7, where the problem does not exist anymore, we can close it.
Note You need to log in before you can comment on or make changes to this bug.