Bug 1001613 - no man-page for spacewalk-sync-setup
Summary: no man-page for spacewalk-sync-setup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 560
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Eric Herget
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat58-errata sat58-nth
TreeView+ depends on / blocked
 
Reported: 2013-08-27 11:52 UTC by Jan Hutař
Modified: 2018-02-23 15:55 UTC (History)
5 users (show)

Fixed In Version: spacewalk-utils-2.5.1-27-sat
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-23 15:55:45 UTC
Target Upstream Version:

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

Description Jan Hutař 2013-08-27 11:52:28 UTC 
Description of problem:
There is no manual page for spacewalk-sync-setup utility.


Version-Release number of selected component (if applicable):
spacewalk-utils-2.0.2-8.el6sat.noarch


How reproducible:
always


Steps to Reproduce:
1. # man spacewalk-sync-setup


Actual results:
No manual entry for spacewalk-sync-setup


Expected results:
There should be some.


Additional info:
Most probably not a Sat560 material
Comment 1 Grant Gainey 2013-08-27 17:37:52 UTC 
Well...sure enough.  Will add to SW, and we can decide when/if we want to pull into satellite.
Comment 3 Grant Gainey 2017-05-18 17:29:30 UTC 
Moving to 'Satellite Synchronization' with the other ISS and sync-setup BZs
Comment 4 Eric Herget 2017-10-05 21:10:33 UTC 
spacewalk.github
72df109b04eb4565cb2f714694e1878824fb9cf1

spacewalk-utils-2.8.6-1
Comment 12 Patrik Segedy 2018-02-22 15:05:45 UTC 
# rpm -q spacewalk-utils
spacewalk-utils-2.5.1-28.el6sat.noarch

man spacewalk-sync-setup
- shows man page

Man page shows the same options as spacewalk-sync-setup --help

Verified
Comment 13 Tomas Lestach 2018-02-23 15:55:45 UTC 
Thank you Patrik!

Based on Comments 11 and 12 I'm closing the BZ CURRENTRELEASE as the fix has been shipped within https://access.redhat.com/errata/RHBA-2018:0274
Note You need to log in before you can comment on or make changes to this bug.