Bug 2066879

Summary: Inconsistent --mapfile / --map-file option spelling in tftpd manual page
Product: [Fedora] Fedora Reporter: Lukáš Zaoral <lzaoral>
Component: tftpAssignee: Dominik 'Rathann' Mierzejewski <dominik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dominik, jsynacek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tftp-5.2-33.fc34 tftp-5.2-35.fc35 tftp-5.2-36.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-06 18:44:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch to fix the --mapfile/--map-file discrepancy none

Description Lukáš Zaoral 2022-03-22 16:38:45 UTC
Created attachment 1867524 [details]
patch to fix the --mapfile/--map-file discrepancy

Description of problem: The --map-file tftpd option is spelled inconsistently in its manual page. Either as --mapfile or --map-file which may make its usage confusing to some users.

Version-Release number of selected component (if applicable): all releases so far

How reproducible: always

A patch fixing this issue is attached.

Comment 1 Fedora Update System 2022-03-29 12:23:23 UTC
FEDORA-2022-a179e3686c has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a179e3686c

Comment 2 Fedora Update System 2022-03-29 12:23:23 UTC
FEDORA-2022-9805cfbe9c has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9805cfbe9c

Comment 3 Fedora Update System 2022-03-29 12:23:24 UTC
FEDORA-2022-59c534a15b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-59c534a15b

Comment 4 Fedora Update System 2022-03-30 01:32:01 UTC
FEDORA-2022-59c534a15b has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-59c534a15b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-59c534a15b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-03-30 02:25:55 UTC
FEDORA-2022-a179e3686c has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a179e3686c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a179e3686c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-03-30 02:26:26 UTC
FEDORA-2022-9805cfbe9c has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-9805cfbe9c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9805cfbe9c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-04-06 18:44:49 UTC
FEDORA-2022-59c534a15b has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2022-04-06 19:04:03 UTC
FEDORA-2022-9805cfbe9c has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2022-05-07 04:12:34 UTC
FEDORA-2022-a179e3686c has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.