Bug 11564 - rsync could suggest openssh-client
Summary: rsync could suggest openssh-client
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Junior_job, Triaged
Depends on:
Blocks:
 
Reported: 2013-10-30 17:15 CET by Raoul
Modified: 2015-03-31 16:06 CEST (History)
3 users (show)

See Also:
Source RPM: rsync
CVE:
Status comment:

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

Description Raoul 2013-10-30 17:15:03 CET 
Apparently rsync ask for an ssh channel, but no ssh is avaialble on this newly installed machine. Which rpm have I to intsall ?


bash-4.2$ rsync pursig.exe XXXX.unige.ch:XXXX/
rsync: Failed to exec ssh: No such file or directory (2)
rsync error: error in IPC code (code 14) at pipe.c(84) [sender=3.0.9]
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in IPC code (code 14) at io.c(605) [sender=3.0.9]


Reproducible: 

Steps to Reproduce:
Comment 1 Raoul 2013-10-30 17:24:47 CET 
openssh-clients's rpm seems to be ok. Please made the test/correction in the rpm dependency.
Manuel Hiebel 2013-10-30 17:52:52 CET

Keywords: (none) => Junior_job, Triaged
CC: (none) => fundawang, nanardon
Summary: rsynch can't use ssh => rsync could suggest openssh-client

Comment 2 Thierry Vignaud 2013-10-30 20:38:52 CET 
ssh isn't needed for normal operation.
People usually use rsync with rsyn, ftp or http protocol.
rsyncing over ssh would not be the common case.
On the other way, a ssh suggests wouldn't hurt

CC: (none) => thierry.vignaud

Comment 3 Manuel Hiebel 2013-10-30 23:45:56 CET 
yep, I located at debian, and this is was is done.
Comment 4 Marja Van Waes 2015-03-31 16:06:55 CEST 
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.