Bug 2070941 - small typo in lchage man page
Summary: small typo in lchage man page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libuser
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Tomas Halman
QA Contact: Filip Dvorak
URL:
Whiteboard:
Depends On:
Blocks: 2070943
TreeView+ depends on / blocked
 
Reported: 2022-04-01 11:32 UTC by Filip Dvorak
Modified: 2023-05-16 11:17 UTC (History)
3 users (show)

Fixed In Version: libuser-0.62-25.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2070943 (view as bug list)
Environment:
Last Closed: 2023-05-16 09:10:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-117623 0 None None None 2022-04-01 11:43:09 UTC
Red Hat Issue Tracker SSSD-4559 0 None None None 2022-04-07 13:26:14 UTC
Red Hat Product Errata RHBA-2023:3013 0 None None None 2023-05-16 09:10:26 UTC

Description Filip Dvorak 2022-04-01 11:32:51 UTC 
Description of problem:

manual page | wrong word | correct word
------------+----------+---------
lchage.1    | pasword  | password

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux release 8.6 Beta (Ootpa)
libuser-0.62-24.el8.

How reproducible:
always

Steps to reproduce:
1. man <anything-from-1st-column>
2. search for <anything-from-2nd-column>

Actual results:
There are typo errors in the man page.

Expected results:
There are no typo errors in the man page.
Comment 8 errata-xmlrpc 2023-05-16 09:10:24 UTC 
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 (libuser bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:3013
Note You need to log in before you can comment on or make changes to this bug.