Bug 799247 - References to rsync 3.0.7: documentation indicates that rsync 3.0.7 is required
Summary: References to rsync 3.0.7: documentation indicates that rsync 3.0.7 is required
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Divya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-02 09:13 UTC by Anjana Suparna Sriram
Modified: 2012-03-08 08:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-08 08:55:03 UTC
Target Upstream Version:

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

Description Anjana Suparna Sriram 2012-03-02 09:13:41 UTC 
rsync v3.0.7 is not needed any more, hence all references to it must be removed from the following User Guides:

16.2.3. Issues in Data Synchronization in RH VSA User Guide
14.2.3. Issues in Data Synchronization in RH SSA User Guide
15.2.3. Issues in Data Synchronization  in RHS User Guide

Note from Vijay on gluster-internal mailing list "We can work with rsync versions >= 3.0.0 and accordingly dependency has been changed for geo-replication rpm.
We would not need 3.0.7 anymore."
Comment 1 Anjana Suparna Sriram 2012-03-05 11:12:22 UTC 
RH SSA User Guide has been updated and re-published.(http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Storage_Software_Appliance/3.2/html/User_Guide/ch14s02s03.html)
Comment 2 Divya 2012-03-06 10:02:27 UTC 
Updated and re-published guides are available at:

RHS User Guide: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Storage/2/html/User_Guide/ch15s02s04.html

RHVSA User Guide: http://docs.redhat.com/docs/en-US/Red_Hat_Virtual_Storage_Appliance/3.2/html/User_Guide/ch16s02s03.html
Comment 3 Divya 2012-03-08 08:55:03 UTC 
Updated all the instances of 3.0.7 to 3.0.0 or higher.
Note You need to log in before you can comment on or make changes to this bug.